<?xml version="1.0" encoding="iso-8859-1"?>
<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>2008-08-05T13:47:47+01:00</dc:date>
<admin:generatorAgent rdf:resource="http://www.movabletype.org/?v=3.15" />
<sy:updatePeriod>hourly</sy:updatePeriod>
<sy:updateFrequency>1</sy:updateFrequency>
<sy:updateBase>2000-01-01T12:00+00:00</sy:updateBase>

<item>
<title><![CDATA[<a href="http://www.mcq.com/article-persona">Using Persona Advocates to develop user-centric intranets and portals</a>]]></title>
<description><![CDATA["Intranets and portals are all—or mostly—about serving and enabling users. What information do they need and what tasks must they accomplish? How will they look for information? How does it need to be organized and presented for them to understand and use it? Do users have expertise in different subject areas or varying levels of technical vocabularies? Do they need instant information gratification or will they patiently research until they explore all possibilities?  Do users know what information they are seeking or do they need to be able to browse for something that will catch their eyes and provide the 'Aha!' experiences. Grasping complex information needs and uses can indeed be daunting. One powerful design tool, personas, can help make sense of these needs and provide a framework for building Intranets that will satisfy a variety of needs.  Effectively developed and used, personas enable Intranet teams to hone in on user needs and build interfaces and user experiences that end-user audiences can and will use." (Howard McQueen) - <i>courtesy of jamesrobertson</i>]]></description>

<!-- 
<link>http://www.informationdesign.org/archives/2008_08.php#004643</link>
<guid isPermaLink="false">4643@http://www.informationdesign.org/</guid>
 -->

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

<dc:date>2008-08-05T13:47:47+01:00</dc:date>
</item>
<item>
<title><![CDATA[<a href="http://personas.dk/?p=26">Engaging Personas and Narrative Scenarios</a>]]></title>
<description>&quot;Personas and scenarios help designers to imagine the users and aid development of design ideas. The concept of engaging personas and narrative scenario explores personas in the light of what what it is to identify with and have empathy with a character. The concept of narrative scenarios views the narrative as aid for exploration of design ideas. Both concepts incorporate a distinction between creating, writing and reading.&quot; (Lene Nielsen PhD thesis 2004)</description>

<!-- 
<link>http://www.informationdesign.org/archives/2008_07.php#004628</link>
<guid isPermaLink="false">4628@http://www.informationdesign.org/</guid>
 -->

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

<dc:date>2008-07-22T13:06:42+01:00</dc:date>
</item>
<item>
<title><![CDATA[<a href="http://www.personacreation.com/persona_creation/2008/04/beyond-fake-per.html">Beyond Fake Personas</a>]]></title>
<description><![CDATA["(...) if personas are fictional, how do you tell when a persona is fake? This great question highlights concerns about persona quality, validity, and usefulness that our clients often raise and that many persona thought leaders have addressed." (<a href="http://www.personacreation.com/about.html">Angela Quail</a> - <a href="http://www.personacreation.com/">Persona Creation</a>)]]></description>

<!-- 
<link>http://www.informationdesign.org/archives/2008_06.php#004591</link>
<guid isPermaLink="false">4591@http://www.informationdesign.org/</guid>
 -->

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

<dc:date>2008-06-11T15:11:08+01:00</dc:date>
</item>
<item>
<title><![CDATA[<a href="http://www.adlininc.com/corporate_underpants/?p=28">The Persona Non Grata article is a gift. Really.</a>]]></title>
<description><![CDATA["Here's the deal... he's got a great point, and I actually kinda furiously like the article because it reflects what annoys me about persona efforts (not personas themselves)." (<a href="http://www.adlininc.com/about/">Tamara Adlin</a> - <a href="http://www.adlininc.com/corporate_underpants/">Corporate Underpants</a>) - <i>courtesy of marrijeschaake</i>]]></description>

<!-- 
<link>http://www.informationdesign.org/archives/2008_02.php#004478</link>
<guid isPermaLink="false">4478@http://www.informationdesign.org/</guid>
 -->

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

