<?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/"
	xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
xmlns:rawvoice="http://www.rawvoice.com/rawvoiceRssModule/"
	>
<channel>
	<title>Comments on: A Front-End Approach to SKU Rationalization</title>
	<atom:link href="http://logisticsviewpoints.com/2009/08/26/a-front-end-approach-to-sku-rationalization/feed/" rel="self" type="application/rss+xml" />
	<link>http://logisticsviewpoints.com/2009/08/26/a-front-end-approach-to-sku-rationalization/</link>
	<description>Providing logistics professionals with clear and concise analyses of Logistics Trends, Technologies, and Services</description>
	<lastBuildDate>Wed, 16 May 2012 10:07:14 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: burnseyjp</title>
		<link>http://logisticsviewpoints.com/2009/08/26/a-front-end-approach-to-sku-rationalization/comment-page-1/#comment-124</link>
		<dc:creator>burnseyjp</dc:creator>
		<pubDate>Fri, 20 Nov 2009 16:49:25 +0000</pubDate>
		<guid isPermaLink="false">http://logisticsviewpoints.com/?p=1625#comment-124</guid>
		<description>Do you have any resources that would cover replacing an existing product with a new product?  Specifically removing the existing from the market as the features on the new product are significantly better.  My concerns here are that by making both products available our team does not have the proper focus to make the new product a success.</description>
		<content:encoded><![CDATA[<p>Do you have any resources that would cover replacing an existing product with a new product?  Specifically removing the existing from the market as the features on the new product are significantly better.  My concerns here are that by making both products available our team does not have the proper focus to make the new product a success.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: shawndolley1</title>
		<link>http://logisticsviewpoints.com/2009/08/26/a-front-end-approach-to-sku-rationalization/comment-page-1/#comment-100</link>
		<dc:creator>shawndolley1</dc:creator>
		<pubDate>Sat, 10 Oct 2009 18:46:08 +0000</pubDate>
		<guid isPermaLink="false">http://logisticsviewpoints.com/?p=1625#comment-100</guid>
		<description>Couldn&#039;t a brand company review their successes in terms of the past product &#039;winners&#039; - those product scores at each stage?  If they find a pattern (such as their winners always do well in development testing), then they could raise the hurdle rates for future products?  If they designed a scoring pattern required across the stages that only the winners would have passed, then future products using those hurdles rates would be more aggressively weeded out.  This would reduce your Type I errors, false positives, and many of the products the company thinks are winners are rejected because they won&#039;t be winners.  Has anyone tried this?
From Shawn Dolley at http://previouslyimpossible.wordpress.com/</description>
		<content:encoded><![CDATA[<p>Couldn&#8217;t a brand company review their successes in terms of the past product &#8216;winners&#8217; &#8211; those product scores at each stage?  If they find a pattern (such as their winners always do well in development testing), then they could raise the hurdle rates for future products?  If they designed a scoring pattern required across the stages that only the winners would have passed, then future products using those hurdles rates would be more aggressively weeded out.  This would reduce your Type I errors, false positives, and many of the products the company thinks are winners are rejected because they won&#8217;t be winners.  Has anyone tried this?<br />
From Shawn Dolley at <a href="http://previouslyimpossible.wordpress.com/" rel="nofollow">http://previouslyimpossible.wordpress.com/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jfisher@emcien.com</title>
		<link>http://logisticsviewpoints.com/2009/08/26/a-front-end-approach-to-sku-rationalization/comment-page-1/#comment-87</link>
		<dc:creator>Jfisher@emcien.com</dc:creator>
		<pubDate>Thu, 27 Aug 2009 12:09:37 +0000</pubDate>
		<guid isPermaLink="false">http://logisticsviewpoints.com/?p=1625#comment-87</guid>
		<description>Very good article.  You are addressing SKU rationalization for NPI, or new products. However, 80% of revenue, the bread and butter is coming from existing products, and there is a lack of product management around them.  Companies launch into SKU rationalization projects, groaning - like my son does when he is pushed to clean his room.  Most of his stuff ends up under the bed. Similarly, most of the SKU rationalization projects do not produce sustainable results. 
SKU rationalization should not be viewed as a one-time exercise, as most companies do.  
It is appalling - but most companies do not have a product management process, which is an ongoing monitoring of SKU profitability, category management and metrics around SKU efficiency. 
Emcien offers a set of tools and process for sustainable SKU management and metrics around SKU efficiency.  The SKU efficiency measures how much distinct attribution the SKU has, and how much demand it captures.  
http://www.emcien.com/Emcienmix
An SKU that is created with just one attribute difference, to capture one more order is very expensive on the enterprise. 

Also - you can read about the analytics around demand sensing to manage SKUs at
http://blog.emcien.com</description>
		<content:encoded><![CDATA[<p>Very good article.  You are addressing SKU rationalization for NPI, or new products. However, 80% of revenue, the bread and butter is coming from existing products, and there is a lack of product management around them.  Companies launch into SKU rationalization projects, groaning &#8211; like my son does when he is pushed to clean his room.  Most of his stuff ends up under the bed. Similarly, most of the SKU rationalization projects do not produce sustainable results.<br />
SKU rationalization should not be viewed as a one-time exercise, as most companies do.<br />
It is appalling &#8211; but most companies do not have a product management process, which is an ongoing monitoring of SKU profitability, category management and metrics around SKU efficiency.<br />
Emcien offers a set of tools and process for sustainable SKU management and metrics around SKU efficiency.  The SKU efficiency measures how much distinct attribution the SKU has, and how much demand it captures.<br />
<a href="http://www.emcien.com/Emcienmix" rel="nofollow">http://www.emcien.com/Emcienmix</a><br />
An SKU that is created with just one attribute difference, to capture one more order is very expensive on the enterprise. </p>
<p>Also &#8211; you can read about the analytics around demand sensing to manage SKUs at<br />
<a href="http://blog.emcien.com" rel="nofollow">http://blog.emcien.com</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>

