<?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>Flex ID &#187; process</title>
	<atom:link href="http://www.flexid.com/tag/process/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.flexid.com</link>
	<description>A digital product design company and blog about interaction design and user experience</description>
	<lastBuildDate>Wed, 10 Feb 2010 08:27:03 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<item>
		<title>9 questions you should be able to answer</title>
		<link>http://www.flexid.com/2009/10/9-questions/</link>
		<comments>http://www.flexid.com/2009/10/9-questions/#comments</comments>
		<pubDate>Wed, 21 Oct 2009 19:18:51 +0000</pubDate>
		<dc:creator>Adam Korman</dc:creator>
				<category><![CDATA[Design]]></category>
		<category><![CDATA[process]]></category>

		<guid isPermaLink="false">http://www.flexid.com/?p=168</guid>
		<description><![CDATA[It&#8217;s surprising how often companies working on new products (or redesigning existing ones) don&#8217;t really know what they are trying to do or why. I&#8217;m a big advocate of talking to users in order to understand their needs, goals and behavior patterns as a starting point in the product design process, but before even getting to [...]]]></description>
			<content:encoded><![CDATA[<p>It&#8217;s surprising how often companies working on new products (or redesigning existing ones) don&#8217;t really know what they are trying to do or why. I&#8217;m a big advocate of talking to users in order to understand their needs, goals and behavior patterns as a starting point in the product design process, but before even getting to that, there are some questions you should be able to answer:</p>
<ol>
<li>What problem/opportunity are you trying to address in the marketplace?</li>
<li>What&#8217;s the high-level product concept?</li>
<li>What do you want to avoid getting into? An example: Microsoft Word is a general purpose word processing tool; it&#8217;s not trying to be a good tool for magazine layout.</li>
<li>What sorts of people do you think are going to use it?</li>
<li>What&#8217;s the planned business model? (Straight purchase vs. subscription vs. license vs. ad supported, etc.)</li>
<li>Are the people making the buying decisions your end users?</li>
<li>What are the technology options and limitations?</li>
<li>Who are the competitors? Think about everything that&#8217;s addressing the current gap, not just direct competitors. For example, Napster&#8217;s competitors include the obvious (iTunes, other digital music services), but the bigger competitors are actually physical medial sales (CDs represent about 2/3 of music purchases in the US), and stealing (~95% of music downloads are illegal).</li>
<li>What&#8217;s the definition of success for the product, and how will that be measured?</li>
</ol>
<p>This isn&#8217;t a comprehensive list, but it&#8217;s a good start. A deep understanding of all these things is great, but you also need to be able to articulate answers to these questions clearly and <em>succinctly</em> (or at least have reasonable hypotheses!). I&#8217;d say there&#8217;s some room for exception, say if you have the time and resources to explore experimental concepts that have a high likelihood of failure. That&#8217;s okay, but only if you know that you&#8217;re working on an experiment that might fail.</p>
<p>So, what&#8217;s the tenth question I missed?</p>
]]></content:encoded>
			<wfw:commentRss>http://www.flexid.com/2009/10/9-questions/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
