<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" 
  xmlns:dc="http://purl.org/dc/elements/1.1/"
  xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
  xmlns:admin="http://webns.net/mvcb/"
  xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#">

<channel>
<title>InfoDesign: Understanding by Design</title>
<link>http://www.informationdesign.org/</link>
<description>Dedicated to the growth and improvement of the information experience industries.</description>
<dc:language>en-us</dc:language>
<dc:creator>plato@xs4all.nl</dc:creator>
<dc:date>2010-02-15T16:04:13+01:00</dc:date>
<admin:generatorAgent rdf:resource="http://www.movabletype.org/?v=4.21-en" />
<sy:updatePeriod>hourly</sy:updatePeriod>
<sy:updateFrequency>1</sy:updateFrequency>
<sy:updateBase>2000-01-01T12:00+00:00</sy:updateBase>


<item>
<title>I Am Not A User!</title>
<description>&quot;Well, first of all let&apos;s get rid off the word user and let’s talk about people. Because user implies something totally internal: I&apos;m a user, I want to use this machine, so let&apos;s use it. This is a utilitarian/task cognitive approach to interaction design, a rather medieval kind of approach. If you talk about people, what they are and what they do in their daily lives, there are so many opportunities to discover… so users will not evolve, they will die out, but people will remain and I would like to talk about their lives and conquests.&quot; (I&apos;m not a user)</description>

<!-- 
<link>http://www.informationdesign.org/archives/2010/02/#005430</link>
<guid isPermaLink="false">5430@http://www.informationdesign.org/</guid>
 -->

<dc:subject>UCD</dc:subject>

<dc:date>2010-02-15T16:04:13+01:00</dc:date>
</item>

<item>
<title>UX Strategy is different than UI strategy: Part 1</title>
<description>&quot;(...) a real iterative UX Strategy that is based on Design practice not software engineering practice.&quot; (Jonathan Arnowitz - User Experience in ArnoLand)</description>

<!-- 
<link>http://www.informationdesign.org/archives/2010/02/#005425</link>
<guid isPermaLink="false">5425@http://www.informationdesign.org/</guid>
 -->

<dc:subject>UCD</dc:subject>

<dc:date>2010-02-10T12:39:18+01:00</dc:date>
</item>

<item>
<title>Hierarchical Task Analysis</title>
<description>&quot;As UX professionals, we have a great many analytical and descriptive tools available to us. In fact, there are so many that it can sometimes be difficult to decide which tool is most appropriate for a given task! Hierarchical task analysis (HTA) is an underused approach in user experience, but one you can easily apply when either modifying an existing design or creating a new design.&quot; (Peter Hornsby - UXmatters)</description>

<!-- 
<link>http://www.informationdesign.org/archives/2010/02/#005421</link>
<guid isPermaLink="false">5421@http://www.informationdesign.org/</guid>
 -->

<dc:subject>UCD</dc:subject>

<dc:date>2010-02-08T12:41:40+01:00</dc:date>
</item>

<item>
<title>Bringing User Centered Design to the Agile Environment</title>
<description>&quot;I am not anti-Agile although I’ve been bitten a few times and feel trepidation when I hear someone singing its praises without having much experience with it. Over the last eight years, I’ve seen Agile badly implemented far more often than well (and yes, it can be done well, too). The result of this is mediocre product released in as much time as it would have taken a good team to release great product using a waterfall approach. In this article, I will describe Agile and attempt to illuminate a potential minefield for those who are swept up in the fervor of this development trend and want to jump in headlong. Then I will present how practices within User Centred Design (UCD) can mitigate the inherent risks of Agile and how these may be integrated within Agile development approaches.&quot; (Anthony Colfelt - Boxes and Arrows)</description>

<!-- 
<link>http://www.informationdesign.org/archives/2010/02/#005412</link>
<guid isPermaLink="false">5412@http://www.informationdesign.org/</guid>
 -->

<dc:subject>UCD</dc:subject>

<dc:date>2010-02-01T09:53:13+01:00</dc:date>
</item>

