<?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: What goes in to a product strategy besides goals, objectives, and tactics?</title>
	<atom:link href="http://ask.goodproductmanager.com/2009/06/21/what-goes-in-to-a-product-strategy-besides-goals-objectives-and-tactics/feed/" rel="self" type="application/rss+xml" />
	<link>http://ask.goodproductmanager.com/2009/06/21/what-goes-in-to-a-product-strategy-besides-goals-objectives-and-tactics/</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: David Locke</title>
		<link>http://ask.goodproductmanager.com/2009/06/21/what-goes-in-to-a-product-strategy-besides-goals-objectives-and-tactics/comment-page-1/#comment-24498</link>
		<dc:creator>David Locke</dc:creator>
		<pubDate>Sun, 01 Nov 2009 06:18:10 +0000</pubDate>
		<guid isPermaLink="false">http://ask.goodproductmanager.com/?p=126#comment-24498</guid>
		<description>Goals and objectives cover just about all of it. The issue is what range of goals. I&#039;ve put channel development on the roadmap. I&#039;ve put ecologies on the roadmap like 3rd-party developers, modelers, and content developers. If organizational capabilities need to be there to sell product, then they need to be on the map. 

Market transitions from Moore&#039;s technology adoption lifecycle need to be scheduled as well, along with marketure, as in technical marketure supporting those transitions, personas need to be on there. 

If you are in late market, your late market strategy will involve the product, so that needs to be there. The same goes for recession response, technical commoditization manuevers, and price commoditizatin manuevers. 

If it is &quot;in offer,&quot; it should be on the map. That includes data center operational goals like ensuring capacity and 24/7/365 service, recovery, rollover, and geomirroring. If it matters put it on the roadmap. 

