<?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 can I avoid cannibalization with a new product?</title>
	<atom:link href="http://ask.goodproductmanager.com/2009/06/01/how-can-i-avoid-cannibalization-with-a-new-product/feed/" rel="self" type="application/rss+xml" />
	<link>http://ask.goodproductmanager.com/2009/06/01/how-can-i-avoid-cannibalization-with-a-new-product/</link>
	<description>Your product management questions answered</description>
	<lastBuildDate>Tue, 13 Dec 2011 18:48:32 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: ban</title>
		<link>http://ask.goodproductmanager.com/2009/06/01/how-can-i-avoid-cannibalization-with-a-new-product/comment-page-1/#comment-83537</link>
		<dc:creator>ban</dc:creator>
		<pubDate>Fri, 30 Apr 2010 03:36:31 +0000</pubDate>
		<guid isPermaLink="false">http://ask.goodproductmanager.com/?p=123#comment-83537</guid>
		<description>I think you should offer an extra with the older product once you have introduced the new version, keep the price of the older product less than the newer one but add something to it that can work  with it , for example a printer needs a ink cartradge to work, there are two products that work together. depending on what your product is think of something you can add to it to make it as good as the new version. 

the new version may have new features but the old one has older feature but at the same time it has an extra product  on the side that appeals as much as the new version. 

in other words it&#039;s like buy one get sumthing free 

if that makes sense. 
i am only a uni student  doing business and i dont know how much  help i contributed , but putting myself in the position of the customer, this perspective would be helpful. may be even do a survey ? ..</description>
		<content:encoded><![CDATA[<p>I think you should offer an extra with the older product once you have introduced the new version, keep the price of the older product less than the newer one but add something to it that can work  with it , for example a printer needs a ink cartradge to work, there are two products that work together. depending on what your product is think of something you can add to it to make it as good as the new version. </p>
<p>the new version may have new features but the old one has older feature but at the same time it has an extra product  on the side that appeals as much as the new version. </p>
<p>in other words it&#8217;s like buy one get sumthing free </p>
<p>if that makes sense.<br />
i am only a uni student  doing business and i dont know how much  help i contributed , but putting myself in the position of the customer, this perspective would be helpful. may be even do a survey ? ..</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Locke</title>
		<link>http://ask.goodproductmanager.com/2009/06/01/how-can-i-avoid-cannibalization-with-a-new-product/comment-page-1/#comment-9059</link>
		<dc:creator>David Locke</dc:creator>
		<pubDate>Mon, 29 Jun 2009 18:09:09 +0000</pubDate>
		<guid isPermaLink="false">http://ask.goodproductmanager.com/?p=123#comment-9059</guid>
		<description>I would wonder why you need a new product. With an appropriate architecture, you can sell a plug-in or supplemental web services to features without modifying your underlying product. 

Doing this would mean that you have to have an appropriate sales force structure, and other organizational impacts. The needed changes might move beyond the scope of the product manager, or it may change the scope of the offer and the product manager&#039;s responsibilities.</description>
		<content:encoded><![CDATA[<p>I would wonder why you need a new product. With an appropriate architecture, you can sell a plug-in or supplemental web services to features without modifying your underlying product. </p>
<p>Doing this would mean that you have to have an appropriate sales force structure, and other organizational impacts. The needed changes might move beyond the scope of the product manager, or it may change the scope of the offer and the product manager&#8217;s responsibilities.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: PuristProductManagement</title>
		<link>http://ask.goodproductmanager.com/2009/06/01/how-can-i-avoid-cannibalization-with-a-new-product/comment-page-1/#comment-6712</link>
		<dc:creator>PuristProductManagement</dc:creator>
		<pubDate>Wed, 10 Jun 2009 15:28:16 +0000</pubDate>
		<guid isPermaLink="false">http://ask.goodproductmanager.com/?p=123#comment-6712</guid>
		<description>I&#039;ve come across this problem multiple times, and the answers really depend on the context of the product, but in essence I agree with Bob. In the past the first point of call for me has been to investigate whether there are incremental release benefits that can be drip fed, although this sometimes dilutes the marketing message</description>
		<content:encoded><![CDATA[<p>I&#8217;ve come across this problem multiple times, and the answers really depend on the context of the product, but in essence I agree with Bob. In the past the first point of call for me has been to investigate whether there are incremental release benefits that can be drip fed, although this sometimes dilutes the marketing message</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Raj</title>
		<link>http://ask.goodproductmanager.com/2009/06/01/how-can-i-avoid-cannibalization-with-a-new-product/comment-page-1/#comment-6098</link>
		<dc:creator>Raj</dc:creator>
		<pubDate>Wed, 03 Jun 2009 01:41:49 +0000</pubDate>
		<guid isPermaLink="false">http://ask.goodproductmanager.com/?p=123#comment-6098</guid>
		<description>Great points by Bob.

Just like Bob, I too feel like I have insufficient understanding of the question. That said, here is a point I&#039;d like to share.

If the new product is just an upgrade over the current product and is sold for the same price - then prospective customers may want to wait until the new version to purchase. One possible way to overcome this issue is to offer them free upgrade to new versions of the product for a period of N months after their original purchase.

- Raj
&lt;a href=&quot;http://www.accompa.com&quot; rel=&quot;nofollow&quot;&gt;Accompa - Affordable Requirements Management Tool for Product Managers&lt;/a&gt;</description>
		<content:encoded><![CDATA[<p>Great points by Bob.</p>
<p>Just like Bob, I too feel like I have insufficient understanding of the question. That said, here is a point I&#8217;d like to share.</p>
<p>If the new product is just an upgrade over the current product and is sold for the same price &#8211; then prospective customers may want to wait until the new version to purchase. One possible way to overcome this issue is to offer them free upgrade to new versions of the product for a period of N months after their original purchase.</p>
<p>- Raj<br />
<a href="http://www.accompa.com" rel="nofollow">Accompa &#8211; Affordable Requirements Management Tool for Product Managers</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>

