<?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: Sensing Or Intuitive: Using Personas To Develop A User Interface</title>
	<atom:link href="http://www.fuelyourinterface.com/sensing-or-intuitive-using-personas-to-develop-a-user-interface/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.fuelyourinterface.com/sensing-or-intuitive-using-personas-to-develop-a-user-interface/</link>
	<description></description>
	<lastBuildDate>Mon, 01 Aug 2011 08:34:24 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Jeff</title>
		<link>http://www.fuelyourinterface.com/sensing-or-intuitive-using-personas-to-develop-a-user-interface/comment-page-1/#comment-1497</link>
		<dc:creator>Jeff</dc:creator>
		<pubDate>Mon, 15 Mar 2010 16:43:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.fuelyourinterface.com/?p=1502#comment-1497</guid>
		<description>You must have some idea whom your trying to target, yes? Age range, male, female, ethnicity, region, specific profession, animal lover, etc.. 

But yes you are right, personas are derived from discovery. Typically you should already have hard data about who your user is before creating personas, but there should also be some clear understanding of who your ultimately targeting before you begin. 

Define, Create, Analyze, Iterate(evolve).

When I talked about not changing the persona, I may have been unclear. I was referring more to not changing them to align with internal business goals and didn&#039;t mean to insinuate once defined they could not change.</description>
		<content:encoded><![CDATA[<p>You must have some idea whom your trying to target, yes? Age range, male, female, ethnicity, region, specific profession, animal lover, etc.. </p>
<p>But yes you are right, personas are derived from discovery. Typically you should already have hard data about who your user is before creating personas, but there should also be some clear understanding of who your ultimately targeting before you begin. </p>
<p>Define, Create, Analyze, Iterate(evolve).</p>
<p>When I talked about not changing the persona, I may have been unclear. I was referring more to not changing them to align with internal business goals and didn&#8217;t mean to insinuate once defined they could not change.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Grishma @strangloops</title>
		<link>http://www.fuelyourinterface.com/sensing-or-intuitive-using-personas-to-develop-a-user-interface/comment-page-1/#comment-1495</link>
		<dc:creator>Grishma @strangloops</dc:creator>
		<pubDate>Mon, 15 Mar 2010 13:28:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.fuelyourinterface.com/?p=1502#comment-1495</guid>
		<description>The naive in me keeps wondering that its hard to just put your customers in such simple groups and then make detailed landing page or conversion site. How do you do this if you are startup - when you are still in the customer discovery process?</description>
		<content:encoded><![CDATA[<p>The naive in me keeps wondering that its hard to just put your customers in such simple groups and then make detailed landing page or conversion site. How do you do this if you are startup &#8211; when you are still in the customer discovery process?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

