<?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: Product Vision and Corporate Culture</title>
	<atom:link href="http://effectivus.com/2009/03/product-vision-and-corporate-culture/feed/" rel="self" type="application/rss+xml" />
	<link>http://effectivus.com/2009/03/product-vision-and-corporate-culture/?utm_source=rss&amp;utm_medium=rss&amp;utm_campaign=rss</link>
	<description>Technology product development, management &#38; marketing</description>
	<lastBuildDate>Wed, 28 Jul 2010 07:05:13 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: Chris</title>
		<link>http://effectivus.com/2009/03/product-vision-and-corporate-culture/comment-page-1/#comment-18</link>
		<dc:creator>Chris</dc:creator>
		<pubDate>Wed, 25 Mar 2009 07:22:06 +0000</pubDate>
		<guid isPermaLink="false">http://effectivus.com/?p=386#comment-18</guid>
		<description>Thanks Andy, it makes a lot of sense to me.
I think the major problem about creating a truly &lt;em&gt;new&lt;/em&gt; product is that you can&#039;t know what it is until you&#039;ve built it, or even later.  That is why so often it is second or third generation products which really hit the spot whilst first generation ones end up in museums, see: &lt;a href=&quot;http://effectivus.com/2009/02/first-mover-advantage-or-winner’s-curse/&quot; rel=&quot;nofollow&quot;&gt;First-Mover Advantage or Winner’s Curse?&lt;/a&gt;
I think of the process as a design one; creative, iterative, exploring and learning.  More on that another time.
Chris</description>
		<content:encoded><![CDATA[<p>Thanks Andy, it makes a lot of sense to me.<br />
I think the major problem about creating a truly <em>new</em> product is that you can&#8217;t know what it is until you&#8217;ve built it, or even later.  That is why so often it is second or third generation products which really hit the spot whilst first generation ones end up in museums, see: <a href="http://effectivus.com/2009/02/first-mover-advantage-or-winner’s-curse/" rel="nofollow">First-Mover Advantage or Winner’s Curse?</a><br />
I think of the process as a design one; creative, iterative, exploring and learning.  More on that another time.<br />
Chris</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andy Ballingall</title>
		<link>http://effectivus.com/2009/03/product-vision-and-corporate-culture/comment-page-1/#comment-17</link>
		<dc:creator>Andy Ballingall</dc:creator>
		<pubDate>Tue, 24 Mar 2009 22:44:55 +0000</pubDate>
		<guid isPermaLink="false">http://effectivus.com/?p=386#comment-17</guid>
		<description>Though running the risk of making a point which itself contains a list (!), two things which have helped efforts I&#039;ve been associated with deliver great products are:

a) Starting by imagining people using your product on a daily basis .

b) Having the creative flexibility and freedom to put together a prototype which works towards that vision, even though the primary benefit of this prototype may in the end only be to understand more fully the challenge ahead.

The first of these requires imagination, and the second of these requires faith in the right solution being found even though you don&#039;t yet know what it&#039;ll be. These two elements are often lacking in corporate culture.

One of the problems with well specified long lists of requirements being set at the start and adhered to religiously is that very often, you simply aren&#039;t in a position to be an expert on what the right requirements are in all but a vague form.

 The world is littered with solutions whose development was rigorously executed with little regard to lessons learned on the journey, and which as a consqequence faithfully reflect the partial ignorance about the challenge held by he team at the outset.

None of this helps when you need things done by a specific time, but reality often kicks in anyway when an unrealistic schedule yields an unsellable product.

(Does any of this make sense?)

Cheers!
Andy</description>
		<content:encoded><![CDATA[<p>Though running the risk of making a point which itself contains a list (!), two things which have helped efforts I&#8217;ve been associated with deliver great products are:</p>
<p>a) Starting by imagining people using your product on a daily basis .</p>
<p>b) Having the creative flexibility and freedom to put together a prototype which works towards that vision, even though the primary benefit of this prototype may in the end only be to understand more fully the challenge ahead.</p>
<p>The first of these requires imagination, and the second of these requires faith in the right solution being found even though you don&#8217;t yet know what it&#8217;ll be. These two elements are often lacking in corporate culture.</p>
<p>One of the problems with well specified long lists of requirements being set at the start and adhered to religiously is that very often, you simply aren&#8217;t in a position to be an expert on what the right requirements are in all but a vague form.</p>
<p> The world is littered with solutions whose development was rigorously executed with little regard to lessons learned on the journey, and which as a consqequence faithfully reflect the partial ignorance about the challenge held by he team at the outset.</p>
<p>None of this helps when you need things done by a specific time, but reality often kicks in anyway when an unrealistic schedule yields an unsellable product.</p>
<p>(Does any of this make sense?)</p>
<p>Cheers!<br />
Andy</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris</title>
		<link>http://effectivus.com/2009/03/product-vision-and-corporate-culture/comment-page-1/#comment-5</link>
		<dc:creator>Chris</dc:creator>
		<pubDate>Mon, 09 Mar 2009 09:51:16 +0000</pubDate>
		<guid isPermaLink="false">http://effectivus.com/?p=386#comment-5</guid>
		<description>Thanks Carl.  Yes, hiring the right people... that is so important.  I mused on some different approaches here: http://effectivus.com/2009/02/shine-your-shoes-go-barefoot/ enjoy!</description>
		<content:encoded><![CDATA[<p>Thanks Carl.  Yes, hiring the right people&#8230; that is so important.  I mused on some different approaches here: <a href="http://effectivus.com/2009/02/shine-your-shoes-go-barefoot/" rel="nofollow">http://effectivus.com/2009/02/shine-your-shoes-go-barefoot/</a> enjoy!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Carl</title>
		<link>http://effectivus.com/2009/03/product-vision-and-corporate-culture/comment-page-1/#comment-4</link>
		<dc:creator>Carl</dc:creator>
		<pubDate>Mon, 09 Mar 2009 08:42:22 +0000</pubDate>
		<guid isPermaLink="false">http://effectivus.com/?p=386#comment-4</guid>
		<description>Interesting post Chris. I particularly like &quot;we should not have to define every requirement in immense detail because the overall objectives are clear and smart employees will figure out how best to fulfill them.  Maybe they’ll do so better than we would.&quot;

I think this is the crux of it. If you go to the trouble and financial commitment of hiring the right people, you need to trust and empower them to work out this stuff out for you.</description>
		<content:encoded><![CDATA[<p>Interesting post Chris. I particularly like &#8220;we should not have to define every requirement in immense detail because the overall objectives are clear and smart employees will figure out how best to fulfill them.  Maybe they’ll do so better than we would.&#8221;</p>
<p>I think this is the crux of it. If you go to the trouble and financial commitment of hiring the right people, you need to trust and empower them to work out this stuff out for you.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
