<?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: Lessons Learned in Product Management</title>
	<atom:link href="http://shapingsoftware.com/2008/12/09/lessons-learned-in-product-management/feed/" rel="self" type="application/rss+xml" />
	<link>http://shapingsoftware.com/2008/12/09/lessons-learned-in-product-management/</link>
	<description>Patterns and Practices for Software Success.</description>
	<pubDate>Thu, 17 May 2012 20:19:54 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Bob</title>
		<link>http://shapingsoftware.com/2008/12/09/lessons-learned-in-product-management/comment-page-1/#comment-18135</link>
		<dc:creator>Bob</dc:creator>
		<pubDate>Thu, 11 Dec 2008 14:12:21 +0000</pubDate>
		<guid isPermaLink="false">http://shapingsoftware.com/2008/12/09/lessons-learned-in-product-management/#comment-18135</guid>
		<description>The term "Voice of the Customer" is used too many times to refer to either market research in general or to the specific features or solutions that a customer desires. More properly, the Voice of the Customer is the statement of the customer's wants and needs, not a specific solution to those needs. Building a product that customers will want to buy means transforming those needs into product specifications. You don't want a product designed by your customers, you want a product &lt;i&gt;inspired&lt;/i&gt; by your customers. That means thinking about wants and needs in a different way. For example, see the excellent article by Gerry Katz from the PDMA's Visions Magazine (http://www.ams-inc.com/pdf/VisionsMar08Katz.pdf).</description>
		<content:encoded><![CDATA[<p>The term &#8220;Voice of the Customer&#8221; is used too many times to refer to either market research in general or to the specific features or solutions that a customer desires. More properly, the Voice of the Customer is the statement of the customer&#8217;s wants and needs, not a specific solution to those needs. Building a product that customers will want to buy means transforming those needs into product specifications. You don&#8217;t want a product designed by your customers, you want a product <i>inspired</i> by your customers. That means thinking about wants and needs in a different way. For example, see the excellent article by Gerry Katz from the PDMA&#8217;s Visions Magazine (http://www.ams-inc.com/pdf/VisionsMar08Katz.pdf).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Product Management Reader: 11Dec08 &#124; The Productologist: Exploring the Depths of Product Management</title>
		<link>http://shapingsoftware.com/2008/12/09/lessons-learned-in-product-management/comment-page-1/#comment-18125</link>
		<dc:creator>Product Management Reader: 11Dec08 &#124; The Productologist: Exploring the Depths of Product Management</dc:creator>
		<pubDate>Thu, 11 Dec 2008 13:25:00 +0000</pubDate>
		<guid isPermaLink="false">http://shapingsoftware.com/2008/12/09/lessons-learned-in-product-management/#comment-18125</guid>
		<description>[...]  Lessons Learned in Product Management [Shaping Software] [...]</description>
		<content:encoded><![CDATA[<p>[...]  Lessons Learned in Product Management [Shaping Software] [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: stevflaming</title>
		<link>http://shapingsoftware.com/2008/12/09/lessons-learned-in-product-management/comment-page-1/#comment-17789</link>
		<dc:creator>stevflaming</dc:creator>
		<pubDate>Wed, 10 Dec 2008 06:06:38 +0000</pubDate>
		<guid isPermaLink="false">http://shapingsoftware.com/2008/12/09/lessons-learned-in-product-management/#comment-17789</guid>
		<description>this post tell about Product Manager has 2 roles – i) Outbound: Communicating the product and the vision out to the customers and ii) Inbound: Feeding customer and market insight into the development teams to better the product, build a new product, acquire a new product, or kill the product.</description>
		<content:encoded><![CDATA[<p>this post tell about Product Manager has 2 roles – i) Outbound: Communicating the product and the vision out to the customers and ii) Inbound: Feeding customer and market insight into the development teams to better the product, build a new product, acquire a new product, or kill the product.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alik Levin</title>
		<link>http://shapingsoftware.com/2008/12/09/lessons-learned-in-product-management/comment-page-1/#comment-17719</link>
		<dc:creator>Alik Levin</dc:creator>
		<pubDate>Tue, 09 Dec 2008 23:48:45 +0000</pubDate>
		<guid isPermaLink="false">http://shapingsoftware.com/2008/12/09/lessons-learned-in-product-management/#comment-17719</guid>
		<description>Rick, thanks for the insights! 
Really good stuff. It only proves once again Weinberg's second law of consulting - "No matter how it looks at first, it's always a people problem."
We are all consultants and we are all "consultees".
I loved "Establish credibility" the most. Here in MCS it is no different - we have our biz folks and consultants. 
What you described in your post is 100% applicable here in the field
Thanks for sharing</description>
		<content:encoded><![CDATA[<p>Rick, thanks for the insights!<br />
Really good stuff. It only proves once again Weinberg&#8217;s second law of consulting - &#8220;No matter how it looks at first, it&#8217;s always a people problem.&#8221;<br />
We are all consultants and we are all &#8220;consultees&#8221;.<br />
I loved &#8220;Establish credibility&#8221; the most. Here in MCS it is no different - we have our biz folks and consultants.<br />
What you described in your post is 100% applicable here in the field<br />
Thanks for sharing</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: J.D. Meier's Blog : Lessons Learned in Product Management on Shaping Software</title>
		<link>http://shapingsoftware.com/2008/12/09/lessons-learned-in-product-management/comment-page-1/#comment-17696</link>
		<dc:creator>J.D. Meier's Blog : Lessons Learned in Product Management on Shaping Software</dc:creator>
		<pubDate>Tue, 09 Dec 2008 21:43:37 +0000</pubDate>
		<guid isPermaLink="false">http://shapingsoftware.com/2008/12/09/lessons-learned-in-product-management/#comment-17696</guid>
		<description>[...] have a guest post at Shaping Software by Rick Samona on Lessons Learned in Product Management.&#160; Rick's actually one of the most effective Microsoft product managers I know.&#160; I had the [...]</description>
		<content:encoded><![CDATA[<p>[...] have a guest post at Shaping Software by Rick Samona on Lessons Learned in Product Management.&#160; Rick&#8217;s actually one of the most effective Microsoft product managers I know.&#160; I had the [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

