<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: 2 personas vs 5 million users</title>
	<atom:link href="http://www.thinkflowinteractive.com/2008/02/22/2-personas-vs-5-million-users/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.thinkflowinteractive.com/2008/02/22/2-personas-vs-5-million-users/</link>
	<description>News and ideas on user experience.</description>
	<lastBuildDate>Thu, 15 Sep 2011 15:36:34 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Bookmarks about Personas</title>
		<link>http://www.thinkflowinteractive.com/2008/02/22/2-personas-vs-5-million-users/comment-page-1/#comment-249</link>
		<dc:creator>Bookmarks about Personas</dc:creator>
		<pubDate>Sun, 03 Aug 2008 15:15:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.thinkflowinteractive.com/2008/02/22/2-personas-vs-5-million-users/#comment-249</guid>
		<description>[...] - bookmarked by 2 members originally found by slgraffoo on July 17, 2008  2 personas vs 5 million users  http://www.thinkflowinteractive.com/2008/02/22/2-personas-vs-5-million-users/ - bookmarked by 3 [...]</description>
		<content:encoded><![CDATA[<p>[...] - bookmarked by 2 members originally found by slgraffoo on July 17, 2008  2 personas vs 5 million users  <a href="http://www.thinkflowinteractive.com/2008/02/22/2-personas-vs-5-million-users/" rel="nofollow">http://www.thinkflowinteractive.com/2008/02/22/2-personas-vs-5-million-users/</a> - bookmarked by 3 [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Simon Johnson</title>
		<link>http://www.thinkflowinteractive.com/2008/02/22/2-personas-vs-5-million-users/comment-page-1/#comment-147</link>
		<dc:creator>Simon Johnson</dc:creator>
		<pubDate>Thu, 06 Mar 2008 09:33:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.thinkflowinteractive.com/2008/02/22/2-personas-vs-5-million-users/#comment-147</guid>
		<description>This is a very interesting take on personas as it emphasises that personas are an empathetic method for design:

http://www.boxesandarrows.com/view/personas-and-the

The biggest insight I get from this story? Personas are not documents, and they are not the result of a step-by-step method that automagically pops out convenient facsimiles of your users. Personas are actually the designer’s focused act of empathetic imagination, grounded in first-hand user knowledge.

The team’s persona descriptions weren’t the source of the designers’ empathy —that kind of immersion doesn’t happen from reading a document. Although the team used various documentation media throughout their work – whiteboards and stickies, diagrams and renderings – these media furthered the design only as ephemeral artifacts of deeper understanding.

And that statement is especially true of personas. They’re not the same as market segmentation, customer profiling or workflow analysis, which are tools for solving other kinds of problems. Neither do personas fit neat preconceptions, use-cases or demographic models, because reality is always thornier and more difficult. Personas aren’t ornaments that make us more comfortable about our design decisions. They should do just the opposite—they may even confound and bedevil us. But they can keep us honest. Imagine that.</description>
		<content:encoded><![CDATA[<p>This is a very interesting take on personas as it emphasises that personas are an empathetic method for design:</p>
<p><a href="http://www.boxesandarrows.com/view/personas-and-the" rel="nofollow">http://www.boxesandarrows.com/view/personas-and-the</a></p>
<p>The biggest insight I get from this story? Personas are not documents, and they are not the result of a step-by-step method that automagically pops out convenient facsimiles of your users. Personas are actually the designer’s focused act of empathetic imagination, grounded in first-hand user knowledge.</p>
<p>The team’s persona descriptions weren’t the source of the designers’ empathy —that kind of immersion doesn’t happen from reading a document. Although the team used various documentation media throughout their work – whiteboards and stickies, diagrams and renderings – these media furthered the design only as ephemeral artifacts of deeper understanding.</p>
<p>And that statement is especially true of personas. They’re not the same as market segmentation, customer profiling or workflow analysis, which are tools for solving other kinds of problems. Neither do personas fit neat preconceptions, use-cases or demographic models, because reality is always thornier and more difficult. Personas aren’t ornaments that make us more comfortable about our design decisions. They should do just the opposite—they may even confound and bedevil us. But they can keep us honest. Imagine that.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alberto Mucignat</title>
		<link>http://www.thinkflowinteractive.com/2008/02/22/2-personas-vs-5-million-users/comment-page-1/#comment-146</link>
		<dc:creator>Alberto Mucignat</dc:creator>
		<pubDate>Mon, 03 Mar 2008 15:01:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.thinkflowinteractive.com/2008/02/22/2-personas-vs-5-million-users/#comment-146</guid>
		<description>&lt;strong&gt;Utenti o personaggi?...&lt;/strong&gt;

Nella progettazione centrata sull&#039;utente (UCD, User-Centered Design) un passaggio chiave è quello di definire i personaggi (o personas), ovvero degli &quot;utenti tipo&quot; sui quali verrà centrata tutta la progettazione del servizio web. Alla fine del proce...</description>
		<content:encoded><![CDATA[<p><strong>Utenti o personaggi?...</strong></p>
<p>Nella progettazione centrata sull'utente (UCD, User-Centered Design) un passaggio chiave è quello di definire i personaggi (o personas), ovvero degli "utenti tipo" sui quali verrà centrata tutta la progettazione del servizio web. Alla fine del proce...</p>
]]></content:encoded>
	</item>
</channel>
</rss>

