<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Perspectives on Sales &#38; Operations Planning &#187; top down forecasting</title>
	<atom:link href="http://www.steelwedge.com/blog/tag/top-down-forecasting/feed" rel="self" type="application/rss+xml" />
	<link>http://www.steelwedge.com/blog</link>
	<description>Best Practices in Sales and Operations Planning (S&#38;OP)</description>
	<lastBuildDate>Tue, 10 Jan 2012 01:55:00 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.1</generator>
		<item>
		<title>Top 10 Mutant S&amp;OP Terms</title>
		<link>http://www.steelwedge.com/blog/top-10-mutant-sop-terms.html</link>
		<comments>http://www.steelwedge.com/blog/top-10-mutant-sop-terms.html#comments</comments>
		<pubDate>Tue, 21 Dec 2010 22:55:40 +0000</pubDate>
		<dc:creator>Rick Blair</dc:creator>
				<category><![CDATA[Sales & Operations Planning]]></category>
		<category><![CDATA[collaborative S&OP]]></category>
		<category><![CDATA[executive S&OP]]></category>
		<category><![CDATA[Performance Management]]></category>
		<category><![CDATA[S&OP]]></category>
		<category><![CDATA[s&op best practices]]></category>
		<category><![CDATA[S&OP terms]]></category>
		<category><![CDATA[steelwedge]]></category>
		<category><![CDATA[top down forecasting]]></category>

		<guid isPermaLink="false">http://www.steelwedge.com/blog/?p=1053</guid>
		<description><![CDATA[<p>Looking back over the year that was 2010, I jotted down several terms which struck me as interesting twists on some familiar terms.  Some of these twists were intentional mutations while others were totally unintentional.  My favorites tend to be of the unintended variety.  Here’s my Top 10 S&#38;OP list of terms from 2010:</p>
<p>10.  <strong>Key Performance Medics</strong>:  Specially trained analysts who come to the rescue to turn around poor performance indicators</p>
<p>9.   <strong>Strategery</strong>:  a plan, approach, line of attack (very similar to strategy)</p>
<p>8.   <strong>Regression Forecasting</strong>:  Reverting to an earlier, more accurate forecast to give the impression of better forecasting</p>
<p>7.   <strong>Imperial Forecasting</strong>:  The ultimate Top Down forecast, dictated by the ruler of the kingdom</p>
<p>6.   <strong>Reactive demand shaping</strong>:  coming up with a marketing promotion during the month in which additional sales are needed rather than planning ahead as part of an overall strategy (or Strategery)</p>
<p>5.   <strong>Tough Luck Capacity Planning</strong>:  Similar to Rough Cut Capacity Planning; however, with Tough Luck, capacity is fixed so the supply plan drives the demand plan</p>
<p>4.   <strong>New Product Insanity</strong>:  The attempt to forecast new product launch dates</p>
<p>3.   <strong>Higher Keys</strong>:  Rooted in the data structure concept of hierarchies, this mutation is the idea that key groups are formed through aggregation</p>
<p>2.   <strong>Moving Adage Forecast</strong>:  A twist on moving average, continually changing forecast caused by management mood swings</p>
<p>And the number 1 term…</p>
<p>1.    <strong>Disaggravation</strong>:  The Steelwedge disaggregation functionality which enables users to enter forecasts at higher levels of aggregation, reducing the number entries and thus, reducing user aggravation.</p>
]]></description>
			<content:encoded><![CDATA[<p>Looking back over the year that was 2010, I jotted down several terms which struck me as interesting twists on some familiar terms.  Some of these twists were intentional mutations while others were totally unintentional.  My favorites tend to be of the unintended variety.  Here’s my Top 10 S&amp;OP list of terms from 2010:</p>
<p>10.  <strong>Key Performance Medics</strong>:  Specially trained analysts who come to the rescue to turn around poor performance indicators</p>
<p>9.   <strong>Strategery</strong>:  a plan, approach, line of attack (very similar to strategy)</p>
<p>8.   <strong>Regression Forecasting</strong>:  Reverting to an earlier, more accurate forecast to give the impression of better forecasting</p>
<p>7.   <strong>Imperial Forecasting</strong>:  The ultimate Top Down forecast, dictated by the ruler of the kingdom</p>
<p>6.   <strong>Reactive demand shaping</strong>:  coming up with a marketing promotion during the month in which additional sales are needed rather than planning ahead as part of an overall strategy (or Strategery)</p>
<p>5.   <strong>Tough Luck Capacity Planning</strong>:  Similar to Rough Cut Capacity Planning; however, with Tough Luck, capacity is fixed so the supply plan drives the demand plan</p>
<p>4.   <strong>New Product Insanity</strong>:  The attempt to forecast new product launch dates</p>
<p>3.   <strong>Higher Keys</strong>:  Rooted in the data structure concept of hierarchies, this mutation is the idea that key groups are formed through aggregation</p>
<p>2.   <strong>Moving Adage Forecast</strong>:  A twist on moving average, continually changing forecast caused by management mood swings</p>
<p>And the number 1 term…</p>
<p>1.    <strong>Disaggravation</strong>:  The Steelwedge disaggregation functionality which enables users to enter forecasts at higher levels of aggregation, reducing the number entries and thus, reducing user aggravation.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.steelwedge.com/blog/top-10-mutant-sop-terms.html/feed</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Boost S&amp;OP with Top-Down and Bottom-Up Strategy</title>
		<link>http://www.steelwedge.com/blog/boost-sop-with-top-down-and-bottom-up-strategy.html</link>
		<comments>http://www.steelwedge.com/blog/boost-sop-with-top-down-and-bottom-up-strategy.html#comments</comments>
		<pubDate>Tue, 02 Nov 2010 19:03:45 +0000</pubDate>
		<dc:creator>Rick Blair</dc:creator>
				<category><![CDATA[Sales & Operations Planning]]></category>
		<category><![CDATA[Sales Forecasting]]></category>
		<category><![CDATA[bottom up forecasting]]></category>
		<category><![CDATA[Collaborative Planning]]></category>
		<category><![CDATA[collaborative S&OP]]></category>
		<category><![CDATA[Demand Forecasting]]></category>
		<category><![CDATA[executive S&OP]]></category>
		<category><![CDATA[S&OP]]></category>
		<category><![CDATA[s&op best practices]]></category>
		<category><![CDATA[S&OP software]]></category>
		<category><![CDATA[s&op solutions]]></category>
		<category><![CDATA[top down forecasting]]></category>

		<guid isPermaLink="false">http://www.steelwedge.com/blog/?p=942</guid>
		<description><![CDATA[<p><a href="http://www.steelwedge.com/blog/media/uploads/2010/11/rescue1.jpg"></a><em>Have you lost faith in Sales forecasts?<br />
Does Sales consistently over or under estimate future sales activity?<br />
</em></p>
<p>A multi-billion dollar global manufacturer is struggling. Two divisions of the company are at odds on how best to achieve world class forecast accuracy. Regional sales account representatives provide forecasts well above historical sales levels. Why? Because inventories made available to each country are insufficient to meet market demand. The result: predict more sales to try to influence supply decisions and receive a greater portion of supply for your region. One division has decided that a centralized approach is best and is no longer considering regional sales input. The other division is moving to a collaborative S&#38;OP approach where regional input is requested, evaluated and incorporated in the overall plan.<br />
<em></em></p>
<p><em>Which method do you think will produce a better plan?<br />
Which method will distribute limited resources better?<br />
Which method will yield higher profitability?<br />
</em></p>
<p>Time will tell for this organization. Yet, we can make a prediction today. Experience would suggest that a well-designed, collaborative S&#38;OP process will produce better results. Here’s how we look at how Top-Down and Bottom-Up S&#38;OP drives better results.<br />
<strong>1. Bottom-Up Inputs:</strong> Bottom-up forecasts are accumulated from many contributors. A distributed sales force may have hundreds or thousands of contributors. Each contributor has a specific area of expertise such as a specific customer, product or geographic area. The contributor enters her forecasts for her specific area of responsibility. Forecasts from all contributors are summed to capture an overall bottom-up forecast.<br />
<strong>2. Top-Down Inputs:</strong> Top-down projections apply a more centralized view. A small number of forecasters will look at various inputs and generate forecasts. Influencing factors may include market data, economic indicators, and general product and customer trends.<br />
<strong>3.</strong>&#8230;</p>]]></description>
			<content:encoded><![CDATA[<p><a href="http://www.steelwedge.com/blog/media/uploads/2010/11/rescue1.jpg"><img class="size-full wp-image-947 alignleft" style="margin: 5px;" src="http://www.steelwedge.com/blog/media/uploads/2010/11/rescue1.jpg" alt="" width="154" height="185" /></a><em>Have you lost faith in Sales forecasts?<br />
Does Sales consistently over or under estimate future sales activity?<br />
</em></p>
<p>A multi-billion dollar global manufacturer is struggling. Two divisions of the company are at odds on how best to achieve world class forecast accuracy. Regional sales account representatives provide forecasts well above historical sales levels. Why? Because inventories made available to each country are insufficient to meet market demand. The result: predict more sales to try to influence supply decisions and receive a greater portion of supply for your region. One division has decided that a centralized approach is best and is no longer considering regional sales input. The other division is moving to a collaborative S&amp;OP approach where regional input is requested, evaluated and incorporated in the overall plan.<br />
<em></em></p>
<p><em>Which method do you think will produce a better plan?<br />
Which method will distribute limited resources better?<br />
Which method will yield higher profitability?<br />
</em></p>
<p>Time will tell for this organization. Yet, we can make a prediction today. Experience would suggest that a well-designed, collaborative S&amp;OP process will produce better results. Here’s how we look at how Top-Down and Bottom-Up S&amp;OP drives better results.<br />
<strong>1. Bottom-Up Inputs:</strong> Bottom-up forecasts are accumulated from many contributors. A distributed sales force may have hundreds or thousands of contributors. Each contributor has a specific area of expertise such as a specific customer, product or geographic area. The contributor enters her forecasts for her specific area of responsibility. Forecasts from all contributors are summed to capture an overall bottom-up forecast.<br />
<strong>2. Top-Down Inputs:</strong> Top-down projections apply a more centralized view. A small number of forecasters will look at various inputs and generate forecasts. Influencing factors may include market data, economic indicators, and general product and customer trends.<br />
<strong>3. Balancing Top-Down and Bottom-Up Forecasts:</strong> The beauty of top-down and bottom-up planning is their ability to look at the world from differing vantage points. The folks in the “ivory tower” know important information, but they don’t know everything. The folks in the field have keen insights into their unique areas, but they only see their small piece.</p>
<p>Recommendations:<br />
<strong>1. Gather Objective Inputs:</strong> The collaboration challenge is to capture the small pieces without tainting the field forecaster’s view. In other words, don’t tell the field forecasters the top-down targets. When field forecasters are told what their forecasts are expected to be, they tend to send back values right in line with the top-down values. Such tainted bottom-up forecasts miss the point of gathering field intelligence.<br />
<strong>2. Balance Inputs:</strong> An effective marriage will capture top-down and bottom-up forecasts separately.<br />
<strong>3. Manage by Exception:</strong> Look for forecasts with the most significant (unit and/or revenue focused) difference between top-down and bottom-up forecasts. Is there an opportunity the field sees that the top-down approach did not capture? A management by exception S&amp;OP tool will make comparisons quickly to enable users to analyze critical differences and refine the ultimate consensus driven forecast.<br />
<strong>4. Provide Feedback:</strong> Tell forecasters how they’re doing. Measure forecast accuracy and bias. Track performance at various levels, including individuals. Forecasters who consistently over or under forecast (bias) should know that the organization knows. Such bias may be intentional or unintentional. Either way, behavior needs to change to produce reliable projections to which the organization can deliver.<br />
S&amp;OP really does lead to improved bottom-line results. Break down the walls of distrust and embrace collaboration.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.steelwedge.com/blog/boost-sop-with-top-down-and-bottom-up-strategy.html/feed</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Sales and Operations Planning: Are Executives Killing Collaboration?</title>
		<link>http://www.steelwedge.com/blog/sop-are-executives-killing-collaboration.html</link>
		<comments>http://www.steelwedge.com/blog/sop-are-executives-killing-collaboration.html#comments</comments>
		<pubDate>Thu, 24 Dec 2009 05:58:47 +0000</pubDate>
		<dc:creator>Rick Blair</dc:creator>
				<category><![CDATA[Sales & Operations Planning]]></category>
		<category><![CDATA[executive S&OP]]></category>
		<category><![CDATA[S&OP]]></category>
		<category><![CDATA[s&op best practices]]></category>
		<category><![CDATA[s&op planning]]></category>
		<category><![CDATA[S&OP process]]></category>
		<category><![CDATA[S&OP Sales]]></category>
		<category><![CDATA[s&op solutions]]></category>
		<category><![CDATA[sales & operations planning process]]></category>
		<category><![CDATA[sales and operations planning]]></category>
		<category><![CDATA[Sales Forecasting and Planning]]></category>
		<category><![CDATA[top down forecasting]]></category>

		<guid isPermaLink="false">http://www.steelwedge.com/blog/sop-are-executives-killing-collaboration.html</guid>
		<description><![CDATA[<p>Why do some executives feel inclined to make substantial forecast changes based solely on their own judgment? There’s no doubt the typical executive has keen insights into the business she directs. Yet, when that executive chooses to override other inputs, she undermines the integrity of the collaborative process.</p>
<p>“Why should I put any effort into creating a forecast when I know he will change it anyway?” This quote came from a client with whom I worked. The clear message was that their company’s collaborative forecasting process was not supported by the senior executive who had the final say in what the “consensus” plan would be. His actions unintentionally conveyed a message that the Sales and Operations Planning process which led to his desk had little merit in his eyes. The prevailing sentiment shared by S&#38;OP participants was that their work was unimportant.</p>
<p>Opportunity lost! Executives must understand that S&#38;OP can be successful only when they are engaged and supportive. Trumping the collaborative output sends a demoralizing signal. Empowered participants deliver superior results.</p>
<p>An effective S&#38;OP process leverages inputs from across functional disciplines and at various levels of responsibility. Most decisions should be made prior to the Executive S&#38;OP meeting. Executives should focus on setting policy, reviewing lower level decisions, breaking ties and making critical, strategic decisions.</p>
<p>Don’t kill collaboration. Empower participants and achieve better results.</p>
<p>By the way…the executive who applied his own final forecast values achieved forecast accuracy levels worse than if they had used the statistical forecast alone. Lots of analysis and meetings with nothing to show for it!</p>
]]></description>
			<content:encoded><![CDATA[<p><img class="alignleft size-full wp-image-443" src="http://www.steelwedge.com/blog/media/uploads/2009/12/killing.jpg" alt="" width="300" height="314" />Why do some executives feel inclined to make substantial forecast changes based solely on their own judgment? There’s no doubt the typical executive has keen insights into the business she directs. Yet, when that executive chooses to override other inputs, she undermines the integrity of the collaborative process.</p>
<p>“Why should I put any effort into creating a forecast when I know he will change it anyway?” This quote came from a client with whom I worked. The clear message was that their company’s collaborative forecasting process was not supported by the senior executive who had the final say in what the “consensus” plan would be. His actions unintentionally conveyed a message that the Sales and Operations Planning process which led to his desk had little merit in his eyes. The prevailing sentiment shared by S&amp;OP participants was that their work was unimportant.</p>
<p>Opportunity lost! Executives must understand that S&amp;OP can be successful only when they are engaged and supportive. Trumping the collaborative output sends a demoralizing signal. Empowered participants deliver superior results.</p>
<p>An effective S&amp;OP process leverages inputs from across functional disciplines and at various levels of responsibility. Most decisions should be made prior to the Executive S&amp;OP meeting. Executives should focus on setting policy, reviewing lower level decisions, breaking ties and making critical, strategic decisions.</p>
<p>Don’t kill collaboration. Empower participants and achieve better results.</p>
<p>By the way…the executive who applied his own final forecast values achieved forecast accuracy levels worse than if they had used the statistical forecast alone. Lots of analysis and meetings with nothing to show for it!</p>
]]></content:encoded>
			<wfw:commentRss>http://www.steelwedge.com/blog/sop-are-executives-killing-collaboration.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Sales and Operations Planning, Collaborative Demand Planning Depends on Bottom-up, Top-down and Statistical Forecasting</title>
		<link>http://www.steelwedge.com/blog/sop-collaborative-demand-planning-depends-bottomup-topdown-statistical-forecasting.html</link>
		<comments>http://www.steelwedge.com/blog/sop-collaborative-demand-planning-depends-bottomup-topdown-statistical-forecasting.html#comments</comments>
		<pubDate>Tue, 08 Dec 2009 02:50:10 +0000</pubDate>
		<dc:creator>Rick Blair</dc:creator>
				<category><![CDATA[Demand Forecasting]]></category>
		<category><![CDATA[Sales & Operations Planning]]></category>
		<category><![CDATA[Sales Forecasting]]></category>
		<category><![CDATA[collaborative planning and forecasting]]></category>
		<category><![CDATA[executive S&OP]]></category>
		<category><![CDATA[S&OP]]></category>
		<category><![CDATA[s&op best practices]]></category>
		<category><![CDATA[s&op planning]]></category>
		<category><![CDATA[S&OP process]]></category>
		<category><![CDATA[S&OP Sales]]></category>
		<category><![CDATA[s&op solutions]]></category>
		<category><![CDATA[sales & operations planning process]]></category>
		<category><![CDATA[sales and operations planning]]></category>
		<category><![CDATA[Sales Forecasting and Planning]]></category>
		<category><![CDATA[top down forecasting]]></category>

		<guid isPermaLink="false">http://www.steelwedge.com/blog/?p=429</guid>
		<description><![CDATA[<p></p>
<p style="text-align: left;">An effective S&#38;OP program depends on solid, accurate demand forecasts. Best practice companies do three things well: statistical, top-down and bottom-up forecasting. Many companies are doing one or two of these, but few are doing all three well. Of course, some companies do none. Let’s just say these companies have a huge upside improvement potential.</p>
<p>A statistically generated forecast should use a “best fit” approach to select the mathematical algorithm that minimizes error (such as mean absolute percentage error (MAPE)). The statistical engine should select the best algorithm for each time-phased data series or set of regression data. The resulting forecast should serve as a starting point for bottom-up and top-down forecasts.</p>
<p>Bottom-up forecasts are accumulated from many contributors. A distributed sales force may have hundreds or thousands of contributors. Each contributor has a specific area of expertise such as a specific customer, product or geographic area. The contributor enters her forecasts for her specific area of responsibility. Forecasts from all contributors are summed to capture an overall bottom-up forecast.</p>
<p>Conversely, a top-down approach applies a more centralized view. A small number of forecasters will look at various inputs and generate forecasts. Influencing factors may include market data, economic indicators, and general product and customer trends. Here, too, the statistically generated forecast is a good number from which to start.</p>
<p>The beauty of top-down and bottom-up forecasts is their ability to look at the world from differing vantage points. The folks in the “ivory tower” know important information, but they don’t know everything. The folks in the field have keen insights into their unique areas, but they only see their small piece. The challenge is to capture the small pieces without tainting the field forecaster’s view. In other words, don’t tell the field forecasters the top-down targets. When field forecasters&#8230;</p>]]></description>
			<content:encoded><![CDATA[<p><img class="size-full wp-image-430 alignleft" src="http://www.steelwedge.com/blog/media/uploads/2009/12/Helping-hands.bmp" alt="Helping hands" width="133" height="180" /></p>
<p style="text-align: left;">An effective S&amp;OP program depends on solid, accurate demand forecasts. Best practice companies do three things well: statistical, top-down and bottom-up forecasting. Many companies are doing one or two of these, but few are doing all three well. Of course, some companies do none. Let’s just say these companies have a huge upside improvement potential.</p>
<p>A statistically generated forecast should use a “best fit” approach to select the mathematical algorithm that minimizes error (such as mean absolute percentage error (MAPE)). The statistical engine should select the best algorithm for each time-phased data series or set of regression data. The resulting forecast should serve as a starting point for bottom-up and top-down forecasts.</p>
<p>Bottom-up forecasts are accumulated from many contributors. A distributed sales force may have hundreds or thousands of contributors. Each contributor has a specific area of expertise such as a specific customer, product or geographic area. The contributor enters her forecasts for her specific area of responsibility. Forecasts from all contributors are summed to capture an overall bottom-up forecast.</p>
<p>Conversely, a top-down approach applies a more centralized view. A small number of forecasters will look at various inputs and generate forecasts. Influencing factors may include market data, economic indicators, and general product and customer trends. Here, too, the statistically generated forecast is a good number from which to start.</p>
<p>The beauty of top-down and bottom-up forecasts is their ability to look at the world from differing vantage points. The folks in the “ivory tower” know important information, but they don’t know everything. The folks in the field have keen insights into their unique areas, but they only see their small piece. The challenge is to capture the small pieces without tainting the field forecaster’s view. In other words, don’t tell the field forecasters the top-down targets. When field forecasters are told what their forecasts are expected to be, they tend to send back values right in line with the top-down values. Such tainted bottom-up forecasts miss the point of gathering field intelligence.</p>
<p>An effective marriage will capture top-down and bottom-up forecasts separately. A management by exception S&amp;OP tool will make comparisons quickly to enable users to analyze critical differences and refine the ultimate consensus driven forecast.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.steelwedge.com/blog/sop-collaborative-demand-planning-depends-bottomup-topdown-statistical-forecasting.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Working Together:  Bottom Up and Top Down Forecasting</title>
		<link>http://www.steelwedge.com/blog/working-together-bottom-up-and-top-down-forecasting.html</link>
		<comments>http://www.steelwedge.com/blog/working-together-bottom-up-and-top-down-forecasting.html#comments</comments>
		<pubDate>Tue, 29 Jul 2008 22:59:22 +0000</pubDate>
		<dc:creator>Rick Blair</dc:creator>
				<category><![CDATA[Sales Forecasting]]></category>
		<category><![CDATA[Collaboration]]></category>
		<category><![CDATA[S&OP]]></category>
		<category><![CDATA[sales and operations planning]]></category>
		<category><![CDATA[top down forecasting]]></category>

		<guid isPermaLink="false">http://www.steelwedge.com/blog/?p=49</guid>
		<description><![CDATA[<p class="MsoNormal"><span>An effective S&#38;OP program depends on solid, accurate demand forecasts.<span> </span>Best practice companies do three things well:<span> </span>statistical, top-down and bottom-up forecasting.<span> </span>Many companies are doing one or two of these, but few are doing all three well.<span> </span>Of course, some companies do none.<span> </span>Let’s just say these companies have a huge upside improvement potential.</span></p>
<p class="MsoNormal"><span>A statistically generated forecast should use a “best fit” approach to select the mathematical algorithm that minimizes error (using mean absolute percentage error (MAPE)).<span> </span>The statistical engine should select the best algorithm for each time-phased data series or set of regression data.<span> </span>The resulting forecast should serve as a starting point for bottom-up and top-down forecasts. </span></p>
<p class="MsoNormal"><span>Bottom-up forecasts are accumulated from many contributors.<span> </span>A distributed sales force may have hundreds or thousands of contributors.<span> </span>Each contributor has a specific area of expertise such as a specific customer, product or geographic area.<span> </span>The contributor enters her forecasts for her specific area of responsibility.<span> </span>Forecasts from all contributors are summed to capture an overall bottom-up forecast.</span></p>
<p class="MsoNormal"><span>Conversely, a top-down approach applies a more centralized view.<span> </span>A small number of forecasters will look at various inputs and generate forecasts.<span> </span>Influencing factors may include market data, economic indicators, and general product and customer trends.<span> </span>Here, too, the statistically generated forecast is a good number from which to start. </span></p>
<p class="MsoNormal"><span>The beauty of top-down and bottom-up forecasts is their ability to look at the world from differing vantage points.<span> </span>The folks in the “ivory tower” know important information, but they don’t know everything.<span> </span>The folks in the field have keen insights into their unique areas, but they only see their small piece.<span> </span>The challenge is to capture the small pieces without tainting the field forecaster’s view.<span> </span>In other words, don’t tell the field forecasters</span>&#8230;</p>]]></description>
			<content:encoded><![CDATA[<p class="MsoNormal"><span>An effective S&amp;OP program depends on solid, accurate demand forecasts.<span> </span>Best practice companies do three things well:<span> </span>statistical, top-down and bottom-up forecasting.<span> </span>Many companies are doing one or two of these, but few are doing all three well.<span> </span>Of course, some companies do none.<span> </span>Let’s just say these companies have a huge upside improvement potential.</span></p>
<p class="MsoNormal"><span>A statistically generated forecast should use a “best fit” approach to select the mathematical algorithm that minimizes error (using mean absolute percentage error (MAPE)).<span> </span>The statistical engine should select the best algorithm for each time-phased data series or set of regression data.<span> </span>The resulting forecast should serve as a starting point for bottom-up and top-down forecasts. </span></p>
<p class="MsoNormal"><span>Bottom-up forecasts are accumulated from many contributors.<span> </span>A distributed sales force may have hundreds or thousands of contributors.<span> </span>Each contributor has a specific area of expertise such as a specific customer, product or geographic area.<span> </span>The contributor enters her forecasts for her specific area of responsibility.<span> </span>Forecasts from all contributors are summed to capture an overall bottom-up forecast.</span></p>
<p class="MsoNormal"><span>Conversely, a top-down approach applies a more centralized view.<span> </span>A small number of forecasters will look at various inputs and generate forecasts.<span> </span>Influencing factors may include market data, economic indicators, and general product and customer trends.<span> </span>Here, too, the statistically generated forecast is a good number from which to start. </span></p>
<p class="MsoNormal"><span>The beauty of top-down and bottom-up forecasts is their ability to look at the world from differing vantage points.<span> </span>The folks in the “ivory tower” know important information, but they don’t know everything.<span> </span>The folks in the field have keen insights into their unique areas, but they only see their small piece.<span> </span>The challenge is to capture the small pieces without tainting the field forecaster’s view.<span> </span>In other words, don’t tell the field forecasters the top-down targets.<span> </span>When field forecasters are told what their forecasts are expected to be, they tend to send back values right in line with the top-down values.<span> </span>Such tainted bottom-up forecasts miss the point of gathering field intelligence.</span></p>
<p class="MsoNormal"><span><span>An effective marriage will capture top-down and bottom-up forecasts separately.<span> </span>A management by exception S&amp;OP tool will make comparisons quickly to enable users to analyze critical differences and refine the ultimate consensus driven forecast.<span> </span></span></span></p>
]]></content:encoded>
			<wfw:commentRss>http://www.steelwedge.com/blog/working-together-bottom-up-and-top-down-forecasting.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