<dc:date>2008-02-27T11:14:53+01:00</dc:date>
</item>
<item>
<title><![CDATA[<a href="http://www.greenonions.com/archives/2008/02/24/personas-good-enough-for-moses-good-enough-for-me/">Personas: Good Enough for Moses, Good Enough for Me</a>]]></title>
<description><![CDATA["These are personas that orbit a single objective and the ways in which people might accomplish that objective is defined in the personas. Writing it down now, it seems self-evident, but my personas have never been framed this way. Instead, typical personas identify user objectives and the product's requirements must support those objectives. To apply this to a specific example, take online banking. What would objectives look like if not defined by the target audience but instead by the business?" (<a href="http://www.greenonions.com/bio">Dan Brown</a> - <a href="http://www.greenonions.com/">Greenonions</a>) - <i>courtesy of livialabate</i>]]></description>

<!-- 
<link>http://www.informationdesign.org/archives/2008_02.php#004474</link>
<guid isPermaLink="false">4474@http://www.informationdesign.org/</guid>
 -->

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

<dc:date>2008-02-27T10:16:25+01:00</dc:date>
</item>
<item>
<title><![CDATA[<a href="http://www.boxesandarrows.com/view/personas-and-the">Personas and the Role of Design Documentation</a>]]></title>
<description><![CDATA["In User Experience Design circles, personas have become part of our established orthodoxy. And, as with anything orthodox, some people disagree on what personas are and the value they bring to design, and some reject the doctrine entirely." (<a href="http://www.boxesandarrows.com/person/43-andrewhinton">Andrew Hinton</a> - <a href="http://www.boxesandarrows.com/">Boxes and Arrows</a>)]]></description>

<!-- 
<link>http://www.informationdesign.org/archives/2008_02.php#004473</link>
<guid isPermaLink="false">4473@http://www.informationdesign.org/</guid>
 -->

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

<dc:date>2008-02-27T09:51:06+01:00</dc:date>
</item>
<item>
<title><![CDATA[<a href="http://bokardo.com/archives/personas-and-the-advantage-of-designing-for-yourself/">Personas and the Advantage of Designing for Yourself</a>]]></title>
<description><![CDATA["I think passion is a real issue with personas. Personas might elicit empathy with the people you design for, but they don't elicit passion. Passion comes from having a stake, having a long-term commitment. Passion is what gets you that last 10% to make something great. Designers designing for themselves are often passionate. It's hard to do as a freelancer or consultant." (<a href="http://bokardo.com/about/">Joshua Porter</a> - <a href="http://bokardo.com/">Bokardo</a>)
]]></description>

<!-- 
<link>http://www.informationdesign.org/archives/2008_01.php#004435</link>
<guid isPermaLink="false">4435@http://www.informationdesign.org/</guid>
 -->

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

<dc:date>2008-01-21T16:56:28+01:00</dc:date>
</item>
<item>
<title><![CDATA[<a href="http://toddwarfel.com/archives/presenting-on-data-driven-design-research-personas-for-connecticut-upa/">Data-Driven Design Research Personas</a>]]></title>
<description><![CDATA["(...) I presented on data-driven design research personas for the Connecticut UPA." (<a href="http://toddwarfel.com/about/">Todd Warfel</a> - <a href="http://messagefirst.com/">Messagefirst</a>)]]></description>

<!-- 
<link>http://www.informationdesign.org/archives/2007_12.php#004402</link>
<guid isPermaLink="false">4402@http://www.informationdesign.org/</guid>
 -->

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

<dc:date>2007-12-02T12:32:20+01:00</dc:date>
</item>
<item>
<title><![CDATA[<a href="http://www.andybudd.com/archives/2007/11/personas_suck/">Personas Suck</a>]]></title>
<description><![CDATA["(...) if you're building a site for a group of web designers, you probably don't need personas, whereas if you're building a site for a group of doctors, they could come in handy." (<a href="http://www.andybudd.com/">Andy Budd</a>)]]></description>

<!-- 
<link>http://www.informationdesign.org/archives/2007_11.php#004375</link>
<guid isPermaLink="false">4375@http://www.informationdesign.org/</guid>
 -->

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

<dc:date>2007-11-15T16:58:10+01:00</dc:date>
</item>
<item>
<title><![CDATA[<a href="http://www.boxesandarrows.com/view/building-a-data">Building a Data-Backed Persona</a>]]></title>
<description><![CDATA["Incorporating the voice of the user into user experience design by using personas in the design process is no longer the latest and greatest new practice. Everyone is doing it these days, and with good reason. Using personas in the design process helps focus the design team's attention and efforts on the needs and challenges of realistic users, which in turn helps the team develop a more usable finished design. While completely imaginary personas will do, it seems only logical that personas based upon real user data will do better. Web analytics can provide a helpful starting point to generate data-backed personas; this article presents an informal 5-step process for building a 'persona of the people'." (<a href="http://www.boxesandarrows.com/person/287-andreawiggins">Andrea Wiggins</a> - <a href="http://www.boxesandarrows.com/">Boxes and Arrows</a>)]]></description>