<item>
<title>Don Norman on Ethnography and Innovation</title>
<description>&quot;Overall, it seems other examinations of innovation have proven the exact opposite of what Norman claims in his article. There is indeed a wealth of evidence that people’s needs can and should precede technology. And frankly, Norman&apos;s &apos;examination&apos; seems more of the back-of-the-napkin type with several errors.&quot; (James Kalbach - Experiencing Information)</description>

<!-- 
<link>http://www.informationdesign.org/archives/2009/12/#005349</link>
<guid isPermaLink="false">5349@http://www.informationdesign.org/</guid>
 -->

<dc:subject>UCD</dc:subject>

<dc:date>2009-12-24T12:02:33+01:00</dc:date>
</item>

<item>
<title>How UCD and Agile can live together</title>
<description>&quot;User-Centered Design is the methodology by which you design a holistic product while considering the needs of stakeholders and users. Agile Development is a programming methodology and philosophy intended to overcome the challenges of the waterfall development process and to deliver clean and functional code. How can these two methodologies come together?&quot; (David Farkas - Johnny Holland Magazine)</description>

<!-- 
<link>http://www.informationdesign.org/archives/2009/12/#005336</link>
<guid isPermaLink="false">5336@http://www.informationdesign.org/</guid>
 -->

<dc:subject>UCD</dc:subject>

<dc:date>2009-12-14T13:19:49+01:00</dc:date>
</item>

<item>
<title>The Fable of the User-Centred Designer</title>
<description>&quot;Follow a young man&apos;s journey as he discovers the three secrets of user-centred design. After reading this 40-page fable, you&apos;ll understand the framework of user-centred design and know how to apply it to your own design project. It&apos;s a small book that has big results.&quot; (UserFocus)</description>

<!-- 
<link>http://www.informationdesign.org/archives/2009/12/#005326</link>
<guid isPermaLink="false">5326@http://www.informationdesign.org/</guid>
 -->

<dc:subject>UCD</dc:subject>

<dc:date>2009-12-07T14:41:53+01:00</dc:date>
</item>

<item>
<title>Getting to the customer: Why everything you think about User Centred Design is wrong</title>
<description><![CDATA["A simple product like a hammer is best tested in it's final form. But a digital product, that in some ways is much more complex, is being tested before, by lesser means as if you can extract important feedback about the hammer." (Thomas Petersen - Black &amp; White) - courtesy of jameskelway]]></description>

<!-- 
<link>http://www.informationdesign.org/archives/2009/11/#005309</link>
<guid isPermaLink="false">5309@http://www.informationdesign.org/</guid>
 -->

<dc:subject>UCD</dc:subject>

<dc:date>2009-11-24T16:43:32+01:00</dc:date>
</item>

<item>
<title>Audience Segmentation Models</title>
<description>&quot;Understanding the people who will ultimately engage with a product or service provides the foundation for user experience design. Modeling those people and segmenting our models into meaningful groups lets us explore different clusters of needs, then address our solutions to meeting the needs of people belonging to specific clusters.&quot; (Steve Baty - UXmatters)</description>

<!-- 
<link>http://www.informationdesign.org/archives/2009/09/#005221</link>
<guid isPermaLink="false">5221@http://www.informationdesign.org/</guid>
 -->

<dc:subject>UCD</dc:subject>

<dc:date>2009-09-21T14:07:06+01:00</dc:date>
</item>

<item>
<title>Why low-fidelity prototyping kicks butt for customer-driven design</title>
<description>&quot;In my discussions with designers, one of the interesting recurring conversations is the tools and process they use to prototype and mock up experiences. In particular, there’s a lot of divergence on how high or low-fidelity to go with a prototype.&quot; (Andrew Chen) - courtesy of uxtweets</description>

<!-- 
<link>http://www.informationdesign.org/archives/2009/09/#005218</link>
<guid isPermaLink="false">5218@http://www.informationdesign.org/</guid>
 -->

<dc:subject>Prototyping</dc:subject>

