<?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: Consider your market window as part of your product strategy</title>
	<atom:link href="http://www.goodproductmanager.com/2009/03/31/consider-your-market-window-as-part-of-your-product-strategy/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.goodproductmanager.com/2009/03/31/consider-your-market-window-as-part-of-your-product-strategy/</link>
	<description>A blog with tips on product management and related topics. Written by Jeff Lash, a product manager in St. Louis, MO</description>
	<lastBuildDate>Sun, 07 Mar 2010 10:14:56 -0800</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Passionate PM</title>
		<link>http://www.goodproductmanager.com/2009/03/31/consider-your-market-window-as-part-of-your-product-strategy/comment-page-1/#comment-45550</link>
		<dc:creator>Passionate PM</dc:creator>
		<pubDate>Thu, 16 Jul 2009 08:11:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.goodproductmanager.com/?p=213#comment-45550</guid>
		<description>This is a great article for any Product Manager.</description>
		<content:encoded><![CDATA[<p>This is a great article for any Product Manager.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: PuristProductManagement</title>
		<link>http://www.goodproductmanager.com/2009/03/31/consider-your-market-window-as-part-of-your-product-strategy/comment-page-1/#comment-35820</link>
		<dc:creator>PuristProductManagement</dc:creator>
		<pubDate>Wed, 10 Jun 2009 16:12:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.goodproductmanager.com/?p=213#comment-35820</guid>
		<description>Yes completely agree with the post, but timing is as important as resource planning. Getting a product to market in the ideal world should be about getting the product out as soon as development is complete so as to be able to capitalise the expense as soon as possible. However, I feel this should be more about delayed development than delayed release. Timing the product launch and then working backwards from that point has often helped me get products to market at the right time, not the soonest time. 

Great post!</description>
		<content:encoded><![CDATA[<p>Yes completely agree with the post, but timing is as important as resource planning. Getting a product to market in the ideal world should be about getting the product out as soon as development is complete so as to be able to capitalise the expense as soon as possible. However, I feel this should be more about delayed development than delayed release. Timing the product launch and then working backwards from that point has often helped me get products to market at the right time, not the soonest time. </p>
<p>Great post!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Locke</title>
		<link>http://www.goodproductmanager.com/2009/03/31/consider-your-market-window-as-part-of-your-product-strategy/comment-page-1/#comment-29108</link>
		<dc:creator>David Locke</dc:creator>
		<pubDate>Sun, 24 May 2009 20:35:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.goodproductmanager.com/?p=213#comment-29108</guid>
		<description>Marshall, Discontinuous/Radical innovations must be adopted. Technology adoption is a slow process. You productize your technology for a single client. Then, you sell that technology into the client&#039;s vertical. 

When you say &quot;only very few high end customers,&quot; it sounds like you are talking about continuous innovations in the consumer market. This is a matter of standardizing the technology, so the price falls and your customer base broadens. 

Early adopters is a term that has two meanings. The first paragraph talks about the B2B early adopter while the second paragraph talks about the B2C early adopter. Many people don&#039;t keep these groups straight. 

The B2B EA happens at the birth of a category, while the B2C EA happens in the consumer market, which is also the late mainstream market for B2B products, which these days have been migrated to SaaS.</description>
		<content:encoded><![CDATA[<p>Marshall, Discontinuous/Radical innovations must be adopted. Technology adoption is a slow process. You productize your technology for a single client. Then, you sell that technology into the client&#8217;s vertical. </p>
<p>When you say &#8220;only very few high end customers,&#8221; it sounds like you are talking about continuous innovations in the consumer market. This is a matter of standardizing the technology, so the price falls and your customer base broadens. </p>
<p>Early adopters is a term that has two meanings. The first paragraph talks about the B2B early adopter while the second paragraph talks about the B2C early adopter. Many people don&#8217;t keep these groups straight. </p>
<p>The B2B EA happens at the birth of a category, while the B2C EA happens in the consumer market, which is also the late mainstream market for B2B products, which these days have been migrated to SaaS.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Marshall</title>
		<link>http://www.goodproductmanager.com/2009/03/31/consider-your-market-window-as-part-of-your-product-strategy/comment-page-1/#comment-27083</link>
		<dc:creator>Marshall</dc:creator>
		<pubDate>Tue, 19 May 2009 07:33:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.goodproductmanager.com/?p=213#comment-27083</guid>
		<description>If innovations are just ahead of their time, only very few high end customers could try to use them, what coule be expected to do next step?</description>
		<content:encoded><![CDATA[<p>If innovations are just ahead of their time, only very few high end customers could try to use them, what coule be expected to do next step?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Locke</title>
		<link>http://www.goodproductmanager.com/2009/03/31/consider-your-market-window-as-part-of-your-product-strategy/comment-page-1/#comment-24848</link>
		<dc:creator>David Locke</dc:creator>
		<pubDate>Mon, 27 Apr 2009 01:47:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.goodproductmanager.com/?p=213#comment-24848</guid>
		<description>I worked in a place that moved from geek to consumer markets. The geeks screamed, so on the next release they moved from consumer back to geek. 

The underlying problem existed in both markets, but in terms of product expectations the customers very far apart. So I ask you, which customer are you going to listen to?

Granted, they should have renamed the product along with the redesign and launched it as a separate consumer product. Still, you have to know if you customers are different the next time launch. 

The decison here was consious, no market timing involved, but yes, under Moore&#039;s paradigm, you have to make a decision to enter the next market. Then, you have to enter it as if it matters. That may take a much larger effort than revising the user interface.</description>
		<content:encoded><![CDATA[<p>I worked in a place that moved from geek to consumer markets. The geeks screamed, so on the next release they moved from consumer back to geek. </p>
<p>The underlying problem existed in both markets, but in terms of product expectations the customers very far apart. So I ask you, which customer are you going to listen to?</p>
<p>Granted, they should have renamed the product along with the redesign and launched it as a separate consumer product. Still, you have to know if you customers are different the next time launch. </p>
<p>The decison here was consious, no market timing involved, but yes, under Moore&#8217;s paradigm, you have to make a decision to enter the next market. Then, you have to enter it as if it matters. That may take a much larger effort than revising the user interface.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dr. Jim Anderson</title>
		<link>http://www.goodproductmanager.com/2009/03/31/consider-your-market-window-as-part-of-your-product-strategy/comment-page-1/#comment-24363</link>
		<dc:creator>Dr. Jim Anderson</dc:creator>
		<pubDate>Mon, 20 Apr 2009 21:31:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.goodproductmanager.com/?p=213#comment-24363</guid>
		<description>Good points all around; however, this sure sounds like trying to &quot;time the market&quot; with stock picks. Maybe a better way to look at things is to clearly identify the problem that your product solves.

This changes the question that you are trying to answer: it&#039;s no longer what is the status of the market window, but rather &quot;does this problem still exist for my customer&quot;. 


- Dr. Jim Anderson
&lt;a href=&quot;http://www.TheAccidentalPM.com/&quot; title=&quot;The Accidental Product Manager Blog&quot; rel=&quot;nofollow&quot;&gt;The Accidental PM Blog&lt;/a&gt;
&quot;Home Of The Billion Dollar Product Manager&quot;</description>
		<content:encoded><![CDATA[<p>Good points all around; however, this sure sounds like trying to &#8220;time the market&#8221; with stock picks. Maybe a better way to look at things is to clearly identify the problem that your product solves.</p>
<p>This changes the question that you are trying to answer: it&#8217;s no longer what is the status of the market window, but rather &#8220;does this problem still exist for my customer&#8221;. </p>
<p>- Dr. Jim Anderson<br />
<a href="http://www.TheAccidentalPM.com/" title="The Accidental Product Manager Blog" rel="nofollow">The Accidental PM Blog</a><br />
&#8220;Home Of The Billion Dollar Product Manager&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Locke</title>
		<link>http://www.goodproductmanager.com/2009/03/31/consider-your-market-window-as-part-of-your-product-strategy/comment-page-1/#comment-24008</link>
		<dc:creator>David Locke</dc:creator>
		<pubDate>Tue, 14 Apr 2009 17:23:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.goodproductmanager.com/?p=213#comment-24008</guid>
		<description>Moore&#039;s technology adoption lifecycle (TALC)predicates a series of market windows. In each the customer is different. Listening to the customer is something that you need to segment, so you listen within and not across market windows. 

The TALC is also, contrary to what Moore said, an asynchronous clock. You can&#039;t set a firm date, but there is a process, a sequence. You may have to wait for the market. 

Concepts come into a firm or a market. They come from a logistics system: inbound concepts, outbound products. Virtual inventories don&#039;t have the same costs as physical inventories, so JIT can be overkill. 

As you plan your releases, consider the trends that are driving adoption and de-adoption. When can we enter? When must we leave? What duration isn&#039;t worth the costs? 

A proactive time stance lets you influence the market. A proactive stance lets you shock the market if you like that approach, but that&#039;s only useful for sustaining innovation. A proactive stance means that you have time to build up a sequence of moves made public only to your advantage. Proactive can enable you to outdisance the fast followers by having them churn their requirements. 

You can keep your developers busy without releasing. There is always more to do.</description>
		<content:encoded><![CDATA[<p>Moore&#8217;s technology adoption lifecycle (TALC)predicates a series of market windows. In each the customer is different. Listening to the customer is something that you need to segment, so you listen within and not across market windows. </p>
<p>The TALC is also, contrary to what Moore said, an asynchronous clock. You can&#8217;t set a firm date, but there is a process, a sequence. You may have to wait for the market. </p>
<p>Concepts come into a firm or a market. They come from a logistics system: inbound concepts, outbound products. Virtual inventories don&#8217;t have the same costs as physical inventories, so JIT can be overkill. </p>
<p>As you plan your releases, consider the trends that are driving adoption and de-adoption. When can we enter? When must we leave? What duration isn&#8217;t worth the costs? </p>
<p>A proactive time stance lets you influence the market. A proactive stance lets you shock the market if you like that approach, but that&#8217;s only useful for sustaining innovation. A proactive stance means that you have time to build up a sequence of moves made public only to your advantage. Proactive can enable you to outdisance the fast followers by having them churn their requirements. </p>
<p>You can keep your developers busy without releasing. There is always more to do.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Saikat Sinha</title>
		<link>http://www.goodproductmanager.com/2009/03/31/consider-your-market-window-as-part-of-your-product-strategy/comment-page-1/#comment-23169</link>
		<dc:creator>Saikat Sinha</dc:creator>
		<pubDate>Thu, 02 Apr 2009 05:26:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.goodproductmanager.com/?p=213#comment-23169</guid>
		<description>I completely agree with JeffLash&#039;s last paragraph. Superbly said!!

If you are a new bee in the market, you should always try to ride on first mover&#039;s  publicity stunts. It always gives you the benefit of educated market. Now you don’t need to spend your tight budget and time on educating them without guarantee of success. 

Till the time your target market is getting educated you should focus on improving value proposition of the product while keeping your eyes wide open to look for the optimum time to launch your product.  It’s more like a tiger&#039;s hunting strategy. It always waits for the right time to jump on its prey...</description>
		<content:encoded><![CDATA[<p>I completely agree with JeffLash&#8217;s last paragraph. Superbly said!!</p>
<p>If you are a new bee in the market, you should always try to ride on first mover&#8217;s  publicity stunts. It always gives you the benefit of educated market. Now you don’t need to spend your tight budget and time on educating them without guarantee of success. </p>
<p>Till the time your target market is getting educated you should focus on improving value proposition of the product while keeping your eyes wide open to look for the optimum time to launch your product.  It’s more like a tiger&#8217;s hunting strategy. It always waits for the right time to jump on its prey&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeff Lash</title>
		<link>http://www.goodproductmanager.com/2009/03/31/consider-your-market-window-as-part-of-your-product-strategy/comment-page-1/#comment-23156</link>
		<dc:creator>Jeff Lash</dc:creator>
		<pubDate>Wed, 01 Apr 2009 22:40:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.goodproductmanager.com/?p=213#comment-23156</guid>
		<description>My intention wasn&#039;t to argue that you shouldn&#039;t release a product early, though I realize now that is probably the main message that comes out of it. 

My point was more to understand the market window and consider that as part of the business case -- in some cases, the window may already be closed and no matter how fast you can build and release the product, you&#039;re going to have a tough time getting any traction.

There may be good reasons to speed up a product&#039;s release to take advantage of the external situation. For example, if you are building a product for Realtors, maybe you originally planned to release it later this year when you expected the real estate market to rebound. Releasing a new product when sales are slow may be a tough sell. However, with historically low mortgage rates and the new first-time home buyer credit, real estate activity has started to increase again, so the market window may be open earlier than you originally thought.

Alternatively, if you were planning on releasing a new iPhone/iTouch App in the coming months, there may be good cause to delay your release and take advantage of the new iPhone 3.0 software which is planned for release this summer. That also may provide the additional advantage of allowing you to ride the publicity that always comes with a new Apple product or software release.</description>
		<content:encoded><![CDATA[<p>My intention wasn&#8217;t to argue that you shouldn&#8217;t release a product early, though I realize now that is probably the main message that comes out of it. </p>
<p>My point was more to understand the market window and consider that as part of the business case &#8212; in some cases, the window may already be closed and no matter how fast you can build and release the product, you&#8217;re going to have a tough time getting any traction.</p>
<p>There may be good reasons to speed up a product&#8217;s release to take advantage of the external situation. For example, if you are building a product for Realtors, maybe you originally planned to release it later this year when you expected the real estate market to rebound. Releasing a new product when sales are slow may be a tough sell. However, with historically low mortgage rates and the new first-time home buyer credit, real estate activity has started to increase again, so the market window may be open earlier than you originally thought.</p>
<p>Alternatively, if you were planning on releasing a new iPhone/iTouch App in the coming months, there may be good cause to delay your release and take advantage of the new iPhone 3.0 software which is planned for release this summer. That also may provide the additional advantage of allowing you to ride the publicity that always comes with a new Apple product or software release.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Roger L. Cauvin</title>
		<link>http://www.goodproductmanager.com/2009/03/31/consider-your-market-window-as-part-of-your-product-strategy/comment-page-1/#comment-23153</link>
		<dc:creator>Roger L. Cauvin</dc:creator>
		<pubDate>Wed, 01 Apr 2009 21:47:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.goodproductmanager.com/?p=213#comment-23153</guid>
		<description>Another reason to release early is to &quot;test&quot; every aspect of the product: the benefits of the product, the sales and pricing, and the positioning.

But it&#039;s true that you severely undermine your chances for long-term success if you create a bad first impression.  To the extent possible, you want the first impressions to reflect the intended position of the product in the marketplace and the brand perception you intend to instill in the mind of customers.

Thus I&#039;d say it can be advantageous to release early if some combination of the following conditions exist:

1. The product can fulfill its brand promise.
2. You manage expectations.
3. You release to a small subset of the target market (which then may render the release a beta of sorts).

Roger</description>
		<content:encoded><![CDATA[<p>Another reason to release early is to &#8220;test&#8221; every aspect of the product: the benefits of the product, the sales and pricing, and the positioning.</p>
<p>But it&#8217;s true that you severely undermine your chances for long-term success if you create a bad first impression.  To the extent possible, you want the first impressions to reflect the intended position of the product in the marketplace and the brand perception you intend to instill in the mind of customers.</p>
<p>Thus I&#8217;d say it can be advantageous to release early if some combination of the following conditions exist:</p>
<p>1. The product can fulfill its brand promise.<br />
2. You manage expectations.<br />
3. You release to a small subset of the target market (which then may render the release a beta of sorts).</p>
<p>Roger</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brendan</title>
		<link>http://www.goodproductmanager.com/2009/03/31/consider-your-market-window-as-part-of-your-product-strategy/comment-page-1/#comment-23144</link>
		<dc:creator>Brendan</dc:creator>
		<pubDate>Wed, 01 Apr 2009 14:57:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.goodproductmanager.com/?p=213#comment-23144</guid>
		<description>Great post, a similar problem that happens to us a lot is we build a product plan around taking advantage of a market opportunity (our business is cyclical), we miss the window because of software delays or some other reason, then we release as soon as we are finished because the product, which will now have significantly less impact in the market, is clogging up our product pipeline. In this case, everything that determines our release time is dictated by our internal perceptions of priority. Sigh.</description>
		<content:encoded><![CDATA[<p>Great post, a similar problem that happens to us a lot is we build a product plan around taking advantage of a market opportunity (our business is cyclical), we miss the window because of software delays or some other reason, then we release as soon as we are finished because the product, which will now have significantly less impact in the market, is clogging up our product pipeline. In this case, everything that determines our release time is dictated by our internal perceptions of priority. Sigh.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Consider your market window as part of your product strategy &#171; It&#8217;s the software, stupid!</title>
		<link>http://www.goodproductmanager.com/2009/03/31/consider-your-market-window-as-part-of-your-product-strategy/comment-page-1/#comment-23123</link>
		<dc:creator>Consider your market window as part of your product strategy &#171; It&#8217;s the software, stupid!</dc:creator>
		<pubDate>Wed, 01 Apr 2009 05:31:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.goodproductmanager.com/?p=213#comment-23123</guid>
		<description>[...] Read on&#8230; [...]</description>
		<content:encoded><![CDATA[<p>[...] Read on&#8230; [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
