<?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: Improved Prioritization And Market Segmentation</title>
	<atom:link href="http://tynerblain.com/blog/2008/04/09/improved-prioritization/feed/" rel="self" type="application/rss+xml" />
	<link>http://tynerblain.com/blog/2008/04/09/improved-prioritization/</link>
	<description>Software product success.</description>
	<lastBuildDate>Thu, 18 Mar 2010 20:39:50 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Planet Project: 10 Rules for Prioritizing Features in a Customer-Oriented Or</title>
		<link>http://tynerblain.com/blog/2008/04/09/improved-prioritization/comment-page-1/#comment-453149</link>
		<dc:creator>Planet Project: 10 Rules for Prioritizing Features in a Customer-Oriented Or</dc:creator>
		<pubDate>Thu, 23 Oct 2008 12:22:09 +0000</pubDate>
		<guid isPermaLink="false">http://tynerblain.com/blog/?p=663#comment-453149</guid>
		<description>[...] http://tynerblain.com/blog/2008/04/09/improved-prioritization, thanks to Scott Selhorst for yet another great idea. Go there if you need a more visual [...]</description>
		<content:encoded><![CDATA[<p>[...] <a href="http://tynerblain.com/blog/2008/04/09/improved-prioritization" rel="nofollow">http://tynerblain.com/blog/2008/04/09/improved-prioritization</a>, thanks to Scott Selhorst for yet another great idea. Go there if you need a more visual [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scott Sehlhorst</title>
		<link>http://tynerblain.com/blog/2008/04/09/improved-prioritization/comment-page-1/#comment-351502</link>
		<dc:creator>Scott Sehlhorst</dc:creator>
		<pubDate>Mon, 21 Apr 2008 00:14:50 +0000</pubDate>
		<guid isPermaLink="false">http://tynerblain.com/blog/?p=663#comment-351502</guid>
		<description>Hey Alan,  thanks for continuing the discussion!

In terms of your example, I think it comes down to one of those &quot;it depends&quot; questions.

Will feature A, delivered to these other segments be enough, by itself, to get people to purchase in those segments (and delight them, in your example)?  If so, then yes - feature A makes much more sense - you get immediate payback.  If feature A is only one of 3 features that each segment must have to really be delighted (and drive exponential / word-of-mouth marketing style growth in those segments), then I am inclined to focus my efforts on a single segment first.

Ultimately it all comes down to the math, right?  I guess what I&#039;m trying to highlight is that there is a better-than-linear growth opportunity in each segment, but to achieve it, you have to address all of a particular segment&#039;s &quot;delight&quot; requirements before you can achieve it.

And I guess I&#039;m making the assumption that geometric growth in one segment exceeds a slower, incremental growth across multiple segments.

Ultimately, you should compare the results of the &quot;be some things to all people, and we will slowly grow in all markets&quot; approach with the &quot;be all things to some people, and we will rapidly grow in one segment (at a time)&quot; approach.  In any given circumstance, it is possible that one approach is a clear winner where the other is not.</description>
		<content:encoded><![CDATA[<p>Hey Alan,  thanks for continuing the discussion!</p>
<p>In terms of your example, I think it comes down to one of those &#8220;it depends&#8221; questions.</p>
<p>Will feature A, delivered to these other segments be enough, by itself, to get people to purchase in those segments (and delight them, in your example)?  If so, then yes &#8211; feature A makes much more sense &#8211; you get immediate payback.  If feature A is only one of 3 features that each segment must have to really be delighted (and drive exponential / word-of-mouth marketing style growth in those segments), then I am inclined to focus my efforts on a single segment first.</p>
<p>Ultimately it all comes down to the math, right?  I guess what I&#8217;m trying to highlight is that there is a better-than-linear growth opportunity in each segment, but to achieve it, you have to address all of a particular segment&#8217;s &#8220;delight&#8221; requirements before you can achieve it.</p>
<p>And I guess I&#8217;m making the assumption that geometric growth in one segment exceeds a slower, incremental growth across multiple segments.</p>
<p>Ultimately, you should compare the results of the &#8220;be some things to all people, and we will slowly grow in all markets&#8221; approach with the &#8220;be all things to some people, and we will rapidly grow in one segment (at a time)&#8221; approach.  In any given circumstance, it is possible that one approach is a clear winner where the other is not.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: AlanAJ01</title>
		<link>http://tynerblain.com/blog/2008/04/09/improved-prioritization/comment-page-1/#comment-346243</link>
		<dc:creator>AlanAJ01</dc:creator>
		<pubDate>Wed, 16 Apr 2008 12:54:42 +0000</pubDate>
		<guid isPermaLink="false">http://tynerblain.com/blog/?p=663#comment-346243</guid>
		<description>Thanks for responding, Scott. 

It seems obvious to me that there will be times when the best thing to do will not be the most important segment&#039;s highest priority. Let&#039;s say Feature A is Segment 1&#039;s second priority (perhaps a close second) and everyone else&#039;s first priority... I think I should delight the vast majority and please the minority, rather than delight the minority and ignore the vast majority. 

I agree that a value-driven approach may lead to mediocrity, but this is far from inevitable. We need to understand how to mix satisfaction and delight to deliver optimal outcomes.</description>
		<content:encoded><![CDATA[<p>Thanks for responding, Scott. </p>
<p>It seems obvious to me that there will be times when the best thing to do will not be the most important segment&#8217;s highest priority. Let&#8217;s say Feature A is Segment 1&#8217;s second priority (perhaps a close second) and everyone else&#8217;s first priority&#8230; I think I should delight the vast majority and please the minority, rather than delight the minority and ignore the vast majority. </p>
<p>I agree that a value-driven approach may lead to mediocrity, but this is far from inevitable. We need to understand how to mix satisfaction and delight to deliver optimal outcomes.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scott Sehlhorst</title>
		<link>http://tynerblain.com/blog/2008/04/09/improved-prioritization/comment-page-1/#comment-346146</link>
		<dc:creator>Scott Sehlhorst</dc:creator>
		<pubDate>Wed, 16 Apr 2008 02:39:05 +0000</pubDate>
		<guid isPermaLink="false">http://tynerblain.com/blog/?p=663#comment-346146</guid>
		<description>Hey Carl,

Great question / interesting twist!

I don&#039;t believe this approach works at all for prioritizing stakeholders, at least in the ways that you&#039;ve defined stakeholders in &lt;a href=&quot;http://tynerblain.com/blog/2007/09/27/outside-in/&quot; rel=&quot;nofollow&quot;&gt;Outside In Development&lt;/a&gt;.  In that case, you have insiders, principals, partners, and end-user stakeholders.  The insiders, partners, and principals (sponsors) all collaborate to achieve something that is a success with end-users.

And in that case, you are, in my opinion, collaborating as a team to deliver success.  You can&#039;t optimize (at least generally speaking) by satisfying all of the most important needs of one stakeholder group in advance of others.  I think this only applies when looking at segmentation of the market into mutually exclusive groups.  Perhaps, within a body - say partners - you might choose to prioritize one subset of the partners stakeholders in advance of another.

The benefit of attacking markets this way is that you get greater penetration of the market segment by making the customers &lt;i&gt;love&lt;/i&gt; your product.  I don&#039;t think you get an benefits from having a subset of your principals &lt;i&gt;love&lt;/i&gt; your product at the expense of another group.  In this case, I think the &quot;numerical best&quot; approach - what I label as least common denominator - would work better.

I&#039;d go on to say, in my experience, that politics within organizations would completely trump any mathematical prioritization for internal stakeholders.  So I would only take this semi-quantitative approach when segmenting end users.

You have a lot more experience in dealing with stakeholders and their priorities - what would you expect to see?</description>
		<content:encoded><![CDATA[<p>Hey Carl,</p>
<p>Great question / interesting twist!</p>
<p>I don&#8217;t believe this approach works at all for prioritizing stakeholders, at least in the ways that you&#8217;ve defined stakeholders in <a href="http://tynerblain.com/blog/2007/09/27/outside-in/" rel="nofollow">Outside In Development</a>.  In that case, you have insiders, principals, partners, and end-user stakeholders.  The insiders, partners, and principals (sponsors) all collaborate to achieve something that is a success with end-users.</p>
<p>And in that case, you are, in my opinion, collaborating as a team to deliver success.  You can&#8217;t optimize (at least generally speaking) by satisfying all of the most important needs of one stakeholder group in advance of others.  I think this only applies when looking at segmentation of the market into mutually exclusive groups.  Perhaps, within a body &#8211; say partners &#8211; you might choose to prioritize one subset of the partners stakeholders in advance of another.</p>
<p>The benefit of attacking markets this way is that you get greater penetration of the market segment by making the customers <i>love</i> your product.  I don&#8217;t think you get an benefits from having a subset of your principals <i>love</i> your product at the expense of another group.  In this case, I think the &#8220;numerical best&#8221; approach &#8211; what I label as least common denominator &#8211; would work better.</p>
<p>I&#8217;d go on to say, in my experience, that politics within organizations would completely trump any mathematical prioritization for internal stakeholders.  So I would only take this semi-quantitative approach when segmenting end users.</p>
<p>You have a lot more experience in dealing with stakeholders and their priorities &#8211; what would you expect to see?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scott Sehlhorst</title>
		<link>http://tynerblain.com/blog/2008/04/09/improved-prioritization/comment-page-1/#comment-346142</link>
		<dc:creator>Scott Sehlhorst</dc:creator>
		<pubDate>Wed, 16 Apr 2008 02:30:11 +0000</pubDate>
		<guid isPermaLink="false">http://tynerblain.com/blog/?p=663#comment-346142</guid>
		<description>Linda,

Thanks very much for commenting and welcome to Tyner Blain!

You&#039;re right - I didn&#039;t talk at all about how or why you would prefer one segment relative to another - or prioritize one ahead of another.  I alluded to this in my previous comment.

I think you&#039;re right also that focusing on a particular market segment not only helps with feature-prioritization, but it also can provide clarity in marketing communications, promotions, branding, and other elements of strategically attacking a market.

You&#039;ve added to the conversation here too, and I appreciate it.</description>
		<content:encoded><![CDATA[<p>Linda,</p>
<p>Thanks very much for commenting and welcome to Tyner Blain!</p>
<p>You&#8217;re right &#8211; I didn&#8217;t talk at all about how or why you would prefer one segment relative to another &#8211; or prioritize one ahead of another.  I alluded to this in my previous comment.</p>
<p>I think you&#8217;re right also that focusing on a particular market segment not only helps with feature-prioritization, but it also can provide clarity in marketing communications, promotions, branding, and other elements of strategically attacking a market.</p>
<p>You&#8217;ve added to the conversation here too, and I appreciate it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scott Sehlhorst</title>
		<link>http://tynerblain.com/blog/2008/04/09/improved-prioritization/comment-page-1/#comment-346140</link>
		<dc:creator>Scott Sehlhorst</dc:creator>
		<pubDate>Wed, 16 Apr 2008 02:26:53 +0000</pubDate>
		<guid isPermaLink="false">http://tynerblain.com/blog/?p=663#comment-346140</guid>
		<description>Alan,

Thanks for commenting!

I think the right approach is to prioritize segments.  You can do that based upon a forecast profitability per segment, a strategic objective (say to serve an existing customer base with a new product first, then expand to other market segments), for competitive reasons (to undermine your competitor&#039;s cash cow, or to gain a foothold / economies of scale before attacking), or whatever reason.

The point being that it is far better to be excellent in one segment - even at the expense of other segments, than it is to be pretty good in multiple segments.  And by prioritizing the features that are most important to a single segment, you reach that point earliest.  I believe that you will have better market penetration in each segment this way, resulting in an improved rate of growth.  If you model your market penetration and don&#039;t see this, then it is moot - but I expect you will find this to be true.

As to the &quot;highly profitable, but otherwise mediocre feature&quot; example, I disagree.  Let me fall on my sword and say that I should have articulated that prioritization within a market segment would include whatever is important in that segment - if profitability is the driver, then that &quot;highly profitable&quot; feature would be highly prioritized.  Sorry for not making that explicitly clear.  Given that clarification, I don&#039;t think your example would exist - the highly profitable feature (when prioritizing by profitability, within a segment) would be highly prioritized for all segments where it is highly profitable.

Thanks again!</description>
		<content:encoded><![CDATA[<p>Alan,</p>
<p>Thanks for commenting!</p>
<p>I think the right approach is to prioritize segments.  You can do that based upon a forecast profitability per segment, a strategic objective (say to serve an existing customer base with a new product first, then expand to other market segments), for competitive reasons (to undermine your competitor&#8217;s cash cow, or to gain a foothold / economies of scale before attacking), or whatever reason.</p>
<p>The point being that it is far better to be excellent in one segment &#8211; even at the expense of other segments, than it is to be pretty good in multiple segments.  And by prioritizing the features that are most important to a single segment, you reach that point earliest.  I believe that you will have better market penetration in each segment this way, resulting in an improved rate of growth.  If you model your market penetration and don&#8217;t see this, then it is moot &#8211; but I expect you will find this to be true.</p>
<p>As to the &#8220;highly profitable, but otherwise mediocre feature&#8221; example, I disagree.  Let me fall on my sword and say that I should have articulated that prioritization within a market segment would include whatever is important in that segment &#8211; if profitability is the driver, then that &#8220;highly profitable&#8221; feature would be highly prioritized.  Sorry for not making that explicitly clear.  Given that clarification, I don&#8217;t think your example would exist &#8211; the highly profitable feature (when prioritizing by profitability, within a segment) would be highly prioritized for all segments where it is highly profitable.</p>
<p>Thanks again!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Carl Kessler</title>
		<link>http://tynerblain.com/blog/2008/04/09/improved-prioritization/comment-page-1/#comment-343722</link>
		<dc:creator>Carl Kessler</dc:creator>
		<pubDate>Thu, 10 Apr 2008 21:49:21 +0000</pubDate>
		<guid isPermaLink="false">http://tynerblain.com/blog/?p=663#comment-343722</guid>
		<description>Very useful ideas.  The twist I&#039;m wondering about is when your analysis isn&#039;t separated by market segment.  In that case, for example, the different groups might represent different types of stakeholders (ala outside-in development, these could be sponsors, partners, insiders, or end-users).

If I tried to use the approach you describe to handle the overlapping / conflicting needs of different stakeholder groups, what would I need to do differently?

In this case, Group 3 wouldn&#039;t represent the most important market segment, but might represent an important (but maybe not &quot;most&quot;) stakeholder group.</description>
		<content:encoded><![CDATA[<p>Very useful ideas.  The twist I&#8217;m wondering about is when your analysis isn&#8217;t separated by market segment.  In that case, for example, the different groups might represent different types of stakeholders (ala outside-in development, these could be sponsors, partners, insiders, or end-users).</p>
<p>If I tried to use the approach you describe to handle the overlapping / conflicting needs of different stakeholder groups, what would I need to do differently?</p>
<p>In this case, Group 3 wouldn&#8217;t represent the most important market segment, but might represent an important (but maybe not &#8220;most&#8221;) stakeholder group.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Linda  P. Morton</title>
		<link>http://tynerblain.com/blog/2008/04/09/improved-prioritization/comment-page-1/#comment-343613</link>
		<dc:creator>Linda  P. Morton</dc:creator>
		<pubDate>Thu, 10 Apr 2008 18:57:52 +0000</pubDate>
		<guid isPermaLink="false">http://tynerblain.com/blog/?p=663#comment-343613</guid>
		<description>I found this blog and Alan&#039;s comment informative.

What seems to be missing from this information is how market 
segmentation helps to determine the best target market for a product.

It often even enables development of products for specific target 
markets. This can bring better profits than developing a generic
product and then trying to find a market for it. Today, people want 
products developed specifically to meet their needs.

Market segmentation sometimes involves math, depending on the process 
used, but it provides much more than just what features to include in
a product. It also reveals the best appeals to use for a target market, their information needs, concerns, values, and the best media to reach them.</description>
		<content:encoded><![CDATA[<p>I found this blog and Alan&#8217;s comment informative.</p>
<p>What seems to be missing from this information is how market<br />
segmentation helps to determine the best target market for a product.</p>
<p>It often even enables development of products for specific target<br />
markets. This can bring better profits than developing a generic<br />
product and then trying to find a market for it. Today, people want<br />
products developed specifically to meet their needs.</p>
<p>Market segmentation sometimes involves math, depending on the process<br />
used, but it provides much more than just what features to include in<br />
a product. It also reveals the best appeals to use for a target market, their information needs, concerns, values, and the best media to reach them.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: AlanAJ01</title>
		<link>http://tynerblain.com/blog/2008/04/09/improved-prioritization/comment-page-1/#comment-343447</link>
		<dc:creator>AlanAJ01</dc:creator>
		<pubDate>Thu, 10 Apr 2008 12:48:39 +0000</pubDate>
		<guid isPermaLink="false">http://tynerblain.com/blog/?p=663#comment-343447</guid>
		<description>Interesting theory...

To some extent it seems to beg the question, though. How do you determine the relative importance of your market segments? Let&#039;s assume profit is a key factor. Is your strategy to sell a few high-margin &quot;sports cars&quot; or a lot of lower-margin &quot;eco-chariots&quot;? If the strategy is not a given (constraint) then you can prioritize on the basis of profitability...but how could you do that when profitability depends on the changes you have yet to prioritize?

What you need to do is consider the impact of your optional enhancements on your strategic objectives, in this case profit. You can then be agnostic about which segment you prefer. A feature that no segment ranks highly may well improve profitability across all segments more than any other feature. Why would prioritizing that feature lead to mediocrity? Even if it does, you just need to add a &quot;stunnedness&quot; metric into your strategic objectives...but if you do this, you will need to establish the relative importance of improved &quot;stunnedness&quot; and higher profits (to combine the scalar objectives into an objective function, in some fashion).</description>
		<content:encoded><![CDATA[<p>Interesting theory&#8230;</p>
<p>To some extent it seems to beg the question, though. How do you determine the relative importance of your market segments? Let&#8217;s assume profit is a key factor. Is your strategy to sell a few high-margin &#8220;sports cars&#8221; or a lot of lower-margin &#8220;eco-chariots&#8221;? If the strategy is not a given (constraint) then you can prioritize on the basis of profitability&#8230;but how could you do that when profitability depends on the changes you have yet to prioritize?</p>
<p>What you need to do is consider the impact of your optional enhancements on your strategic objectives, in this case profit. You can then be agnostic about which segment you prefer. A feature that no segment ranks highly may well improve profitability across all segments more than any other feature. Why would prioritizing that feature lead to mediocrity? Even if it does, you just need to add a &#8220;stunnedness&#8221; metric into your strategic objectives&#8230;but if you do this, you will need to establish the relative importance of improved &#8220;stunnedness&#8221; and higher profits (to combine the scalar objectives into an objective function, in some fashion).</p>
]]></content:encoded>
	</item>
</channel>
</rss>