<!-- 
<link>http://www.informationdesign.org/archives/2007_11.php#004372</link>
<guid isPermaLink="false">4372@http://www.informationdesign.org/</guid>
 -->

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

<dc:date>2007-11-15T11:54:50+01:00</dc:date>
</item>
<item>
<title><![CDATA[<a href="http://www.hceye.org/HCInsight-Nielsen.htm">Ten Steps to Personas</a>]]></title>
<description><![CDATA["Any project that uses personas does not necessarily need to follow all 10 steps as long as the responsible party knows the consequences of skipping a step." (Lene Nielsen - <a href="http://hceye.org/HCVistas-About.htm">HCI Vistas</a>)]]></description>

<!-- 
<link>http://www.informationdesign.org/archives/2007_09.php#004318</link>
<guid isPermaLink="false">4318@http://www.informationdesign.org/</guid>
 -->

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

<dc:date>2007-09-28T16:36:11+01:00</dc:date>
</item>
<item>
<title><![CDATA[<a href="http://toddwarfel.com/archives/looking-back-on-data-driven-design-research-personas/">Looking Back on Data-Driven Design Research Personas</a>]]></title>
<description><![CDATA["The primary goal of the tutorial was to show people how to work data into developing personas and how they can be used for more than just design.”  (<a href="http://toddwarfel.com/">Todd Zaki Warfel</a>)]]></description>

<!-- 
<link>http://www.informationdesign.org/archives/2007_08.php#004291</link>
<guid isPermaLink="false">4291@http://www.informationdesign.org/</guid>
 -->

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

<dc:date>2007-08-31T11:45:56+01:00</dc:date>
</item>
<item>
<title><![CDATA[<a href="http://www.boxesandarrows.com/view/everything-and-the">Everything and the Kitchen Sink</a>]]></title>
<description><![CDATA[Book review on '<i>The Persona Lifecycle</i>' (Pruit and Adlin 2006) - "Pruit and Adlin use the lifecycle as a metaphor to frame the different stages personas go through, from birth to retirement. To highlight their process, a fictional case study runs throughout the book tying everything together. Because design doesn’t happen in a vacuum, the authors talk about how to ease the adoption and communication of personas at different levels of your organization. In fact, the book covers the two most important facets of personas: making them and getting them used." (Austin Govella - <a href="http://www.boxesandarrows.com/">Boxes and Arrows</a>)]]></description>

<!-- 
<link>http://www.informationdesign.org/archives/2007_05.php#004188</link>
<guid isPermaLink="false">4188@http://www.informationdesign.org/</guid>
 -->

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

<dc:date>2007-05-09T09:39:12+01:00</dc:date>
</item>
<item>
<title><![CDATA[<a href="http://www.wqusability.com/articles/personas_storytelling.html">Personas and Storytelling</a>]]></title>
<description><![CDATA["Personas work because they tell stories. Stories are part of every community. They communicate culture, organize and transmit information. Most importantly, they spark the imagination as you explore new ideas. They can ignite action." (<a href="http://www.wqusability.com/index.html">Whitney Quesenbery</a>) - <i>courtesy of craig marion</i>]]></description>

<!-- 
<link>http://www.informationdesign.org/archives/2007_04.php#004179</link>
<guid isPermaLink="false">4179@http://www.informationdesign.org/</guid>
 -->

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

<dc:date>2007-04-26T21:38:59+01:00</dc:date>
</item>
<item>
<title><![CDATA[<a href="http://www.disambiguity.com/yes-you-should-be-using-personas/">Yes, you should be using personas</a>]]></title>
<description><![CDATA["Personas communicate the user centred process like no other method." (<a href="http://www.disambiguity.com/about/">Leisa Reichelt</a> - <a href="http://www.disambiguity.com/">disambiguity</a>) - <i>courtesy of usernomics</i>]]></description>

<!-- 
<link>http://www.informationdesign.org/archives/2007_04.php#004174</link>
<guid isPermaLink="false">4174@http://www.informationdesign.org/</guid>
 -->

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

<dc:date>2007-04-24T09:51:16+01:00</dc:date>
</item>


</channel>
</rss>