The roadmap should inform the PM as to the scope of the influence they will need by a certain date. But, certain dates are uncertain, so think of the roadmap as an asynchronous clock. This before that. Hey, I better take the CIO to lunch, I&#039;ll need something from him a year from now.</description>
		<content:encoded><![CDATA[<p>Goals and objectives cover just about all of it. The issue is what range of goals. I&#8217;ve put channel development on the roadmap. I&#8217;ve put ecologies on the roadmap like 3rd-party developers, modelers, and content developers. If organizational capabilities need to be there to sell product, then they need to be on the map. </p>
<p>Market transitions from Moore&#8217;s technology adoption lifecycle need to be scheduled as well, along with marketure, as in technical marketure supporting those transitions, personas need to be on there. </p>
<p>If you are in late market, your late market strategy will involve the product, so that needs to be there. The same goes for recession response, technical commoditization manuevers, and price commoditizatin manuevers. </p>
<p>If it is &#8220;in offer,&#8221; it should be on the map. That includes data center operational goals like ensuring capacity and 24/7/365 service, recovery, rollover, and geomirroring. If it matters put it on the roadmap. </p>
<p>The roadmap should inform the PM as to the scope of the influence they will need by a certain date. But, certain dates are uncertain, so think of the roadmap as an asynchronous clock. This before that. Hey, I better take the CIO to lunch, I&#8217;ll need something from him a year from now.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: uberVU - social comments</title>
		<link>http://ask.goodproductmanager.com/2009/06/21/what-goes-in-to-a-product-strategy-besides-goals-objectives-and-tactics/comment-page-1/#comment-24098</link>
		<dc:creator>uberVU - social comments</dc:creator>
		<pubDate>Fri, 30 Oct 2009 16:38:32 +0000</pubDate>
		<guid isPermaLink="false">http://ask.goodproductmanager.com/?p=126#comment-24098</guid>
		<description>&lt;strong&gt;Social comments and analytics for this post...&lt;/strong&gt;

This post was mentioned on Twitter by Jim_Holland: &quot;What goes into a product strategy beside goals-objectives and tactics?&quot; by @jefflash http://bit.ly/t75iH #prodmgmt #agile #scrum...</description>
		<content:encoded><![CDATA[<p><strong>Social comments and analytics for this post&#8230;</strong></p>
<p>This post was mentioned on Twitter by Jim_Holland: &#8220;What goes into a product strategy beside goals-objectives and tactics?&#8221; by @jefflash <a href="http://bit.ly/t75iH" rel="nofollow">http://bit.ly/t75iH</a> #prodmgmt #agile #scrum&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mara Krieps</title>
		<link>http://ask.goodproductmanager.com/2009/06/21/what-goes-in-to-a-product-strategy-besides-goals-objectives-and-tactics/comment-page-1/#comment-14882</link>
		<dc:creator>Mara Krieps</dc:creator>
		<pubDate>Tue, 25 Aug 2009 15:17:28 +0000</pubDate>
		<guid isPermaLink="false">http://ask.goodproductmanager.com/?p=126#comment-14882</guid>
		<description>Agree with most of the comments above.  

One key point to add:  Your strategy should enable you to say &quot;No&quot; with confidence, as in the inevitable situation when you&#039;re presented with a &quot;great&quot; opportunity that doesn&#039;t align with your strategy.  

A clearly articulated strategy will provide you with the means to say, &quot;No and here&#039;s why&quot;.  The benefit to you and the product: many cycles saved, and resources protected for the critical work that needs to be done.</description>
		<content:encoded><![CDATA[<p>Agree with most of the comments above.  </p>
<p>One key point to add:  Your strategy should enable you to say &#8220;No&#8221; with confidence, as in the inevitable situation when you&#8217;re presented with a &#8220;great&#8221; opportunity that doesn&#8217;t align with your strategy.  </p>
<p>A clearly articulated strategy will provide you with the means to say, &#8220;No and here&#8217;s why&#8221;.  The benefit to you and the product: many cycles saved, and resources protected for the critical work that needs to be done.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: What goes into a product strategy other than goals, objectives and tactics &#124; brainmates - product management people</title>
		<link>http://ask.goodproductmanager.com/2009/06/21/what-goes-in-to-a-product-strategy-besides-goals-objectives-and-tactics/comment-page-1/#comment-8897</link>
		<dc:creator>What goes into a product strategy other than goals, objectives and tactics &#124; brainmates - product management people</dc:creator>
		<pubDate>Wed, 24 Jun 2009 08:58:30 +0000</pubDate>
		<guid isPermaLink="false">http://ask.goodproductmanager.com/?p=126#comment-8897</guid>
		<description>[...] I recently wrote an answer to &#8220;How do product goals, objectives, and tactics relate to the product strategy?&#8221; for the excellent blog Ask A Good Product Manager. Here is a copy of my answer but to read what other Product Managers have to say, click here. [...]</description>
		<content:encoded><![CDATA[<p>[...] I recently wrote an answer to &#8220;How do product goals, objectives, and tactics relate to the product strategy?&#8221; for the excellent blog Ask A Good Product Manager. Here is a copy of my answer but to read what other Product Managers have to say, click here. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stewart Rogers</title>
		<link>http://ask.goodproductmanager.com/2009/06/21/what-goes-in-to-a-product-strategy-besides-goals-objectives-and-tactics/comment-page-1/#comment-8869</link>
		<dc:creator>Stewart Rogers</dc:creator>
		<pubDate>Tue, 23 Jun 2009 12:19:44 +0000</pubDate>
		<guid isPermaLink="false">http://ask.goodproductmanager.com/?p=126#comment-8869</guid>
		<description>I agree with Purist that defining the strategy is a collaborative effort (more for validation and alignment), however make no mistake that product management owns the strategy and therefore has final say. Assuming you have the facts to justify your say. :-)

And although I agree with what Janey says, this smells a little like competitive strategy. The competitive strategy is only one aspect of your product strategy and you have to be mindful of the red ocean.

The piece to remember, your strategy is the &quot;how&quot; of a complete story that also tells &quot;who&quot;, &quot;what&quot;, &quot;why&quot; and how it is aligned. 

It is hard work, will change weekly (maybe, but be aware it might be) and as product managers this is the majority of your job so apply the time necessary.

Stewart</description>
		<content:encoded><![CDATA[<p>I agree with Purist that defining the strategy is a collaborative effort (more for validation and alignment), however make no mistake that product management owns the strategy and therefore has final say. Assuming you have the facts to justify your say. <img src='http://ask.goodproductmanager.com/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
<p>And although I agree with what Janey says, this smells a little like competitive strategy. The competitive strategy is only one aspect of your product strategy and you have to be mindful of the red ocean.</p>
<p>The piece to remember, your strategy is the &#8220;how&#8221; of a complete story that also tells &#8220;who&#8221;, &#8220;what&#8221;, &#8220;why&#8221; and how it is aligned. </p>
<p>It is hard work, will change weekly (maybe, but be aware it might be) and as product managers this is the majority of your job so apply the time necessary.</p>
<p>Stewart</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Raj</title>
		<link>http://ask.goodproductmanager.com/2009/06/21/what-goes-in-to-a-product-strategy-besides-goals-objectives-and-tactics/comment-page-1/#comment-8861</link>
		<dc:creator>Raj</dc:creator>
		<pubDate>Tue, 23 Jun 2009 07:16:01 +0000</pubDate>
		<guid isPermaLink="false">http://ask.goodproductmanager.com/?p=126#comment-8861</guid>
		<description>Great points by both Janey and PuristPM.

Another angle I&#039;d like to add is this. Product goals, objectives and tactics should follow from product strategy.

In this sense, product strategy comes first. Then you derive goals, objectives and tactics. 

As Janey says product strategy should be in sync with and flow from corporate strategy.

Hope this makes sense and is helpful.

- Raj
&lt;a href=&quot;http://www.accompa.com&quot; rel=&quot;nofollow&quot;&gt;Accompa - Affordable Requirements Tool for Product Managers&lt;/a&gt;</description>
		<content:encoded><![CDATA[<p>Great points by both Janey and PuristPM.</p>
<p>Another angle I&#8217;d like to add is this. Product goals, objectives and tactics should follow from product strategy.</p>
<p>In this sense, product strategy comes first. Then you derive goals, objectives and tactics. </p>
<p>As Janey says product strategy should be in sync with and flow from corporate strategy.</p>
<p>Hope this makes sense and is helpful.</p>
<p>- Raj<br />
<a href="http://www.accompa.com" rel="nofollow">Accompa &#8211; Affordable Requirements Tool for Product Managers</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: PuristProductManagement</title>
		<link>http://ask.goodproductmanager.com/2009/06/21/what-goes-in-to-a-product-strategy-besides-goals-objectives-and-tactics/comment-page-1/#comment-8829</link>
		<dc:creator>PuristProductManagement</dc:creator>
		<pubDate>Mon, 22 Jun 2009 10:09:06 +0000</pubDate>
		<guid isPermaLink="false">http://ask.goodproductmanager.com/?p=126#comment-8829</guid>
		<description>Agree. I also think that the most important aspect of a product strategy is understanding how the product will be positioned within the market - i.e. a positioning document. For me, creating a product strategy is very much a collaborative process between; Sales, Marketing, business development and technology with product management pulling the strings. 
The reason for this is 2 fold: 
1 - to be able to get access to all the relevant information as required. 
2 - to be gain buy in to the strategy from all the key departments.</description>
		<content:encoded><![CDATA[<p>Agree. I also think that the most important aspect of a product strategy is understanding how the product will be positioned within the market &#8211; i.e. a positioning document. For me, creating a product strategy is very much a collaborative process between; Sales, Marketing, business development and technology with product management pulling the strings.<br />
The reason for this is 2 fold:<br />
1 &#8211; to be able to get access to all the relevant information as required.<br />
2 &#8211; to be gain buy in to the strategy from all the key departments.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
