<?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>Sales Process Engineering &#187; sales forecast</title>
	<atom:link href="http://www.salesprocessengineering.net/tag/sales-forecast/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.salesprocessengineering.net</link>
	<description>The application of process-engineering principles (particularly TOC) to the sales process</description>
	<lastBuildDate>Sat, 04 Feb 2012 04:49:49 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>An alternative to forecasting in major-account sales environments</title>
		<link>http://www.salesprocessengineering.net/2008/11/11/an-alternative-to-forecasting-in-major-account-sales-environments/</link>
		<comments>http://www.salesprocessengineering.net/2008/11/11/an-alternative-to-forecasting-in-major-account-sales-environments/#comments</comments>
		<pubDate>Tue, 11 Nov 2008 06:03:09 +0000</pubDate>
		<dc:creator>Justin Roff-Marsh</dc:creator>
				<category><![CDATA[Measures and General Management]]></category>
		<category><![CDATA[measurement]]></category>
		<category><![CDATA[sales forecast]]></category>

		<guid isPermaLink="false">http://www.salesprocessengineering.net/2008/11/11/an-alternative-to-forecasting-in-major-account-sales-environments/</guid>
		<description><![CDATA[In a previous post, I poked fun at the practice of sales forecasting in major-account sales environments &#8212; referring to it as hocus-pocus with a dollar sign. The essence of my argument was that, in environments where transactions are small in frequency, but large in magnitude ($&#8217;s), the traditional approach to forecasting destroys information &#8212; [...]]]></description>
			<content:encoded><![CDATA[<p>In a previous post, I poked fun at the practice of sales forecasting in major-account sales environments &mdash; referring to it as <a href="http://www.salesprocessengineering.net/2008/08/11/sales-forecasts-hocus-pocus-with-a-dollar-sign/"><i>hocus-pocus with a dollar sign</i></a>.</p>
<p>The essence of my argument was that, in environments where transactions are small in frequency, but large in magnitude ($&rsquo;s), the traditional approach to forecasting destroys information &mdash; rather than creating it.</p>
<h3>The traditional approach: statistics</h3>
<p>Here&rsquo;s an example.</p>
<p>Let&rsquo;s assume that you are the manager of a project environment in a technology company.&nbsp; Your job is to deploy teams of technical experts to deliver large projects that have been sold by your sales department.</p>
<p>Your challenge is that you need to make resource-allocation decisions based upon both current and future orders.</p>
<p>You ask your sales department for an estimate of future sales and &mdash; after much gnashing of teeth and grinding of gears &mdash; you are provided with a forecast.&nbsp; This forecast advises that sales next month will be $653k; the following month: $432k; and so on.</p>
<p>These numbers seem strangely precise, considering that they are estimates.&nbsp; Furthermore, the forecast doesn&rsquo;t give you any indication of how confident you should be of these estimates falling within a particular range of values.</p>
<p>Suspicious; you ask the head of sales how these numbers were compiled.&nbsp; He advises that the following method was used:</p>
<ol>
<li>Salespeople used a set of rules to assign a probability to each opportunity upon which they are working (these rules prompt salespeople to consider factors like number of competitors, seniority of decision-makers, and so on).</li>
<li>Salespeople&rsquo;s data was aggregated so as to provide a risk-adjusted estimate of future orders by calendar month.</li>
</ol>
<p>Ask yourself, how useful is this forecast?</p>
<p>The forecast tells you that orders in two months&rsquo; time will total $297k.&nbsp; When you enquire into this number you discover that it primarily consists of a $635k order that Sales believe they have a 34% probability of winning.</p>
<p>What decisions can you make on the basis of this estimate?&nbsp; Can you set-aside 34% of the necessary resources?&nbsp; Should you recruit new personnel?&nbsp; And, in either case, can you pay for these resources using the $216k revenue that constitutes the risk-adjusted value of the $635k sale ($635k x 34%)?</p>
<p>Of course not.</p>
<p>If Sales fails to win that order in two months&rsquo; time as projected, the project will place no demand whatsoever on your resource pool, and will generate precisely $0 in revenues!</p>
<p>To use statistics in this environment is obviously foolish because orders are won so infrequently.&nbsp; The problem is compounded by assigning probabilities to opportunities based primarily upon salespeople&rsquo;s (subjective) opinions.</p>
<p>So, if this approach is so obviously foolish, why do so many organisations adopt it?</p>
<p>I can think of a handful of reasons:</p>
<ol>
<li>Because it <i>does </i>make sense in environments where transactions are high in frequency and low in magnitude</li>
<li>Because it appears (at first glance) to be scientific</li>
<li>Because senior management (or other departments) demand it</li>
<li>Because the CRM came with this capability built-in</li>
<li>Because no one is aware of an alternative approach</li>
</ol>
<h3>An alternate approach: heuristics</h3>
<p>Let me propose an alternative approach &mdash; the approach we use internally.</p>
<p>But first, let&rsquo;s remind ourselves that, because the dataset upon which we are reporting is not statistically significant, our approach <i>must not </i>make use of statistics.</p>
<p>The alternative approach is remarkably simple.</p>
<p>Sales maintains two sets of assumptions for each opportunity:</p>
<ol>
<li>Optimistic (but not exuberant)</li>
<li>Pessimistic (but not paranoid)</li>
</ol>
<p>So, for each of the critical opportunity variables (<i>opportunity value </i>and <i>commencement month</i>) both an optimistic and a pessimistic value is recorded &mdash; and revised weekly.&nbsp; These values are <i>not </i>calculated, they are arrived at by discussion in sales meetings.&nbsp; In other words, a value for each variable is <i>negotiated </i>by the salesperson, the sales coordinator and the sales manager.</p>
<p>Then, each week, two <i>scenarios </i>are created for distribution to senior management (and other departments) &mdash; the optimistic and the pessimistic scenario.&nbsp; Each scenario details specific projects (and the full value of each) &mdash; as opposed to risk-adjusted aggregates.&nbsp;Ideally, each scenario will also detail resourcing and cashflow implications.</p>
<p>Each department then uses these two scenarios to plan as best they can.</p>
<h3>What happened to precision?</h3>
<p>At first glance the second (heuristic) approach lacks the precision of the traditional approach to forecasting (statistical).</p>
<p>However, upon closer examination it becomes obvious that the precision of the traditional approach is an illusion.&nbsp; Contrary to popular belief, the mathematical manipulation of salespeople&rsquo;s opinions does not convert subjective data into objective information.</p>
<p>The heuristic approach acknowledges the existence of uncertainty, rather than disguising it.&nbsp; Accordingly, it is significantly more useful to those who intend to use the reports provided by sales to make actual business decisions.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.salesprocessengineering.net/2008/11/11/an-alternative-to-forecasting-in-major-account-sales-environments/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>Sales forecasts: hocus-pocus with a dollar sign!</title>
		<link>http://www.salesprocessengineering.net/2008/08/11/sales-forecasts-hocus-pocus-with-a-dollar-sign/</link>
		<comments>http://www.salesprocessengineering.net/2008/08/11/sales-forecasts-hocus-pocus-with-a-dollar-sign/#comments</comments>
		<pubDate>Mon, 11 Aug 2008 07:44:08 +0000</pubDate>
		<dc:creator>Justin Roff-Marsh</dc:creator>
				<category><![CDATA[Measures and General Management]]></category>
		<category><![CDATA[Slaying Sacred Cows]]></category>
		<category><![CDATA[forecasting]]></category>
		<category><![CDATA[sales forecast]]></category>

		<guid isPermaLink="false">http://www.salesprocessengineering.net/2008/08/11/sales-forecasts-hocus-pocus-with-a-dollar-sign/</guid>
		<description><![CDATA[The emergence of cargo cults on some Pacific Islands after World War II is an amusing and oft-repeated story. The relatively primitive lifestyles of these islanders were interrupted by Japanese aircraft dropping large supplies of clothing, medicine, canned food and tents to support the Japanese war effort. Some of these supplies were shared with islanders, [...]]]></description>
			<content:encoded><![CDATA[<p>The emergence of <i>cargo cults</i> on some Pacific Islands after World War II is an amusing and oft-repeated story.</p>
<p>The relatively primitive lifestyles of these islanders were interrupted by Japanese aircraft dropping large supplies of clothing, medicine, canned food and tents to support the Japanese war effort.</p>
<p>Some of these supplies were shared with islanders, in exchange for their assistance.</p>
<p>After the war, when planes and their valuable cargos disappeared, some islanders took to imitating the <i>rituals</i> they&rsquo;d observed the Japanese performing.&nbsp;They carved <span>headphones from wood and wore them while sitting in fabricated control towers. &nbsp;And they waved landing signals while standing on abandoned runways.</span></p>
<p>I&rsquo;ve noticed the emergence of a similar <i>cargo cult</i> in organisations in recent years &mdash; particularly those organisations that sell <i>major</i> products and services.</p>
<p>Sales departments have observed a rapid evolution in the performance of their organisations&rsquo; operations departments.&nbsp;They&rsquo;ve seen outputs increase by orders of magnitude.&nbsp;And they&rsquo;ve seen quality and on-time performance improve by similar degrees.</p>
<p>Of course, sales departments have also observed that these performance improvements have been accompanied by an increase in the usage of mathematics in operations &mdash; and, particularly, an increase in the role of statistics.</p>
<p>Sales departments have taken to imitating these <i>rituals</i> &mdash; in the hope that they will have a similar effect on the performance of their departments.&nbsp;Increasingly, we&rsquo;re seeing mathematical models, sophisticated databases and business intelligence tools being applied in the pursuit of greater (or more consistent) sales results.</p>
<p>What sales departments fail to recognise, however, is that operations uses such tools to measure (and predict) the behaviour of processes that are <i>inherently measureable</i>.&nbsp;Sales processes, for the most part, are not.</p>
<p>Let&rsquo;s consider the practice of <i>sales forecasting</i>: a perfect example of this management <i>hocus-pocus.</i></p>
<p>In most major-account sales environments, salespeople are expected to regularly enter data into their firms&rsquo; CRM&rsquo;s, reporting on the status of sales opportunities and the activities performed in pursuit of these opportunities.&nbsp;This data is then manipulated by management and used to estimate month-by-month revenue numbers.&nbsp;These revenue numbers are then provided to operations so that they can be used to determine production quotas and raw-material requirements; as well as to update cashflow models.</p>
<p>At first glance this practice sounds sensible enough.&nbsp;However, we don&rsquo;t have to dig far beneath the surface to realise that the mathematics is not quite as elegant as it appears!</p>
<p>The first thing that we should recognise is that, in most organisations, major sales are landed quite infrequently.&nbsp;This is due, in part, to the fact that salespeople dedicate only a small amount of their time to business-development (selling) activities.&nbsp;Most of their time is consumed by customer-service and clerical tasks, and fulfilment-related activities.&nbsp;(Believe it or not, a typical salesperson performs just two business-development appointments a week.)</p>
<p>Aside from infrequent major sales, another symptom of salespeople&rsquo;s limited business-development activity is a shortage of smaller sales.&nbsp;(Salespeople&rsquo;s limited capacity and their performance-based pay cause them to focus on larger transactions.)</p>
<p>Because salespeople dedicate only a small amount of their capacity to selling, it follows that the organisation has only a small number of opportunities under management at any one point in time.&nbsp;Management must scrutinise this small dataset and somehow predict the month-by-month emergence of major (and infrequent) orders.</p>
<p>In most organisations, management should recognise the impossibility of this undertaking and resolve that it has as much chance of predicting sales revenue in three months time as it does the weather!</p>
<p>But management is not so easily deterred.&nbsp;It is true that there are only a small number of opportunities under management.&nbsp;However, management has been insisting that salespeople enter an increasing volume of data relating to each opportunity into the CRM.&nbsp;The assumption is that more data means more accurate predictions.</p>
<p>Let&rsquo;s consider the nature and source of this data and the conditions under which it is collected.</p>
<p>Aside from minimal amounts of objective data, salespeople are expected to enter numerous <i>best-guesses</i> relating to everything from customer predispositions to competitor intentions.&nbsp;Even much of the data that appears to be objective at first glance reveals itself as otherwise under close scrutiny.&nbsp;For example, even though the opportunity-management process is divided into a series of milestones, the achievement of few of these milestones is actually signalled by unambiguous customer behaviour.</p>
<p>What&rsquo;s even scarier is that few organisations have an objective definition of <i>sales opportunity</i>.&nbsp;It&rsquo;s a common phenomenon for major opportunities to appear in the CRM just days before they are won when, in reality, opportunities of this size would have required months&rsquo; worth of work.</p>
<p>The prevailing assumption in sales departments seems to be that if we take a large number of subjective data and multiply them together, the process of multiplication will somehow furnish us with an objective result.</p>
<p>But it gets worse.&nbsp;The inaccuracy of the data in the CRM is not just limited by salespeople&rsquo;s personal biases.&nbsp;In most cases the problem is compounded by the fact that salespeople enter data into the CRM weekly (as opposed to daily) and by the fact that management provides opportunities and incentives (of various kinds) to salespeople to <i>game the system</i> by flavouring the data that they enter.</p>
<p>Now the lunacy of this pointless and time-consuming exercise does not escape operations.&nbsp;In most organisations, finance and production have concluded that their best-guesses are more accurate than the numbers delivered by the sales department&rsquo;s elaborate models.&nbsp;If these forecasts <i>are</i> put to use, it&rsquo;s more likely that they will be used as ammunition in the ongoing rivalry between operations and sales!</p>
<p>If the sales department wishes to remedy this problem, there are two obvious courses of action.&nbsp;It can either accept that forecasts in which operations cannot have the necessary degree of confidence are of <i>less value</i> than no forecasts at all &mdash; and stop producing them.&nbsp;Or it can figure out how to reengineer the sales department so that its output becomes predictable.</p>
<p>At a minimum, the latter course of action would require that salespeople spend the majority of their time selling &mdash; and that they pursue a sensible mix of major and minor sales.&nbsp;It would require an objective definition of <i>sales opportunity</i>, and milestones that are achieved <i>only</i> when potential customers exhibit unambiguous behaviours (customer opinions are worthless).&nbsp;And it would require that the responsibility for scheduling salespeople&rsquo;s activities and compiling reports be removed from salespeople.</p>
<p>Of course, if management were to examine operations <i>carefully</i>, it would discover that operation&rsquo;s mathematical models and scientific methods <i>begin</i> with the careful collection of objective data.&nbsp;Operations people know that garbage in equals garbage out.</p>
<p>Even though some Pacific Island cargo cults persist to this day, Islanders&rsquo; rituals are as unproductive now as they were in the nineteen-fifties.</p>
<p>It&rsquo;s time that sales departments recognise that the root cause of inaccurate sales forecasts has <i>nothing at all</i> to do with inferior mathematical models and insufficient technology.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.salesprocessengineering.net/2008/08/11/sales-forecasts-hocus-pocus-with-a-dollar-sign/feed/</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
	</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Minified using disk: basic
Page Caching using disk: enhanced

Served from: www.salesprocessengineering.net @ 2012-02-05 19:03:15 -->
