<?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: The Value of Asking &#8216;Why?&#8217;</title>
	<atom:link href="http://johnnyholland.org/2009/08/06/value/feed/" rel="self" type="application/rss+xml" />
	<link>http://johnnyholland.org/2009/08/06/value/</link>
	<description></description>
	<lastBuildDate>Tue, 16 Mar 2010 14:06:21 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: links for 2009-10-07 &#124; On9 Systems</title>
		<link>http://johnnyholland.org/2009/08/06/value/comment-page-1/#comment-28429</link>
		<dc:creator>links for 2009-10-07 &#124; On9 Systems</dc:creator>
		<pubDate>Thu, 08 Oct 2009 00:18:09 +0000</pubDate>
		<guid isPermaLink="false">http://johnnyholland.org/?p=3040#comment-28429</guid>
		<description>[...] Johnny Holland &#8211; It’s all about interaction » Blog Archive » The Value of Asking ‘Why?</description>
		<content:encoded><![CDATA[<p>[...] Johnny Holland &#8211; It’s all about interaction » Blog Archive » The Value of Asking ‘Why?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Blog Archive &#187; links for 2009-08-31 &#187; Small Farm Design</title>
		<link>http://johnnyholland.org/2009/08/06/value/comment-page-1/#comment-25014</link>
		<dc:creator>Blog Archive &#187; links for 2009-08-31 &#187; Small Farm Design</dc:creator>
		<pubDate>Mon, 31 Aug 2009 18:01:05 +0000</pubDate>
		<guid isPermaLink="false">http://johnnyholland.org/?p=3040#comment-25014</guid>
		<description>[...] The Value of Asking ‘Why?’ We must dedicate more time up front, at the start of any project or before we jump into developing a new feature, feature set or redesign effort to better assess the value of stuff we make. What makes people want something in the first place, use it, continue to use it, buy more of the same, treasure it and keep it? (tags: usability business strategy ux) [...]</description>
		<content:encoded><![CDATA[<p>[...] The Value of Asking ‘Why?’ We must dedicate more time up front, at the start of any project or before we jump into developing a new feature, feature set or redesign effort to better assess the value of stuff we make. What makes people want something in the first place, use it, continue to use it, buy more of the same, treasure it and keep it? (tags: usability business strategy ux) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Twitted by kopuru</title>
		<link>http://johnnyholland.org/2009/08/06/value/comment-page-1/#comment-22752</link>
		<dc:creator>Twitted by kopuru</dc:creator>
		<pubDate>Thu, 13 Aug 2009 07:25:43 +0000</pubDate>
		<guid isPermaLink="false">http://johnnyholland.org/?p=3040#comment-22752</guid>
		<description>[...] This post was Twitted by kopuru [...]</description>
		<content:encoded><![CDATA[<p>[...] This post was Twitted by kopuru [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Twitted by bnunnally</title>
		<link>http://johnnyholland.org/2009/08/06/value/comment-page-1/#comment-22131</link>
		<dc:creator>Twitted by bnunnally</dc:creator>
		<pubDate>Fri, 07 Aug 2009 13:32:50 +0000</pubDate>
		<guid isPermaLink="false">http://johnnyholland.org/?p=3040#comment-22131</guid>
		<description>[...] This post was Twitted by bnunnally [...]</description>
		<content:encoded><![CDATA[<p>[...] This post was Twitted by bnunnally [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Daniel Szuc</title>
		<link>http://johnnyholland.org/2009/08/06/value/comment-page-1/#comment-22129</link>
		<dc:creator>Daniel Szuc</dc:creator>
		<pubDate>Fri, 07 Aug 2009 13:06:58 +0000</pubDate>
		<guid isPermaLink="false">http://johnnyholland.org/?p=3040#comment-22129</guid>
		<description>Lets try that again - &quot;The Cultures of Design&quot; - 

http://www.dmi.org/dmi/html/publications/news/viewpoints/connect_vp_sp.htm</description>
		<content:encoded><![CDATA[<p>Lets try that again &#8211; &#8220;The Cultures of Design&#8221; &#8211; </p>
<p><a href="http://www.dmi.org/dmi/html/publications/news/viewpoints/connect_vp_sp.htm" rel="nofollow" onclick="pageTracker._trackPageview('/outgoing/www.dmi.org/dmi/html/publications/news/viewpoints/connect_vp_sp.htm?referer=');">http://www.dmi.org/dmi/html/publications/news/viewpoints/connect_vp_sp.htm</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Twitted by lwcavallucci</title>
		<link>http://johnnyholland.org/2009/08/06/value/comment-page-1/#comment-22128</link>
		<dc:creator>Twitted by lwcavallucci</dc:creator>
		<pubDate>Fri, 07 Aug 2009 13:05:41 +0000</pubDate>
		<guid isPermaLink="false">http://johnnyholland.org/?p=3040#comment-22128</guid>
		<description>[...] This post was Twitted by lwcavallucci [...]</description>
		<content:encoded><![CDATA[<p>[...] This post was Twitted by lwcavallucci [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Daniel Szuc</title>
		<link>http://johnnyholland.org/2009/08/06/value/comment-page-1/#comment-22127</link>
		<dc:creator>Daniel Szuc</dc:creator>
		<pubDate>Fri, 07 Aug 2009 13:03:29 +0000</pubDate>
		<guid isPermaLink="false">http://johnnyholland.org/?p=3040#comment-22127</guid>
		<description>@Jeroen - &quot;they should feel and breath it&quot; &amp; &quot;It will be a driving force instead of just a rule.&quot; - absolutely! Suggest these are challenges for Product Teams.

Has adequate time been allocated to:

1. Articulate the Product and UX Vision?
2. Communicate it the Vision and Values clearly?

Are people able to:

3. Hold onto the Vision, Design Tenets and Values along the way
4. Revisit it and know when and why you need to go against the original values
5. Scope and focus correctly so you are building the right thing and testing assumptions through research along the way

A reasonable amount of dependency on &quot;corporate culture&quot; - http://www.portigal.com/news/new-article-the-cultures-of-design-at-dmi/

Good discussion.

rgds,
Dan</description>
		<content:encoded><![CDATA[<p>@Jeroen &#8211; &#8220;they should feel and breath it&#8221; &amp; &#8220;It will be a driving force instead of just a rule.&#8221; &#8211; absolutely! Suggest these are challenges for Product Teams.</p>
<p>Has adequate time been allocated to:</p>
<p>1. Articulate the Product and UX Vision?<br />
2. Communicate it the Vision and Values clearly?</p>
<p>Are people able to:</p>
<p>3. Hold onto the Vision, Design Tenets and Values along the way<br />
4. Revisit it and know when and why you need to go against the original values<br />
5. Scope and focus correctly so you are building the right thing and testing assumptions through research along the way</p>
<p>A reasonable amount of dependency on &#8220;corporate culture&#8221; &#8211; <a href="http://www.portigal.com/news/new-article-the-cultures-of-design-at-dmi/" rel="nofollow" onclick="pageTracker._trackPageview('/outgoing/www.portigal.com/news/new-article-the-cultures-of-design-at-dmi/?referer=');">http://www.portigal.com/news/new-article-the-cultures-of-design-at-dmi/</a></p>
<p>Good discussion.</p>
<p>rgds,<br />
Dan</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Twitted by johnnyholland</title>
		<link>http://johnnyholland.org/2009/08/06/value/comment-page-1/#comment-22124</link>
		<dc:creator>Twitted by johnnyholland</dc:creator>
		<pubDate>Fri, 07 Aug 2009 12:41:02 +0000</pubDate>
		<guid isPermaLink="false">http://johnnyholland.org/?p=3040#comment-22124</guid>
		<description>[...] This post was Twitted by johnnyholland [...]</description>
		<content:encoded><![CDATA[<p>[...] This post was Twitted by johnnyholland [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: links for 2009-08-07 &#124; burningCat</title>
		<link>http://johnnyholland.org/2009/08/06/value/comment-page-1/#comment-22102</link>
		<dc:creator>links for 2009-08-07 &#124; burningCat</dc:creator>
		<pubDate>Fri, 07 Aug 2009 08:05:38 +0000</pubDate>
		<guid isPermaLink="false">http://johnnyholland.org/?p=3040#comment-22102</guid>
		<description>[...] The Value of Asking ‘Why?’ (tags: design process) [...]</description>
		<content:encoded><![CDATA[<p>[...] The Value of Asking ‘Why?’ (tags: design process) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeroen van Geel</title>
		<link>http://johnnyholland.org/2009/08/06/value/comment-page-1/#comment-22101</link>
		<dc:creator>Jeroen van Geel</dc:creator>
		<pubDate>Fri, 07 Aug 2009 08:03:16 +0000</pubDate>
		<guid isPermaLink="false">http://johnnyholland.org/?p=3040#comment-22101</guid>
		<description>@clark I think this position is changing (or needs to be changed)... it&#039;s not the product manager, but the design team that should be asking the questions. It&#039;s fundamental that the design team understands the &#039;Why?&#039; behind the product. And this shouldn&#039;t be passed over to them by a Powerpoint presentation, but they should feel and breath it.

By doing this research we start to understand. And this is especially important when you are designing products that are not unique (what 99% of us do all the time). The products we design, digital or physical, aren&#039;t revolutionary. So in order to stand out we must start diving into it and understand what makes it stand out in that particular field. These are often things you trully understand when you dove into the world. E.g.: finding out that people really don&#039;t like the product, but they love the service behind it. When your product manager tells this you get a feeling, but when you hear this from the users themselves... you will value it and defend it until the end. It will be a driving force instead of just a rule.</description>
		<content:encoded><![CDATA[<p>@clark I think this position is changing (or needs to be changed)&#8230; it&#8217;s not the product manager, but the design team that should be asking the questions. It&#8217;s fundamental that the design team understands the &#8216;Why?&#8217; behind the product. And this shouldn&#8217;t be passed over to them by a Powerpoint presentation, but they should feel and breath it.</p>
<p>By doing this research we start to understand. And this is especially important when you are designing products that are not unique (what 99% of us do all the time). The products we design, digital or physical, aren&#8217;t revolutionary. So in order to stand out we must start diving into it and understand what makes it stand out in that particular field. These are often things you trully understand when you dove into the world. E.g.: finding out that people really don&#8217;t like the product, but they love the service behind it. When your product manager tells this you get a feeling, but when you hear this from the users themselves&#8230; you will value it and defend it until the end. It will be a driving force instead of just a rule.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
