<?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>The Product Vision blog &#187; product vision</title>
	<atom:link href="http://productvision.org/blog/category/product-vision/feed/" rel="self" type="application/rss+xml" />
	<link>http://productvision.org/blog</link>
	<description>Articles about Product Vision and Strategy by D. Philip Haine</description>
	<lastBuildDate>Thu, 13 Jan 2011 07:56:53 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.4</generator>
		<item>
		<title>Just Four Ways to Make Money</title>
		<link>http://productvision.org/blog/four-ways-to-succeed/</link>
		<comments>http://productvision.org/blog/four-ways-to-succeed/#comments</comments>
		<pubDate>Tue, 02 Mar 2010 19:43:39 +0000</pubDate>
		<dc:creator>Philip Haine</dc:creator>
				<category><![CDATA[product vision]]></category>
		<category><![CDATA[business success]]></category>
		<category><![CDATA[ethics]]></category>
		<category><![CDATA[leadership]]></category>

		<guid isPermaLink="false">http://productvision.org/blog/?p=601</guid>
		<description><![CDATA[As I see it, there are just four overarching ways that businesses achieve financial success: Satisfy important unmet needs Convince people that they are doing #1 (whether or not they actually are) Exploit a human weakness Exploit cracks in the system (creating them if necessary) You might want to think about this a bit.  What [...]]]></description>
			<content:encoded><![CDATA[<p>As I see it, there are just four overarching ways that businesses achieve financial success:</p>
<ol>
<li><a href="http://productvision.org/blog/satisfy-important-needs/">Satisfy important unmet needs</a></li>
<li>Convince people that they are doing #1 (whether or not they actually are)</li>
<li>Exploit a human weakness</li>
<li>Exploit cracks in the system (creating them if necessary)</li>
</ol>
<p>You might want to think about this a bit.  What types of companies epitomize each?</p>
<p>The focus of this blog and <a href="http://productvision.com/">my company</a> is succeeding on the basis of method #1, satisfying important unmet needs.  It&#8217;s the sustainable, no-BS way to go about it.</p>
<p>But we must acknowledge that companies can and do succeed &#8212; at least from a financial standpoint &#8212; without actually having to do so.  You can, in fact, make a good living selling snake oil.</p>
<p>How about you?  How does your company succeed?  What type of business do you, personally, like to be involved in?  Which of the four are you personally driven to, and which are you repulsed  by?</p>
]]></content:encoded>
			<wfw:commentRss>http://productvision.org/blog/four-ways-to-succeed/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Predicting the impact of an innovation</title>
		<link>http://productvision.org/blog/predicting-innovation/</link>
		<comments>http://productvision.org/blog/predicting-innovation/#comments</comments>
		<pubDate>Mon, 09 Nov 2009 19:30:15 +0000</pubDate>
		<dc:creator>Philip Haine</dc:creator>
				<category><![CDATA[commentary]]></category>
		<category><![CDATA[product vision]]></category>
		<category><![CDATA[predictions]]></category>

		<guid isPermaLink="false">http://productvision.org/blog/?p=579</guid>
		<description><![CDATA[Over at Steve Portigal&#8217;s blog there was a discussion of France Telecom which has been introducing high quality audio to cellular voice calls.  (This is #7 on my 10 UI Wishes for 2008.) A commenter asked, and I paraphrase, &#8220;The question is, will people care? Is existing voice quality &#8216;good enough&#8217; that a jump in [...]]]></description>
			<content:encoded><![CDATA[<p>Over at Steve Portigal&#8217;s blog there was a <a href="http://www.portigal.com/blog/innovative-outcomes-take-years-to-launch-part-2/">discussion of France Telecom</a> which has been introducing <a href="http://www.nytimes.com/2009/09/17/technology/17voicehd.html">high quality audio to cellular voice calls</a>.  (This is #7 on my <a href="http://stealthisidea.com/articles/2008-ui-wishes/">10 UI Wishes for 2008</a>.)</p>
<p>A commenter asked, and I paraphrase, &#8220;The question is, will people care? Is existing voice quality &#8216;good enough&#8217; that a jump in quality won’t matter that much?&#8221;</p>
<p>What is important about this question is that it gets to the product vision skill of being able to distinguish revolutionary technologies from those that only sound revolutionary.</p>
<p>One guy <a href="http://www.nytimes.com/2009/09/17/technology/17voicehd.html">seemed to think HD audio was radical</a>, &#8220;This is a bigger innovation than cameras on handsets or app stores for the industry.”</p>
<p>Is he right?  Here was my response on Steve&#8217;s blog:</p>
<blockquote><p>Will customers care about HD audio?  I like to think about these things <a href="http://productvision.org/blog/products-by-needs/">in terms of needs</a>.  The HD audio people cited in the NYTimes thinks that this is more revolutionary than the camera in the mobile or the app store.</p>
<p>The guy is wrong. The cellphone camera and the app store are important because they <strong>enable the satisfaction of a host of new needs and scenarios</strong>.  You can now email a <a href="http://twitpic.com/135xa">picture of a sinking airplane</a> from a boat on the Hudson river.  The innovation is valuable to customers because more real needs are being met.  Simple as that.</p>
<p>HD audio,while difficult to do and very welcome, is still an incremental innovation to customers, because it merely <strong>does a better job of addressing needs that were adequately covered</strong> for the last 70 years.</p>
<p>In the market, incremental refinements like HD Audio are not irrelevant, but they tend to be tie-breakers.  Given two otherwise equal offerings, a customer might as well choose the more refined one.</p>
<p>Eventually the competition responds, and the refinement becomes table stakes for all players.  But until the advantage is neutralized, the company with the more refined solution has bragging rights that can distract customers from <a href="http://productvision.org/blog/satisfy-important-needs/">more important unmet needs</a>.</p></blockquote>
<p>It may be fairly obvious that HD audio is a nice-to-have, because we are all intimate users of telephony.  However this way of thinking &#8212; connecting the technology back to <a href="stealthisidea.com/articles/ssnifs/">scenarios and needs</a> &#8212; applies to less familiar ideas.  It&#8217;s a useful way to break through reality distortion fields and make predictions about the true relevance of exciting looking technologies to customers.</p>
]]></content:encoded>
			<wfw:commentRss>http://productvision.org/blog/predicting-innovation/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Complexity slays giants</title>
		<link>http://productvision.org/blog/complexity-slays-giants/</link>
		<comments>http://productvision.org/blog/complexity-slays-giants/#comments</comments>
		<pubDate>Thu, 15 Oct 2009 18:54:03 +0000</pubDate>
		<dc:creator>Philip Haine</dc:creator>
				<category><![CDATA[commentary]]></category>
		<category><![CDATA[predictions]]></category>
		<category><![CDATA[product vision]]></category>
		<category><![CDATA[Nokia]]></category>
		<category><![CDATA[Sony]]></category>

		<guid isPermaLink="false">http://productvision.org/blog/?p=546</guid>
		<description><![CDATA[Today&#8217;s news: Nokia reported a $1.36 billion loss in the third quarter as the company wrote down the value of its wireless networks venture by $1.35 billion and global sales declined 20 percent. The company [..] acknowledged that its lead in smartphones, the fastest-growing segment of the market, had fallen to 35 percent from 41 [...]]]></description>
			<content:encoded><![CDATA[<p><img class="alignright size-full wp-image-548" title="nokia" src="http://productvision.org/blog/wp-content/uploads/2009/10/nokia.gif" alt="nokia" width="200" height="200" /><a href="http://www.nytimes.com/2009/10/16/technology/companies/16nokia.html">Today&#8217;s news</a>:</p>
<blockquote><p>Nokia reported a $1.36 billion loss in the third quarter as the company wrote down the value of its wireless networks venture by $1.35 billion and global sales declined 20 percent.</p>
<p>The company [..] acknowledged that its lead in smartphones, the fastest-growing segment of the market, had fallen to 35 percent from 41 percent, losing ground to Apple’s iPhone and Research in Motion’s BlackBerry devices.</p></blockquote>
<p>Nokia&#8217;s problem is not execution.  It knows how to build things and bring them to market: it cranks out new models by the dozen.  Its problem is not innovation, at least not at the tactical level: every feature you&#8217;ve heard has made it into a shipping Nokia device.  Nokia&#8217;s problem is in product vision, of being able to imagine a coherent future reality with an ideal smartphone.</p>
<p>You might think that Nokia, with 25 years in the business, wouldn&#8217;t have allowed itself to be surpassed so easily.  But we should expect it.  It&#8217;s common pattern among big, old, successful companies.  Sony, Dell, GM, Motorola and countless others have fallen into the product vision trap, opening the door to disruptors.</p>
<p>Product vision becomes a bigger factor the more dials there are to turn in product formulation.</p>
<p>Sony traveled a similar arc in consumer electronics.  Sony was untouchable when their gadgets did only one or two things.  Like Nokia, it could master those core capabilities and move on to providing a variety of product variants for every segment, on marketing and on operations.  These were the business drivers as long as there was a steady state in the market.</p>
<p>But as technology enabled new classes of products, those old recipes no longer worked.  As the number of dials to turn in product formulation increase, the tried-and-true approach of cranking out incrementally better products breaks down.  Leadership gets overwhelmed by the plethora of choice.  In lieu of product vision to guide the way, they resort to guesswork, throwing everything against the wall to see what might stick.</p>
<p>Without a clear, coherent image of how things should be, design suffers.   Nokia&#8217;s products (and Sony&#8217;s, and Motorola&#8217;s, etc.) became complex, incoherent, and frustrating to use.  When products take on more capabilities, keeping things simple gets exponentially harder, because every feature relates to every other feature.  The possible associations grows with the square of the number of features.  (Even the best-of-class iPhone and Palm Pre are not immune.  <a href="http://stealthisidea.com/articles/palm-vs-iphone/">Both could do their core tasks considerably easier.</a>)</p>
<p>When products get more and more capable, the only way to cut through the jungle of choice, and the only way to keep the user experience coherent is with a clear product vision.</p>
<p>PS: Nokia has the market power but not the product vision.  Palm has the vision but not the market power.  I&#8217;m hungry for my <a href="http://www.youtube.com/watch?v=QfGQmotCIN0">Reese&#8217;s Peanut Butter Cup</a>.  When will Nokia acquire Palm?</p>
<p><em>&#8212;</em></p>
<p><em>Philip Haine is principal of <a style="color: #662625; outline-style: none; outline-width: initial; outline-color: initial;" href="http://productvision.com/">Product Vision Associates</a>, a product innovation consultancy that helps product leaders and their teams envision new, breakthrough products and reboot older ones.  To follow him on Twitter <a style="color: #662625; outline-style: none; outline-width: initial; outline-color: initial;" href="http://twitter.com/dphaine">click here</a>.</em></p>
]]></content:encoded>
			<wfw:commentRss>http://productvision.org/blog/complexity-slays-giants/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>You can&#8217;t focus on fog</title>
		<link>http://productvision.org/blog/focus-on-fog/</link>
		<comments>http://productvision.org/blog/focus-on-fog/#comments</comments>
		<pubDate>Mon, 14 Sep 2009 23:30:08 +0000</pubDate>
		<dc:creator>Philip Haine</dc:creator>
				<category><![CDATA[commentary]]></category>
		<category><![CDATA[product vision]]></category>

		<guid isPermaLink="false">http://productvision.org/blog/?p=494</guid>
		<description><![CDATA[The CEO of a hitherto search engine company reportedly told the troops: Let’s focus on a great Yahoo! Our average user is just trying to get through the day…looking to find out what’s going on in the big world and their own world. They want their Internet site to be great, and to work. They [...]]]></description>
			<content:encoded><![CDATA[<p>The CEO of a hitherto search engine company reportedly <a href="http://kara.allthingsd.com/20090831/the-carol-bartz-is-mad-as-hell-and-not-going-to-take-it-anymore-memo-the-hypoglycemic-edition/">told the troops</a>:</p>
<blockquote><p>Let’s focus on a great Yahoo! Our average user is just trying to get through the day…looking to find out what’s going on in the big world and their own world. They want their Internet site to be great, and to work. They don’t care about how or about deals. They care that we are a trusted dependable site.</p>
<p>That is our simple mission. Focus on it!!!</p></blockquote>
<p>Let&#8217;s itemize that.  Yahoo&#8217;s simple mission is to:</p>
<ol>
<li>Help users get through the day</li>
<li>Help users find out what&#8217;s going on in the world and their own world</li>
<li>Make an Internet site that is great, and works</li>
<li>Have a site that is trusted and dependable</li>
</ol>
<p>That&#8217;s a rather hazy vision to try and focus on.  Only #2 provides a modicum of guidance.  And even that amounts to, &#8220;Let&#8217;s do more of what we&#8217;ve been doing for the past 10 years.&#8221;  If that was the right strategy I doubt Yahoo would be where they are now.</p>
<p>Someone could use a little help with their product vision.</p>
]]></content:encoded>
			<wfw:commentRss>http://productvision.org/blog/focus-on-fog/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>GM: Epic failure of vision? Or culture?</title>
		<link>http://productvision.org/blog/gm-culture/</link>
		<comments>http://productvision.org/blog/gm-culture/#comments</comments>
		<pubDate>Wed, 10 Jun 2009 23:50:22 +0000</pubDate>
		<dc:creator>Philip Haine</dc:creator>
				<category><![CDATA[commentary]]></category>
		<category><![CDATA[product vision]]></category>
		<category><![CDATA[corporate culture]]></category>
		<category><![CDATA[GM]]></category>
		<category><![CDATA[strategy]]></category>

		<guid isPermaLink="false">http://productvision.org/blog/?p=346</guid>
		<description><![CDATA[Through the lens of product vision, I&#8217;ve been watching the devolution of GM for years.  So when it declared bankruptcy last week I was ready to commemorate the occasion by pronouncing it an epic failure of product vision. After all, they permitted the competition to consistently be superior in quality, not for a few quarters [...]]]></description>
			<content:encoded><![CDATA[<p style="font-size: 13px; line-height: 19px;"><img class="alignright" src="http://productvision.org/blog/wp-content/uploads/2009/06/gm.png" alt="" width="130" height="129" />Through the lens of product vision, I&#8217;ve been watching the devolution of GM for years.  So when it declared bankruptcy last week I was ready to commemorate the occasion by pronouncing it an epic failure of product vision.</p>
<p style="font-size: 13px; line-height: 19px;">After all, they permitted the competition to <a href="http://www.nytimes.com/2009/06/03/business/economy/03leonhardt.html">consistently be superior in quality</a>, not for a few quarters or years, but for a few decades. Their best efforts at innovation were directed not towards better cars, but the problem of preserving the status quo.  And they willfully ignored the writing on the wall with respect to future oil crises and the latent demand for efficiency.</p>
<p style="font-size: 13px; line-height: 19px;">Did you know that, as a result of progressive legislation, GM had an early lead not just in electrical vehicles like the <a href="http://en.wikipedia.org/wiki/Ev1">EV1</a>, but <a href="http://en.wikipedia.org/wiki/General_Motors_Precept">in hybrids</a> as <a href="http://www.popularmechanics.com/automotive/new_cars/1267946.html">well</a>? As soon as lobbyists managed to squelch California&#8217;s strict emissions standards (with the <a href="http://www.nytimes.com/2002/10/10/us/white-house-joins-fight-against-electric-cars.html">aid of the White House</a> at the time) GM yanked the plug on electrics.</p>
<p style="font-size: 13px; line-height: 19px;">The incredible postscript to this story is that it was <a href="http://en.wikipedia.org/wiki/Who_killed_the_electric_car">America&#8217;s call-to-arms for efficient vehicles that panicked Honda and Toyota into action</a>.  The Japanese manufacturers invested heavily in hybrids, leading to Toyota&#8217;s years-long lead in hybrid vehicles and the birth of the Prius.  While the American auto execs congratulated themselves for <a href="http://findarticles.com/p/articles/mi_qn4176/is_20060602/ai_n16460862/">persuading</a> <a href="http://www.nytimes.com/2008/11/12/opinion/12friedman.html">government</a> not to force it to invest in the inevitable future, Toyota went ahead and invented it.  Hybrids  “<a href="http://www.nytimes.com/2008/11/12/opinion/12friedman.html">make no economic sense</a>,” said GM vice-chairman Bob Lutz.  Oops.</p>
<p style="font-size: 13px; line-height: 19px;">And so an epic failure of product vision it certainly was. But that is not the heart of the story, or its root cause. The root cause is a cancerous corporate culture.</p>
<p style="font-size: 13px; line-height: 19px;">It&#8217;s a corporate culture where <strong>dissenting opinion is marginalized</strong> and only the yes-men survive. (For a taste of this, check out the <a href="http://fyi.gmblogs.com/2006/06/the_ban_on_rubbish_in_the_new_1.html">sycophantic employee comments</a> at GM&#8217;s own blog.)</p>
<p style="font-size: 13px; line-height: 19px;">It&#8217;s a corporate culture that&#8217;s <strong>driven by PR</strong> rather than product.  It&#8217;s a culture with a cynical view of customers that says that you don&#8217;t have to actually <em>deliver</em> the best products to them.  You only have to <em>convince</em> customers that they are the best products. You don&#8217;t have to actually <em>be</em> a green company.  Job #1 is to <a href="http://www.autobloggreen.com/2007/07/05/chevrolet-moving-ahead-with-more-green-vehicle-promotions-2007/"><em>convince everybody</em> that you&#8217;re green</a>.  The first act of a supposedly chastened GM?  <a href="http://www.nytimes.com/2009/06/02/business/media/02gmad.html">Yet another PR campaign</a> stating (<a href="http://www.nytimes.com/2009/06/03/business/economy/03leonhardt.html">yet again</a>) how it&#8217;s turned the corner.  At GM, image follows product.</p>
<p style="font-size: 13px; line-height: 19px;">This culture neglects the fact that between what you say and the money you want to make, you actually have to provide significant value to customers.  Making a lot of money in a sustainable fashion requires consistently <a href="http://productvision.org/blog/satisfy-important-needs/">satisfying important unmet customer needs</a>.</p>
<p style="font-size: 13px; line-height: 19px;">GM&#8217;s is a corporate culture that <strong>resolves the cognitive dissonance</strong> between the claimed and actual quality by <em>truly believing</em> that they are delivering quality. A company that believes its own BS sets sail from the reality-based community.  If it cannot be honest with itself, so loses its ability to self-correct and goes increasingly off-course.</p>
<p style="font-size: 13px; line-height: 19px;">GM&#8217;s is a corporate culture that <strong>is in denial</strong> about its own and failures and limitations, where <a href="http://www.nytimes.com/2009/06/01/business/01downfall.html">everyone else is the scapegoat</a>.  No failure is admitted, except perhaps the failure to get their message across to the public.</p>
<blockquote>
<p style="font-size: 13px; line-height: 19px;">“G.M., for all these decades, has been a ‘know-it-all’ company that had all the answers [..] I think it’s been proven that they really didn’t know it all.” &#8211; <a href="http://www.nytimes.com/2009/06/10/business/10auto.html">David Lewis</a></p>
</blockquote>
<p style="font-size: 13px; line-height: 19px;">GM&#8217;s culture is a <a href="http://www.nytimes.com/2009/06/02/opinion/02brooks.html">systemic cancer</a> that is not easily cured.</p>
<p style="font-size: 13px; line-height: 19px;">That&#8217;s why I was not very hopeful that a new GM, radically cut back, would be much different than the old, bloated GM. The only hope of turning around a corporate culture around like this is by decapitation.  The old leadership is simply too vested in their past decisions, too stewed in ancient assumptions and attitudes.  For fundamental change, the company&#8217;s values, reward system and world view must be turned upside down.  That is only possible with strong new leadership.</p>
<p style="font-size: 13px; line-height: 19px;">And that&#8217;s why it&#8217;s encouraging news that the shareholders of GM &#8212; i.e. us, the American public, as represented by our government &#8212; are <a href="http://www.nytimes.com/2009/06/10/business/10auto.html">replacing its leadership</a>.  Not just the CEO, but the entire board of directors, which somehow &#8212; someone please tell me how &#8212; tolerated the destruction of billions of dollars of value before their eyes over decades.</p>
<p>It won&#8217;t be easy to turn GM&#8217;s culture around.  Old habits die hard, and remember, it&#8217;s the yes-men who survived at GM, not the innovative rebels.  But at least now, with new leadership, it stands chance.</p>
<p>For the rest of us, GM&#8217;s insidious corporate culture is worth pondering and comparing against the institutions over which we have influence.</p>
<p><em>Update 6/10/09 nytimes has more on the challenges of <a href="http://www.nytimes.com/2009/06/11/business/11auto.html">reinventing GM&#8217;s culture</a>.</em></p>
<p>&#8212;</p>
<p><em>Philip Haine is principal of <a href="http://productvision.com/">Product Vision Associates</a>, a product innovation consultancy that helps product leaders and their teams envision new, breakthrough products and reboot older ones.  To follow him on Twitter <a href="http://twitter.com/dphaine">click here</a>.</em></p>
]]></content:encoded>
			<wfw:commentRss>http://productvision.org/blog/gm-culture/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Needs Analysis Part 1: Rating Products by Needs</title>
		<link>http://productvision.org/blog/products-by-needs/</link>
		<comments>http://productvision.org/blog/products-by-needs/#comments</comments>
		<pubDate>Fri, 21 Nov 2008 19:59:54 +0000</pubDate>
		<dc:creator>Philip Haine</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[product vision]]></category>
		<category><![CDATA[vision book]]></category>
		<category><![CDATA[needs analysis]]></category>

		<guid isPermaLink="false">http://productvision.org/blog/?p=212</guid>
		<description><![CDATA[In the last installment I used the example of the the Toyota Prius to demonstrate how the heart of a product can be expressed in terms of the problems it solves for customers, rather than by its features, design technologies.  Put another way, we can see beyond the surface by focusing on a product&#8217;s needs [...]]]></description>
			<content:encoded><![CDATA[<p style="font-size: 13px; line-height: 19px;">In the <a style="font-size: 13px; line-height: 19px;" href="http://productvision.org/blog/choosing-the-right-problem-to-solve/">last installment</a> I used the example of the the Toyota Prius to demonstrate how the heart of a product can be expressed in terms of the problems it solves for customers, rather than by its features, design technologies.  Put another way, we can see beyond the surface by focusing on a product&#8217;s needs profile &#8212; which set of needs it addresses, and to what degree.</p>
<p style="font-size: 13px; line-height: 19px;">Now I&#8217;d like to take it a step forward and show how to rate and visualize those needs.  This will help to formalize our needs analysis, laying down another stepping stone in our quest for a systematic way to approach product vision.</p>
<h3 style="font-size: 13px; line-height: 19px;">Grading how well each need is addressed</h3>
<p style="font-size: 13px; line-height: 19px;">Whether a need is addressed is not a black and white thing.  A product might do well on some needs, poorly on others, and in-between on others.  We can grade each need numerically.  I prefer to use a limited scale of 0 to 3, which makes assigning a value easy and avoids splitting hairs:</p>
<ul style="font-size: 13px; line-height: 19px;">
<li style="font-size: 13px; line-height: 19px;"><strong>0</strong> &#8211; The product does not attempt to address the need.</li>
<li style="font-size: 13px; line-height: 19px;"><strong>1</strong> &#8211; The product addresses the need at a basic level.</li>
<li style="font-size: 13px; line-height: 19px;"><strong>2</strong> &#8211; The product does a decent job of addressing the need, but there is still room for improvement.</li>
<li style="font-size: 13px; line-height: 19px;"><strong>3</strong> &#8211; The product fully satisfies the customer need, or the product is significantly ahead of the competition in doing so.</li>
</ul>
<h3 style="font-size: 15.2111px; line-height: 19px;">Needs Profile of the Prius<br style="font-size: 15.2111px; line-height: 19px;" /></h3>
<p style="font-size: 13px; line-height: 19px;"><a href="http://productvision.org/blog/wp-content/uploads/2008/11/prius4.jpg"><img class="alignright size-full wp-image-255" title="prius4" src="http://productvision.org/blog/wp-content/uploads/2008/11/prius4.jpg" alt="" width="254" height="142" /></a>When <a href="http://productvision.org/blog/choosing-the-right-problem-to-solve/">discussing the Prius</a> I spoke loosely of several customer needs: the needs for comfort, safety, fuel economy, and so on.  Let&#8217;s now enumerate and rate each one relative to other mid-size sedans and efficient vehicles that would serve as comparison points for a customer considering a Prius.</p>
<ul>
<li><strong>Need for </strong><strong>comfort</strong> &#8211; The Prius is surprisingly comfortable, but it&#8217;s not a luxury car.  So let&#8217;s give it a 2 for comfort and reserve the 3 for the more cushy rides.</li>
<li><strong>Need for </strong><strong>performance</strong> &#8211; The Prius has plenty of power to climb hills and pass, but it&#8217;s not a performance automobile.  We&#8217;ll give it a 2 out of 3.</li>
<li><strong>Need for </strong><strong>safety</strong> &#8211; It&#8217;s got a full compliment of safety features so we&#8217;ll give a 3.</li>
<li><strong>Need for </strong><strong>long range &#8211; </strong>The Prius&#8217;s range is excellent for a sedan, so it gets a 3.</li>
<li><strong>Need for </strong><strong>low fuel cost &#8211; </strong>Compared with regular sedans, the Prius has excellent fuel economy, so we&#8217;ll give it a 3.</li>
<li><strong>Need for </strong><strong>eco-friendliness</strong><strong> &#8211; </strong>It&#8217;s rated as a Super Ultra Low Emissions Vehicle (SULEV), so it gets 3 on need for eco-friendliness.</li>
<li><strong>Need for </strong><strong>distinctive styling</strong> -The Prius stands out among sedans, but it&#8217;s not showy.  We&#8217;ll give it a 2. (And we&#8217;ll say more about aesthetics later.)</li>
<li><strong>Need for </strong><strong>passenger capacity</strong> &#8211; The Prius comfortably sits five people.  We&#8217;ll give it a full 3 for passenger capacity.  (If we included minivans in the comparison set we&#8217;d have to give the Prius only a 2.) <strong><br />
</strong></li>
<li><strong>Need for </strong><strong>cargo capacity</strong> &#8211; the Prius has a large trunk and fold down back seats.  Quite good for a sedan, so we&#8217;ll give it 3 for cargo capacity.</li>
<li><strong>Need for </strong><strong>ease of learning and use</strong> &#8211; Part of the Prius&#8217;s appeal is that it operates like any regular car.   Unlike some alternative fuel vehicles, it requires no special training or change of habits.  We&#8217;ll give it 3 for learnability and usability.</li>
<li><strong>Need for </strong><strong>refueling convenience</strong> &#8211; With an electric car, you better make sure you&#8217;re near an outlet at the end of the day.  The Prius, on the other hand, is gassed up like any other car at any gas station. We&#8217;ll give it a 3 for refueling convenience.</li>
<li><strong>Need for </strong><strong>low initial costs</strong> &#8211; The sophisticated new engine on the Prius adds a couple of thousand dollars to the sticker price.  We&#8217;ll give it a 1 for low initial cost.</li>
<li><strong>Need for </strong><strong>low maintenance cost</strong> &#8211; More sophisticated cars require special training on the part of car shops, and are therefore <a href="http://articles.moneycentral.msn.com/SavingandDebt/SaveonaCar/HighTechCarRepairs.aspx">more expensive</a> to repair.  We&#8217;ll assign the Prius a 1.</li>
</ul>
<p style="font-size: 13px; line-height: 19px;">We can now visualize these values in a table:</p>
<p style="text-align: center;"><a href="http://productvision.org/blog/wp-content/uploads/2008/11/prius-needs.gif"><img class="aligncenter size-full wp-image-219" title="prius-needs" src="http://productvision.org/blog/wp-content/uploads/2008/11/prius-needs.gif" alt="" width="448" height="170" /></a></p>
<p>This is the <strong>needs profile</strong> of the Toyota Prius. The set of dimensions along the top is called the <strong>needs space</strong> and it will serve as the basis for comparison between products.</p>
<p>Notice that needs are always expressed in the positive. Bigger and darker numbers are always better.  Standardizing on this scale makes it easy to read the table and make comparisons.</p>
<h3>What&#8217;s going on here?</h3>
<p>Thinking of a product in terms of its needs profile forces us to think at a higher conceptual level.  for the Prius, we see beyond the details of its hybrid engine technology, funky styling and other features to the relevance those features have to the customer at the end of the day.  The needs viewpoint is intrinsically customer-centric.  When thinking needs, we can&#8217;t help but think of our product from the viewpoint of the people whom we want to have buy it.</p>
<p>The needs profile is a much more manageable way of understanding a product.  Thousands of minute variables are synthesized down into a reasonable set of dimensions that we can wrap our head around.</p>
<p>Using needs for our dimensions is not arbitrary.  We don&#8217;t just make up the needs.  Needs ultimately come from customers in particular situations (see <a href="http://stealthisidea.com/articles/ssnifs/">SSNiF Analysis</a>). The features of the Prius or any other product can be traced to specific needs that fall out of specific situations that are experienced by a specific set of customers (or stakeholders).  Even a feature as minute as a wide cupholder is traceable to a situation (buying Big Gulp at the drive-thru) and a resulting need (to put it down somewhere stable while traveling in a moving vehicle).  Because needs are always traceable to SSNiFs they are less arbitrary and more reliability.</p>
<p>We now have a the beginnings of a new conceptual model for dealing with product vision.  I call this approach to looking at products (and soon, customers), Formal Needs Analysis.  Things get more interesting when we use the same basis of needs to compare products, so let&#8217;s do that next.</p>
<h4 style="font-size: 13px; line-height: 19px;">See also</h4>
<p style="font-size: 13px; line-height: 19px;">
<ul style="font-size: 13px; line-height: 19px;">
<li style="font-size: 13px; line-height: 19px;"><a style="font-size: 13px; line-height: 19px;" href="http://productvision.org/blog/choosing-the-right-problem-to-solve/">Choosing the Right Problem to Solve</a></li>
<li style="font-size: 13px; line-height: 19px;">Other examples of needs analysis: <a href="http://stealthisidea.com/articles/reusable-bags/">Reusable shopping bags</a> | <a href="http://stealthisidea.com/articles/movie-needs/">Moviegoing</a></li>
<li style="font-size: 13px; line-height: 19px;"><a href="http://stealthisidea.com/articles/ssnifs/">SSNiF analysis</a> (Modeling scenarios in terms of Stakeholders, Situations and Needs, and connecting them to Features)</li>
</ul>
<p>&#8212;</p>
<p><em>Philip Haine is principal of <a href="http://productvision.com/">Product Vision Associates</a>, a product innovation consultancy that helps product leaders and their teams envision new, breakthrough products and reboot older ones.  To follow him on Twitter <a href="http://twitter.com/dphaine">click here</a>.</em></p>
<p style="font-size: 13px; line-height: 19px;">
]]></content:encoded>
			<wfw:commentRss>http://productvision.org/blog/products-by-needs/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>Choosing the right problem to solve</title>
		<link>http://productvision.org/blog/choosing-the-right-problem-to-solve/</link>
		<comments>http://productvision.org/blog/choosing-the-right-problem-to-solve/#comments</comments>
		<pubDate>Thu, 13 Nov 2008 18:25:38 +0000</pubDate>
		<dc:creator>Philip Haine</dc:creator>
				<category><![CDATA[product vision]]></category>
		<category><![CDATA[vision book]]></category>
		<category><![CDATA[book]]></category>
		<category><![CDATA[examples]]></category>

		<guid isPermaLink="false">http://productvision.org/blog/?p=192</guid>
		<description><![CDATA[Product vision can seem impenetrable. How did the breakthrough products in the Product Vision Hall of Fame manage to achieve something so much more advanced than the competition?  It is mysterious when we look at products at a surface level.  But things start to make sense when we shift our focus from the how we [...]]]></description>
			<content:encoded><![CDATA[<p>Product vision can seem impenetrable. How did the breakthrough products in the <a href="http://productvision.org/blog/hall-of-fame/ ">Product Vision Hall of Fame</a> manage to achieve something so much more advanced than the competition?  It is mysterious when we look at products at a surface level.  But things start to make sense when we shift our focus from the how we solve problems, to the choice of which problems to solve.</p>
<p>Normally when we look at any product, we see the tangible and concrete: the features, design, and technologies.  This is natural.  But it&#8217;s important to recognize that these things exist for a purpose, which is to solve a problem for someone.  When we scratch past the surface, we see that it&#8217;s this selection of the problem, not how it&#8217;s solved, that determines so much of a product&#8217;s fate.</p>
<p>When we look at the breakthrough products, we see that they didn&#8217;t merely do a better job of addressing the same customer needs.  They chose a a different set of needs.  And when we look at the spectacular failures, we find that the problems that they chose to solve were not especially important to customers.  <strong>Envisioning great products is about choosing the right set of problems to solve.</strong></p>
<h3>Deconstructing the problem</h3>
<p>We can always take a product and look beyond its surface to figure out what problems it is endeavoring to solve.  A corkscrew solves the problem of removing a cork from a bottle. A hammer and nails solves the problem of fastening large things together.</p>
<div id="attachment_252" class="wp-caption alignright" style="width: 264px"><a href="http://productvision.org/blog/wp-content/uploads/2008/11/prius3.jpg"><img class="size-full wp-image-252" title="prius3" src="http://productvision.org/blog/wp-content/uploads/2008/11/prius3.jpg" alt="Toyota Prius" width="254" height="166" /></a><p class="wp-caption-text">Toyota Prius</p></div>
<p>For a more sophisticated product, we can trace each individual feature to specific problems. Let&#8217;s take one of the <a href="http://productvision.org/blog/hall-of-fame/ ">Product Vision Hall of Fame</a>, the <a href="http://en.wikipedia.org/wiki/Prius">Toyota Prius</a>.</p>
<p>Looking at the distinguishing features of the Prius, we see a funky looking car that operates and performs like any other sedan, except that it has a a hybrid gas-electric engine.  Each of these key features exists to address some customer need:</p>
<ul>
<li>The hybrid engine saves fuel, which addresses the problem of high gas costs.  Phrased in terms of needs, we can say that it addresses the customer&#8217;s <strong>need for fuel economy</strong>.</li>
<li>The hybrid engine helps to qualify the Prius as a Super-Ultra Low Emissions Vehicle.  This help address the problem of greenhouse gas emissions and global warming. It helps address the customer need to minimize the impact on the environment, or, for brevity, the <strong>need for eco-friendliness</strong>.</li>
<li>The fact that the Prius drives like any other car solves the customer&#8217;s <strong>needs for comfort, safety, performance and range</strong>.  The driving experience is not compromised for the sake of economy, unlike earlier efficient vehicles.</li>
<li>The Prius is operated like any other vehicle: gas it up, step on the pedal, and go.  It does not require the driver to learn any new skills or change any habits,  Electric cars have a limited range and require that the driver plan out where the next charge will come from.  The Prius solves the customer <strong>need for ease of learning</strong> and, shall we say, the <strong>need for refueling convenience</strong>.</li>
<li>
<div id="attachment_251" class="wp-caption alignright" style="width: 264px"><a href="http://productvision.org/blog/wp-content/uploads/2008/11/insight2010.jpg"><img class="size-full wp-image-251" title="insight2010" src="http://productvision.org/blog/wp-content/uploads/2008/11/insight2010.jpg" alt="2010 Honda Insight" width="254" height="138" /></a><p class="wp-caption-text">2010 Honda Insight</p></div>
<p>What need is served by the Prius&#8217;s unusual styling?  To achieve it&#8217;s high mileage rating, Toyota was impelled by the laws of aerodynamics to deviate from the current fashion in automobile styling.  The weird body shape helped address the need for fuel economy.  But it also advanced Toyota&#8217;s need to have a distinctive automobile that stood out and declared to the world a new era in cars had arrived.  Now, several years after the Prius&#8217;s North American introduction, the body shape is iconic and is even being copied by Honda with the <a href="http://en.wikipedia.org/wiki/Honda_Insight#Second_generation">2010 Insight</a>.</li>
<li>The funky body styling turns out to address a second customer need as well. According to the <a href="http://www.nytimes.com/2007/07/04/business/04hybrid.html">New York Times</a>:</li>
</ul>
<blockquote><p>..more than half of the Prius buyers surveyed [..] said the main reason they purchased their car was that “it makes a statement about me.  [..] “I really want people to know that I care about the environment,” said Joy Feasley of Philadelphia, owner of a green 2006 Prius. “I like that people stop and ask me how I like my car.”</p></blockquote>
<p style="padding-left: 30px;">So it turns out that many customers had a couple of ulterior motives for buying a Prius: to make a personal statement, and to influence others into thinking about the environment and making progressive choices, too. The unusual body styling helped address these needs.</p>
<h3>Making Trade-offs</h3>
<p>Nothing comes for free in product design.  There are always trade-offs to be made.  And so it goes with product vision.  In the case of the Prius, the more complex engine and batteries come with a higher initial price, and possibly greater maintenance costs.</p>
<p>This set of trade-offs, with some needs addressed well and others addressed less well or not at all is what I call the product&#8217;s <strong>needs profile</strong>.  It is the blueprint of the product&#8217;s vision.</p>
<p>The Prius has a fundamentally different product vision, because its needs profile is unique.  None of the predecessors make the same set of trade-offs. Regular sedans are comfortable and safe, but do not address the need for fuel economy as well. Small cars address the need for fuel-efficiency but not the needs for space and comfort. Early electric vehicles like the <a href="http://en.wikipedia.org/wiki/Ev1">Ford EV1</a> were extremely efficient, but sacrificed internal passenger and cargo capacity, performance, range and refueling convenience.  Each comparison point makes a different balance of trade-offs and has a different  needs profile.</p>
<p>This will be a central theme in our study of product vision.  Sculpting the needs profile of future products will be a key tool in our arsenal for defining breakthrough products.</p>
<h3>Try this at home</h3>
<p>You can try this exercise of deconstructing products by needs yourself.  Pick up any simple product around you like a mechanical pencil or your coffee mug.  First ask yourself, what features or design elements or technologies make it unique among its peers?  Then ask, what problem does each feature solve that the others do not?  Then try and express the problem in terms of a customer need as I did for the Prius.</p>
<p>When you start to get good at this, you will develop an x-ray vision that lets you see past a product&#8217;s superficial skin to its essence and the reason that it exists. This is a core perspective for doing product vision work.</p>
<p>To summarize, envisioning great products is not about solving problems better, but choosing the right problems to solve.  Choose the wrong problems and your product will be doomed before the project begins.  Choose the right set of problems and you have the blueprint for a breakthrough product</p>
<p>See also:</p>
<ul>
<li><a href="http://productvision.org/blog/activities-goals-needs/">Picking a frame: Activities vs. Goals vs. Needs needs</a></li>
<li><a href="http://productvision.org/blog/satisfy-important-needs/">The First Rule of Product Vision </a></li>
<li><a href="http://stealthisidea.com/articles/ssnifs/">Introduction to SSNiF Analysis</a></li>
</ul>
<p>&#8212;</p>
<p><em>Philip Haine is principal of <a href="http://productvision.com/">Product Vision Associates</a>, a product innovation consultancy that helps product leaders and their teams envision new, breakthrough products and reboot older ones.  To follow him on Twitter <a href="http://twitter.com/dphaine">click here</a>.</em></p>
]]></content:encoded>
			<wfw:commentRss>http://productvision.org/blog/choosing-the-right-problem-to-solve/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
	</channel>
</rss>

