<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Done Bright! &#187; UX community</title>
	<atom:link href="http://luminanze.com/blog/category/ux-community/feed/" rel="self" type="application/rss+xml" />
	<link>http://luminanze.com/blog</link>
	<description>the Luminanze Consulting Blog</description>
	<lastBuildDate>Mon, 30 Mar 2015 08:49:21 +0000</lastBuildDate>
	
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>A Seminar and a Panelist Statement</title>
		<link>http://luminanze.com/blog/ux-community/a-seminar-and-a-panelist-statement/</link>
		<comments>http://luminanze.com/blog/ux-community/a-seminar-and-a-panelist-statement/#comments</comments>
		<pubDate>Sat, 09 Oct 2010 02:45:42 +0000</pubDate>
		<dc:creator>Elizabeth Buie</dc:creator>
				<category><![CDATA[UX community]]></category>
		<category><![CDATA[CHI2011]]></category>
		<category><![CDATA[SIGCHI]]></category>
		<category><![CDATA[ux]]></category>

		<guid isPermaLink="false">http://luminanze.com/blog/?p=69</guid>
		<description><![CDATA[I recently participated in a Dagstuhl seminar called &#8220;Demarcating User eXperience&#8221;. This 2.5-day workshop brought together 30 UX researchers and practitioners into an Eighteenth-Century manor house cum computer science conference center, just outside a tiny German village, to define the boundaries of the field of UX and begin writing a white paper about it. The [...]]]></description>
			<content:encoded><![CDATA[<p>I recently participated in a <a href="http://www.dagstuhl.de/en/program/calendar/semhp/?semnr=10373">Dagstuhl seminar called &#8220;Demarcating User eXperience&#8221;</a>. This 2.5-day workshop brought together 30 UX researchers and practitioners into an Eighteenth-Century manor house <em>cum</em> computer science conference center, just outside a tiny German village, to define the boundaries of the field of UX and begin writing a white paper about it. The seminar&#8217;s organizers described the problem this way:</p>
<p style="padding-left: 30px;">The concept of user experience (UX) is widely used but understood in  many different ways. The multidisciplinary nature of UX has provoked  several definitions and perspectives to UX, each approaching the concept  from a different viewpoint.</p>
<p style="padding-left: 30px;">UX is seen as a holistic concept covering all aspects of experiencing  a phenomenon, but we are facing the point where UX has become a concept  too broad to be useful in practice. Practitioners have difficulties to  understand the concept and to improve UX in their work, and researchers  rather use some other term to make their research scope clear.</p>
<p>So our job was to &#8220;demarcate&#8221; UX.</p>
<p>Most of the group was from academia, so I set myself the goal of keeping some level of focus on practitioners&#8217; needs, to maintain a balance. Each participant had to prepare a poster to present at the beginning of the seminar; mine is at <a href="http://www.luminanze.com/writings/DagstuhlPosterBuie.pdf">http://www.luminanze.com/writings/DagstuhlPosterBuie.pdf</a> (note: PDF). My main point was this:</p>
<p style="text-align: center; font-size: 1.2em; font-face: helvetica, arial, sans-serif;">UX already has a thriving practitioner community.<br />
We must address their needs.</p>
<p>After the introductions were complete, we spent the next few days discussing UX — what it is, how it&#8217;s measured, how long it lasts, how to design for it — until finally our time ran out. (We could have gone on a lot longer, I suspect.) Fortunately, I wasn&#8217;t the only one urging that we consider design, and we ended up adding to the outline of the white paper a section on design for user experience.</p>
<p>At the end, we talked about next steps, in particular how we could publicize the seminar&#8217;s results. Among other things, we decided to submit a panel proposal to the <a href="http://chi2011.org">CHI2011 conference</a>. <a href="http://research.nokia.com/people/jofish_kaye">Jofish Kaye</a> agreed to recruit the panelists and prepare the proposal; and two days ago when I asked him how it was going — surprise! — he added me to the panelists. This meant I had to write a position statement.</p>
<p>Now, I&#8217;m pretty good at writing short, pithy comments, such as tweets and Facebook statuses. A statement of two paragraphs, however, was much more daunting. But I managed, and here&#8217;s what I wrote:</p>
<p style="padding-left: 30px;">&#8220;User experience&#8221; abounds and thrives in the practitioner community. Events and organizations identify themselves with the &#8220;UX&#8221; label — from &#8220;UX Magazine&#8221; (<a href="http://uxmag.com">http://uxmag.com</a>), to Adaptive Path’s &#8220;UX Week&#8221; conference (<a href="http://www.uxweek.com">http://www.uxweek.com</a>), to the various &#8220;UX Book Clubs&#8221; (<a href="http://uxbookclub.org">http://uxbookclub.org</a>), to the titles of numerous practitioner books. Nowhere is the label more evident than on Twitter: People and organizations use &#8220;ux&#8221; in their handles (@lynneux, @uxmike, @inspire_ux, @ux_jobs, @uxfactory, @ux_dc, etc. etc.), in content-related hashtags (#ux, #uxdesignjobs), and even in social hashtags related to the community (#uxsters, #uxlovelies, #uxboots). Even the <a href="http://www.upassoc.org">Usability Professionals Association</a> titles its magazine &#8220;User Experience&#8221;.</p>
<p style="padding-left: 30px;">As practitioners, we generally agree that we are not designing experiences <em>per se</em>; &#8220;UX design&#8221; is just shorthand for designing <em>for</em> experience. We do lack a rigorous definition for &#8220;user experience&#8221; (we often refer to &#8220;DTDT&#8221; — &#8220;defining the damn thing&#8221; — to express the difficulty of agreeing on it), but I suspect we don’t actually need one. To design for experience, we don’t have to decide whether &#8220;experience&#8221; is immediate (e.g., three seconds) or it lasts from anticipation through memory of use; we need only recognize that it <em>occurs</em> throughout these phases and consider them all as we design. To create products that give users experiences along the lines of what we have in mind, we conduct user research and employ other time-honored as well as innovative design and evaluation techniques. We treat user experience as a focus in everything we do in our practice (see <a href="http://explainux.com">http://explainux.com</a>), and most of us are passionate about giving our users good experiences. Academic research can help by paying attention to the issues of practice and by making sure we know when it has discovered something that can make us more effective in realizing these goals.</p>
<p>Unfortunately, space limitations meant that only a very small part of each panelist&#8217;s statement made it into the submitted proposal. I think the proposal turned out well, though, and I&#8217;m optimistic that the panel will happen. Stay tuned.</p>
<p>(I will write more about the seminar in a later post. For now you can see <a href="http://www.flickr.com/groups/1485719@N24/pool/with/4992187615/">our photos on Flickr</a>.)</p>
]]></content:encoded>
			<wfw:commentRss>http://luminanze.com/blog/ux-community/a-seminar-and-a-panelist-statement/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Susan Dray: A portrait for Ada Lovelace Day</title>
		<link>http://luminanze.com/blog/ux-community/susan-dray-a-portrait-for-ada-lovelace-day/</link>
		<comments>http://luminanze.com/blog/ux-community/susan-dray-a-portrait-for-ada-lovelace-day/#comments</comments>
		<pubDate>Tue, 24 Mar 2009 00:01:00 +0000</pubDate>
		<dc:creator>Elizabeth</dc:creator>
				<category><![CDATA[UX community]]></category>
		<category><![CDATA[AdaLovelaceDay09]]></category>
		<category><![CDATA[CHI 2009]]></category>
		<category><![CDATA[MatriarCHI]]></category>
		<category><![CDATA[Susan Dray]]></category>
		<category><![CDATA[tributes]]></category>

		<guid isPermaLink="false">http://luminanze.com/blog/?p=24</guid>
		<description><![CDATA[A few months ago I made a pledge to participate in Ada Lovelace Day . This project asks bloggers to dedicate March 24 to blogging about women who excel in technology, to help provide girls and young women with role models in a variety of technological fields. I honor Ada Lovelace Day today by writing [...]]]></description>
			<content:encoded><![CDATA[<p>A few months ago I made a pledge to participate in <a title="Link to description of Ada Lovelace Day (will open in a new window)" href="http://findingada.com/" target="_blank">Ada Lovelace Day <img src="http://www.luminanze.com/images/new-window.gif" alt="" /></a>. This project asks bloggers to dedicate March 24 to blogging about women who excel in technology, to help provide girls and young women with role models in a variety of technological fields. I honor Ada Lovelace Day today by writing about Susan Dray.</p>
<p>Dr. Susan Dray is an international consultant on human-computer interaction design and usability. She has contributed tremendously to the profession of human-computer interaction throughout her 30-year career in the field, beginning with managing a human factors department and then pioneering the development of usability labs in corporations outside the computing industry. In recent years she has been instrumental in spreading the use of cross-cultural and ethnographic user research throughout the developing world. She works tirelessly to facilitate the appropriate design and use of technology in cultures where it can make a profound difference in their lives.</p>
<p>Susan Dray really does it bright. Although I have been in the field just a few years less than she has, Susan has been a role model for me — not only as a professional, but also as a human being. She inspires me to reach beyond what I already know I can do, to stretch myself, and to care even more deeply about how my work helps improve people&#8217;s lives.</p>
<p>I met Susan in 1983, during my first time at a conference of the Human Factors Society (now called the <a title="Link to Human Factors and Ergonomics Society (will open in a new window)" href="http://www.hfes.org" target="_blank">Human Factors and Ergonomics Society <img src="http://www.luminanze.com/images/new-window.gif" alt="" /></a>). She was co-leading a workshop on how to deal with being the only human factors person on a project, and as someone new to the field, not only did I find her knowledge and experience enlightening, but her energy and warmth encouraged me to persist with it; and I went on to get a second master&#8217;s, in a discipline related to the field. Our paths have crossed frequently over the years, and right now we are working more closely together than ever, co-chairing the User Experience Community at next month&#8217;s <a title="Link to CHI 2009 (will open in a new window)" href="http://www.chi2009.org" target="_blank">CHI 2009 <img src="http://www.luminanze.com/images/new-window.gif" alt="" /></a>, the annual conference of the Association for Computing Machinery&#8217;s Special Interest Group on Computer and Human Interaction. The last time I saw Susan, at CHI 2008, she had just finished leading a workshop on &#8220;HCI for Community and International Development&#8221; and was handing out pairs of socks left over from the workshop.</p>
<p><em>Socks?</em></p>
<p>Yep, socks. Socks with hearts on them.</p>
<p>&#8220;Anyone can wear their heart on their sleeve,&#8221; Susan explained. &#8220;But to make a real difference, to go in the right direction, we have to wear them on our feet as well.&#8221;</p>
<p>I took the purple ones.</p>
]]></content:encoded>
			<wfw:commentRss>http://luminanze.com/blog/ux-community/susan-dray-a-portrait-for-ada-lovelace-day/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