<dc:date>2009-09-18T15:11:40+01:00</dc:date>
</item>

<item>
<title>Design Ethnography &amp; Mood Maps</title>
<description>&quot;The sole purpose of this exercise is to document and map the emotional states of a user so that it can guide the creation and communication of personas to stakeholders while also informing the design process itself. I&apos;m not one for ux deliverables for their own sake, but this is one that carry&apos;s a lot of weight and also goes a ways towards &apos;traceability&apos; - that is, the ability to show all the real research that went into your personas.&quot; (Will Evans) - courtesy of ppf</description>

<!-- 
<link>http://www.informationdesign.org/archives/2009/07/#005117</link>
<guid isPermaLink="false">5117@http://www.informationdesign.org/</guid>
 -->

<dc:subject>Personas</dc:subject>

<dc:date>2009-07-06T10:13:02+01:00</dc:date>
</item>

<item>
<title>Follow the Recipe</title>
<description>&quot;There are many good processes for software design. By process, I mean a prescribed way of performing software design. Every software company I’ve ever worked with has a design process they&apos;ve adopted or created to meet their needs. However, after working on numerous software projects, I have come to realize how few projects actually follow their companies’ intended design processes. Why is it that so many companies don&apos;t follow their existing processes for software design?&quot; - (Ron Gagnier - UXmatters)</description>

<!-- 
<link>http://www.informationdesign.org/archives/2009/05/#005047</link>
<guid isPermaLink="false">5047@http://www.informationdesign.org/</guid>
 -->

<dc:subject>UCD</dc:subject>

<dc:date>2009-05-26T10:30:04+01:00</dc:date>
</item>

<item>
<title>The poverty of user-centered design</title>
<description>&quot;(...) the set of methods employed by most user-centered professionals fails to deliver truly user-centric insights. The so-called &apos;science&apos; of usability which underlies user-centeredness leaves much to be desired. It rests too much on anecdote, assumed truths about human behavior and an emphasis on performance metrics that serve the perspective of people other than the user. - If we could de-couple user-centered design and usability then there might be some benefit but I don’t think this is as important as it might first appear. More important is the very conception we have of users and uses for which we wish to derive technologies and information resources. Designing for augmentation is a very real problem and a great challenge for our field theoretically and practically.&quot; - (Andrew Dillon - InfoMatters)</description>

<!-- 
<link>http://www.informationdesign.org/archives/2009/05/#005016</link>
<guid isPermaLink="false">5016@http://www.informationdesign.org/</guid>
 -->

<dc:subject>UCD</dc:subject>

<dc:date>2009-05-06T12:08:54+01:00</dc:date>
</item>

<item>
<title>You&apos;re only a first-time user once</title>
<description>&quot;Remember: a person is a first-time user exactly once (and in the case of the infusion pump, because of training and observation, nurses were actually never really first-time users), and in many cases a beginner for only a very short while.&quot; - (Steve Calde - Cooper Journal)</description>

<!-- 
<link>http://www.informationdesign.org/archives/2009/04/#004995</link>
<guid isPermaLink="false">4995@http://www.informationdesign.org/</guid>
 -->

<dc:subject>UCD</dc:subject>

<dc:date>2009-04-23T09:29:47+01:00</dc:date>
</item>

<item>
<title>Progressive User Adoption</title>
<description>&quot;Users of technology products—from mobile phones to ecommerce Web sites—often stop learning and adopting features long before they&apos;ve mastered those products’ full capabilities. A learning plateau usually occurs once a user has learned the features that meet his minimum product-adoption criteria, when the benefit of adopting more features doesn&apos;t seem worth the extra effort or risk.&quot; - (Mike Hughes - UXmatters)</description>

<!-- 
<link>http://www.informationdesign.org/archives/2009/03/#004950</link>
<guid isPermaLink="false">4950@http://www.informationdesign.org/</guid>
 -->

<dc:subject>UCD</dc:subject>

<dc:date>2009-03-24T09:39:46+01:00</dc:date>
</item>


</channel>
</rss>