<?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: How much should Sales be involved in Product Development?</title>
	<atom:link href="http://ask.goodproductmanager.com/2008/03/05/how-much-should-sales-be-involved-in-product-development/feed/" rel="self" type="application/rss+xml" />
	<link>http://ask.goodproductmanager.com/2008/03/05/how-much-should-sales-be-involved-in-product-development/</link>
	<description>Your product management questions answered</description>
	<lastBuildDate>Mon, 08 Feb 2010 13:24:53 +0000</lastBuildDate>
	
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Bob Corrigan</title>
		<link>http://ask.goodproductmanager.com/2008/03/05/how-much-should-sales-be-involved-in-product-development/comment-page-1/#comment-133</link>
		<dc:creator>Bob Corrigan</dc:creator>
		<pubDate>Mon, 12 May 2008 17:45:50 +0000</pubDate>
		<guid isPermaLink="false">http://ask.goodproductmanager.com/2008/03/05/how-much-should-sales-be-involved-in-product-development/#comment-133</guid>
		<description>Ivan raises an interesting point - I can see that when you are a new entrant to the market and have followed the &quot;don&#039;t worry, be crappy&quot; rule and jumped into the market, getting real-time feedback from sales would be super-fabulous.  Especially if you leverage the feedback to get the sales guy to introduce you to the prospect, so you can ask questions and understand what the prospect is really asking for.</description>
		<content:encoded><![CDATA[<p>Ivan raises an interesting point &#8211; I can see that when you are a new entrant to the market and have followed the &#8220;don&#8217;t worry, be crappy&#8221; rule and jumped into the market, getting real-time feedback from sales would be super-fabulous.  Especially if you leverage the feedback to get the sales guy to introduce you to the prospect, so you can ask questions and understand what the prospect is really asking for.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Should Product Management let Sales drive product requirements? : Practical Product Management</title>
		<link>http://ask.goodproductmanager.com/2008/03/05/how-much-should-sales-be-involved-in-product-development/comment-page-1/#comment-35</link>
		<dc:creator>Should Product Management let Sales drive product requirements? : Practical Product Management</dc:creator>
		<pubDate>Sun, 16 Mar 2008 23:48:05 +0000</pubDate>
		<guid isPermaLink="false">http://ask.goodproductmanager.com/2008/03/05/how-much-should-sales-be-involved-in-product-development/#comment-35</guid>
		<description>[...] been a good discussion over the past couple of weeks at the How To Be A Good Product Manager and Ask A Good Product Manager blogs run by Jeff Lash on the topic of how Product Management can work effectively with [...]</description>
		<content:encoded><![CDATA[<p>[...] been a good discussion over the past couple of weeks at the How To Be A Good Product Manager and Ask A Good Product Manager blogs run by Jeff Lash on the topic of how Product Management can work effectively with [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Adam Bullied</title>
		<link>http://ask.goodproductmanager.com/2008/03/05/how-much-should-sales-be-involved-in-product-development/comment-page-1/#comment-29</link>
		<dc:creator>Adam Bullied</dc:creator>
		<pubDate>Tue, 11 Mar 2008 03:50:04 +0000</pubDate>
		<guid isPermaLink="false">http://ask.goodproductmanager.com/2008/03/05/how-much-should-sales-be-involved-in-product-development/#comment-29</guid>
		<description>Bob&#039;s assessment is very much the reality.

You have to provide Sales with some different materials than other functional groups within the organization. Especially the roadmap - no question.

This may be different at other organizations; my experience in the past has been, if you don&#039;t do this, you are setting yourself up for failure. Better safe than sorry.

You must listen to sales. They are on the front-lines and their input is valuable; to a point. The access to customers their relationships provide is fantastic. Sales people will only ever think about 3 things - their next 3 deals that they can close to give them commissions.

Again, there are exceptions to this rule and better safe than sorry.

I find it&#039;s always good to use your best judgment and always question quality. Chances are, you are certainly going to want to follow-up on feedback received before making decisions using it.</description>
		<content:encoded><![CDATA[<p>Bob&#8217;s assessment is very much the reality.</p>
<p>You have to provide Sales with some different materials than other functional groups within the organization. Especially the roadmap &#8211; no question.</p>
<p>This may be different at other organizations; my experience in the past has been, if you don&#8217;t do this, you are setting yourself up for failure. Better safe than sorry.</p>
<p>You must listen to sales. They are on the front-lines and their input is valuable; to a point. The access to customers their relationships provide is fantastic. Sales people will only ever think about 3 things &#8211; their next 3 deals that they can close to give them commissions.</p>
<p>Again, there are exceptions to this rule and better safe than sorry.</p>
<p>I find it&#8217;s always good to use your best judgment and always question quality. Chances are, you are certainly going to want to follow-up on feedback received before making decisions using it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Xavier</title>
		<link>http://ask.goodproductmanager.com/2008/03/05/how-much-should-sales-be-involved-in-product-development/comment-page-1/#comment-26</link>
		<dc:creator>Xavier</dc:creator>
		<pubDate>Mon, 10 Mar 2008 13:20:21 +0000</pubDate>
		<guid isPermaLink="false">http://ask.goodproductmanager.com/2008/03/05/how-much-should-sales-be-involved-in-product-development/#comment-26</guid>
		<description>Ivan,

I believe that we&#039;re all basically saying the same thing here.

The point is to listen to them without involving them too much, as in &quot;deciding what should be done or not&quot;.</description>
		<content:encoded><![CDATA[<p>Ivan,</p>
<p>I believe that we&#8217;re all basically saying the same thing here.</p>
<p>The point is to listen to them without involving them too much, as in &#8220;deciding what should be done or not&#8221;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ivan Chalif</title>
		<link>http://ask.goodproductmanager.com/2008/03/05/how-much-should-sales-be-involved-in-product-development/comment-page-1/#comment-25</link>
		<dc:creator>Ivan Chalif</dc:creator>
		<pubDate>Sun, 09 Mar 2008 06:09:41 +0000</pubDate>
		<guid isPermaLink="false">http://ask.goodproductmanager.com/2008/03/05/how-much-should-sales-be-involved-in-product-development/#comment-25</guid>
		<description>Hmmm...I don&#039;t fully agree with Bob&#039;s assessment. The caveats that he raises are all valid, but I don&#039;t think they are necessarily reasons to limit Sales exposure to the development process.

Sales is one among many voices that a Product Manager must listen to and consider as they plan and prioritize their products. Yes, they are self-serving and are most interested in their own deals, they provide a valuable mechanism for feeling out upcoming business requirements or new business opportunities for your industry.

Here&#039;s an example--at my company, we have a weekly meeting with the Sales leadership team to discuss requirements related to upcoming deals. This has two benefits: 

1. Sales has a clear and consistent chance to provide input about what&#039;s important in the field
2. I get to hear about what prospects want to do with my product

Number 1 limits the number of times that I have to hear the same request from multiple Sales reps and let&#039;s me point to a specific process for providing feedback. Number 2 gives me insights that are difficult and time-consuming to get on my own. If something interesting comes up, I can work with the Sales rep to talk to the prospect and get a better understanding of their future plans and that can help me make better choices for product priorities.

Don&#039;t think of Sales as a nuisance (I know, it&#039;s hard). Think of your Sales team as a tool that you can use to better understand the market.</description>
		<content:encoded><![CDATA[<p>Hmmm&#8230;I don&#8217;t fully agree with Bob&#8217;s assessment. The caveats that he raises are all valid, but I don&#8217;t think they are necessarily reasons to limit Sales exposure to the development process.</p>
<p>Sales is one among many voices that a Product Manager must listen to and consider as they plan and prioritize their products. Yes, they are self-serving and are most interested in their own deals, they provide a valuable mechanism for feeling out upcoming business requirements or new business opportunities for your industry.</p>
<p>Here&#8217;s an example&#8211;at my company, we have a weekly meeting with the Sales leadership team to discuss requirements related to upcoming deals. This has two benefits: </p>
<p>1. Sales has a clear and consistent chance to provide input about what&#8217;s important in the field<br />
2. I get to hear about what prospects want to do with my product</p>
<p>Number 1 limits the number of times that I have to hear the same request from multiple Sales reps and let&#8217;s me point to a specific process for providing feedback. Number 2 gives me insights that are difficult and time-consuming to get on my own. If something interesting comes up, I can work with the Sales rep to talk to the prospect and get a better understanding of their future plans and that can help me make better choices for product priorities.</p>
<p>Don&#8217;t think of Sales as a nuisance (I know, it&#8217;s hard). Think of your Sales team as a tool that you can use to better understand the market.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Xavier</title>
		<link>http://ask.goodproductmanager.com/2008/03/05/how-much-should-sales-be-involved-in-product-development/comment-page-1/#comment-19</link>
		<dc:creator>Xavier</dc:creator>
		<pubDate>Thu, 06 Mar 2008 07:08:37 +0000</pubDate>
		<guid isPermaLink="false">http://ask.goodproductmanager.com/2008/03/05/how-much-should-sales-be-involved-in-product-development/#comment-19</guid>
		<description>Wow!

Great Answer!

I actually do agree with you, and it was never in my intentions to keep the mushr .. em .. the salesforce in the dark! ;o)

Thanks Bob.</description>
		<content:encoded><![CDATA[<p>Wow!</p>
<p>Great Answer!</p>
<p>I actually do agree with you, and it was never in my intentions to keep the mushr .. em .. the salesforce in the dark! ;o)</p>
<p>Thanks Bob.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
