<?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; throughput</title>
	<atom:link href="http://www.salesprocessengineering.net/tag/throughput/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>How to build an objective management structure for your sales process</title>
		<link>http://www.salesprocessengineering.net/2008/07/22/how-to-build-an-objective-management-structure-for-your-sales-process/</link>
		<comments>http://www.salesprocessengineering.net/2008/07/22/how-to-build-an-objective-management-structure-for-your-sales-process/#comments</comments>
		<pubDate>Tue, 22 Jul 2008 11:43:37 +0000</pubDate>
		<dc:creator></dc:creator>
				<category><![CDATA[Applying Sales Process Engineering]]></category>
		<category><![CDATA[measurement]]></category>
		<category><![CDATA[opportunity management]]></category>
		<category><![CDATA[sales]]></category>
		<category><![CDATA[sales process]]></category>
		<category><![CDATA[throughput]]></category>
		<category><![CDATA[toc]]></category>

		<guid isPermaLink="false">http://www.salesprocessengineering.net/2008/07/22/how-to-build-an-objective-management-structure-for-your-sales-process/</guid>
		<description><![CDATA[Imagine you were to awaken one morning suffering from a strange disorder: one that rendered your eyesight unreliable. When you open your eyes, your bedroom appears roughly as it did the night before. Your bed is below the open window, and your dresser is still adjacent to the door. However, a second look reveals that [...]]]></description>
			<content:encoded><![CDATA[<p><img align="right" src="http://www.salesprocessengineering.net/wp-content/uploads/image/objective_mgmt_image.jpg" alt="sales process engineering" />Imagine you were to awaken one morning suffering from a strange disorder: one that rendered your eyesight unreliable.</p>
<p>When you open your eyes, your bedroom appears roughly as it did the night before. Your bed is below the open window, and your dresser is still adjacent to the door.</p>
<p>However, a second look reveals that the curtains that normally hang above your windows are missing. As is the painting that normally hangs, slightly crooked, on the wall facing your bed.</p>
<p>What&rsquo;s more, you notice some strange additions to your bedroom furnishings. A plaster bust now dominates your dresser. And an empty hat rack leans precariously against your bed head.</p>
<p>As you rise and navigate your way around your bedroom, you discover that your memory provides the accurate version of reality. In spite of the information tendered by your eyes, your curtains still hang above your open window, and your painting still adorns the wall adjacent to your bed. Your sense of touch confirms that there is no plaster bust on your dresser, and that the hat rack is also a mirage.</p>
<p>You only have to spend a day in a typical marketing or sales department to discover that this scenario is analogous to the environment in which management operates.</p>
<p>Various reports and performance indicators (both formal and informal) provide glimpses of reality. However, this feedback falls short of delivering the accurate and complete viewthat managers need in order to be truly effective.</p>
<p>When hobbled with an incomplete and unreliable view of reality, managers&rsquo; activities are, at best, inefficient and risk-adverse. At worst, managers unknowingly engage in activities that are harmful to the organisation as a whole.</p>
<p>Hence the need for an objective management structure!</p>
<h3>Reality</h3>
<p>By definition, reality must be the starting point for an objective management structure.</p>
<p>Without the ability to accurately perceive reality, measurement and, accordingly, management is impossible.</p>
<p>Of course, the concept of measurement presupposes something to measure.</p>
<p>This means that the ability to perceive reality is not enough. We need also to determine upon what aspect of reality we should focus.</p>
<p>It is perhaps self-evident that our focus must be determined by our goal. After all, a measurement out of context with a goal is just a number (data, not information).</p>
<p>If your goal were to drive from Sydney to Darwin, your current location, speed and direction of travel are information; the weather in Perth is data.</p>
<p>For this reason, the most critical step in designing an objective management structure is defining your goal.</p>
<p>I&rsquo;ve had many managers assure me that this is also self-evident:</p>
<p>Marketing managers tell me that it&rsquo;s their goal to generate sales opportunities.</p>
<p>Sales managers advise me that their goal is to generate sales.</p>
<p>In each instance, managers forget that the processes they manage are part of a larger system. As a result, they fail to recognise that their goal must be subordinated to the goal of the system.</p>
<h3>One system, one goal!</h3>
<p>For simplicity, let&rsquo;s define a system as a set of interdependent processes.</p>
<p>A fine example of a system &mdash; one with which we&rsquo;re all familiar &mdash; is an internal combustion engine (pictured below).</p>
<p align="center"><img src="http://www.salesprocessengineering.net/wp-content/uploads/image/Engine.gif" alt="sales process engineering" /></p>
<p>As you no doubt know from your experience with this particular system, the goal of the internal combustion engine is to generate torque (rotational force).</p>
<p>As depicted above, this system consists of four processes:</p>
<ol>
<li><strong>INTAKE</strong> (a mixture of fuel and air is drawn into the cylinder).</li>
<li><strong>COMPRESSION</strong> (this mixture is compressed by the rising piston).</li>
<li><strong>COMBUSTION</strong> (the fuel/air mix is ignited by the sparkplug).</li>
<li><strong>EXHAUST</strong> (the resulting exhaust gasses are expelled from the cylinder).</li>
</ol>
<p>Now, consider this question for me:</p>
<p>If you were the sparkplug in this system, what would be your goal?</p>
<ol>
<li>Would it simply be to generate sparks (as many as possible)?</li>
<li>Or would it be to generate (a set quota of, say) 10 sparks a second?</li>
</ol>
<p>Of course, neither answer is correct.</p>
<p>Your goal could only be expressed in terms that recognise the relationship between your activities and the goal of the system.</p>
<p>Accordingly, your goal would be something like the following:</p>
<p style="margin-left: 40px;"><i>To produce a spark at the top of each compression stroke.*</i></p>
<p>* Technically, the sparkplug produces a spark fractionally before the top of the compression stroke.</p>
<p>If your goal must be subordinated to the goal of the system, it&rsquo;s essential for us to identify your organisation&rsquo;s goal.</p>
<h3>Why does this organisation exist?</h3>
<p>Whenever I ask this question of a seminar audience, I get a range of answers:</p>
<ol>
<li>Some managers claim that their organisations exist to manufacture widgets.</li>
<li>Others explain that their organisational goal is produce happy customers.</li>
<li>Others try and cover all bases with statements that reference the organisation&iexcl;&macr;s relationship with all stakeholders (shareholders, staff, the community, the goldfish in the corporate pond etc.)</li>
</ol>
<p>In each instance, managers are confusing the goal of their organisations with necessary conditions.</p>
<p>The goal of any commercial organisation is, by definition, to make money.* Necessary conditions are the conditions that must be present to enable this goal to be achieved.</p>
<p>* Goldratt (whose work has had a significant impact on the thinking behind this article) explains that the goal of a business is to make money, now and in the future. I would argue (as, in fact, does he) that the latter part of this statement is redundant (we&rsquo;re all accustomed to recognising the value of future revenues). To learn more of Goldratt&rsquo;s work, begin by reading The Goal.</p>
<p>While the idea that the goal of a commercial organisation is to make money may initially cause managers some discomfort (believe me, it does), it also provides the clarity we need to start to piece together our objective management structure.</p>
<h3>Unravelling organisational complexity</h3>
<p>As our internal combustion example illustrated, all goals at a process level must reflect the contribution that the process makes to the goal of the system as a whole.</p>
<p>Unfortunately, organisations tend not to be as simple as our little engine.</p>
<p>In fact, one of the greatest challenges faced by managers is the requirement to understand the interaction between multiple organisational processes.</p>
<p>As has been explained in recent editions of AdVerb, this challenge has been greatly simplified by Goldratt&rsquo;s Theory of Constraints (TOC).</p>
<p>In short, TOC recognises that the output of any system is determined by the system&rsquo;s constraint (or bottleneck). It also points out that:</p>
<ol>
<li>Every system has a constraint (if it didn&rsquo;t, output would be infinite).</li>
<li>At any one point in time, every system has only one constraint.</li>
<li>A stable system is one where the constraint remains in one location.</li>
<li>Because the constraint is the sole determinate of system output, every management decision should reference the constraint.</li>
<li>The investment of resources in any non-constrained process or activity will produce absolutely no return (contrary to the assumptions that underpin cost accounting).</li>
</ol>
<p>An understanding of TOC enables a manager to ignore organisational complexity when making decisions, and simply consider the impact that the options under consideration will have on the system&rsquo;s constraint.</p>
<p>Now, because the goal of the organisation is to make money, when we&rsquo;re discussing system output, what we&rsquo;re really talking about is money. And when we&rsquo;re discussing the system&rsquo;s constraint, our consideration is the flow of money at the constraint.</p>
<p>TOC practitioners use a simple formula to express this concept:</p>
<p style="margin-left: 40px;"><i>Flow of Money = Throughput / Available Constraint Units</i></p>
<p>Throughput (T) refers to revenue minus totally variable costs (true gross profit).</p>
<p>Available Constraint Units (ACU) refers to the number of units of constraint that are available over the period of consideration. (If the constraint is a machine, the Constraint Unit is likely to be time-based. If the constraint is a salesperson, the Constraint Unit will be an appointment slot.)</p>
<p>As we&rsquo;ve established, the goal of every process within our organisational system should reference the organisational goal: maximising the flow of money at the system&rsquo;s constraint (or T/ACU).</p>
<p>Let&rsquo;s pause now, for a practical example.</p>
<h3>A two-process organisational system</h3>
<p>Consider the simple organisation pictured below.</p>
<p align="center"><img src="http://www.salesprocessengineering.net/wp-content/uploads/image/org1.gif" alt="sales process engineering" /></p>
<p>If we assume that the constraint in the organisation above is in the production process, what is the goal of the sales process?</p>
<p>Is it to produce as many sales as possible?</p>
<p>Obviously not!</p>
<p>The sales process should produce enough sales to ensure that the production process operates at peak capacity, all the time. To produce more sales than this would waste resources (and annoy the marketplace).</p>
<p>But, that&rsquo;s only the half of it.</p>
<p>If the production process is constrained, the sales process should also produce the kind of sales that are going to deliver the greatest return on the Constraint Units consumed.</p>
<p>Here&rsquo;s the solution:</p>
<p align="center"><img src="http://www.salesprocessengineering.net/wp-content/uploads/image/org2.gif" alt="sales process engineering" /></p>
<p>System Goal: maximise T/ACU (measured at point of sale).</p>
<p>Production Process Goal: maximise T/CU (measured at point of sale).</p>
<p>Sales Process Goal: maintain a production buffer of optimal size (x days&rsquo; worth of unstarted work in progress). Maximise the value of the production buffer (T/CU).</p>
<p>To translate this into plain English:</p>
<p>The goal of our simple organisation is to maximise the yield (Throughput) it gets on its Available Constraint Units. (Because the output of a system is determined by the system&rsquo;s constraint, this is equivalent to saying that the goal of the organisation is to make money.)</p>
<p>The goal of the production process is to maximise the yield it earns on every Constraint Unit it consumes.</p>
<p>The goal of the sales process is to:</p>
<ul>
<li>Maintain a buffer (or inventory) of unstarted work in progress (or orders) of an optimal size. If this production buffer is too small, there is a risk that the production process may sit idle from time to time. If it is too large, this indicates that the sales process is wasting resources that would be better deployed at the constraint.</li>
<li>Maximise the value of the production buffer. The value of the buffer is the total Throughput that the buffer represents, divided by the number of Constraint Units that will be consumed to realise this Throughput. The inference here is that not all Throughput dollars are equal in this scenario. The sales process must focus on winning the sales that produce the greatest yield on the scarce Constraint Units.</li>
</ul>
<h3>The sales process dissected</h3>
<p>We have now accumulated all the theory we need to apply our focus to the sales process.</p>
<p>I&rsquo;m going to assume for simplicity&rsquo;s sake (and because it is often the reality) that your system constraint is your sales process. In other words, I&rsquo;m assuming that your production process can handle all the sales that your sales process produces (at least for the duration of this discussion).</p>
<p>Because we&rsquo;re now shifting our focus from the system (which is a collection of processes), to one particular process within that system, we&rsquo;re now going to have to think at a more granular level.</p>
<p>Our interest now shifts from determining which process is constrained to determining the exact location of the constraint within the constrained process.</p>
<p>Let&rsquo;s consider a simple sales process (designed around Relationship-centric guidelines), containing three personnel:</p>
<p align="center"><img src="http://www.salesprocessengineering.net/wp-content/uploads/image/salesprocess1.gif" alt="sales process engineering" /></p>
<p>The basic responsibilities of each person are:</p>
<ol>
<li>Marketing Coordinator. Producing sales opportunities.</li>
<li>Sales Coordinator. Managing the salesperson&rsquo;s diary.</li>
<li>Salesperson. Negotiating transactions.</li>
</ol>
<p>Before we even attempt to manage this process, we need to determine exactly where the constraint is.</p>
<p>Now, the nice thing about operating at this level of granularity is that you get to choose! At this level, it&rsquo;s quite easy for you to shift resources around to ensure that the constraint is exactly where you want it to be (and to ensure that it stays there).</p>
<p>If you consider that, in any process, by definition, it is only the constraint that operates at 100% capacity, ask yourself, who in the process above would you least like to be idle?</p>
<p>It&rsquo;s obvious, isn&rsquo;t it?</p>
<p>You would like your salesperson to be operating at 100% capacity, all the time. This is because your sales process will generate a greater flow of Throughput when your salesperson is fully utilised than it will when either your sales or marketing coordinator is flat-out (and your salesperson has idle time).</p>
<p>If you want to ensure that your salesperson is the constraint (and stays that way), you simply over-resource the marketing coordinator and the sales coordinator. In practical terms, this means ensuring that they never have to operate at full capacity (at least where their critical tasks are concerned).</p>
<p>As we did in our previous example, we&rsquo;re going to take one more precaution to ensure that the constraint stays put.</p>
<p>We&rsquo;re going to build an inventory (or buffer) of unallocated sales opportunities to ensure that the salesperson never has to sit idle.</p>
<p>The resulting process is pictured below:</p>
<p align="center"><img align="middle" src="http://www.salesprocessengineering.net/wp-content/uploads/image/salesprocess2.gif" alt="sales process engineering" /></p>
<p>Now, let&rsquo;s apply the same logic to this sales process that we applied a moment ago to our simple organisational system.</p>
<p>We should first remind ourselves that the sales process pictured above is part of a larger system &iexcl;&ordf; the business as a whole.</p>
<p>We already know that the goal of that system is to make money.</p>
<p>We also know that the money that the system makes is determined by the organisational constraint, which happens to be the salesperson.</p>
<p>The salesperson&rsquo;s Constraint Unit is an appointment slot.</p>
<p>&nbsp;Accordingly, the goal of the system as a whole is to maximise T/ACU (or Throughput / Available Appointment Slot).</p>
<p>Now, if we shift our focus to the sales process, it is obvious that the goal of the sales process must be the same as the goal of the system. (The sales process is the constrained process.)</p>
<p>Let&rsquo;s look now at each of the personnel operating within the sales process.</p>
<p>The salesperson&rsquo;s goal should be to maximise his Throughput per appointment slot consumed (or Throughput / Appointment). It&rsquo;s worth noting that the salesperson&rsquo;s goal is not simply to maximise Throughput, nor is it to maximise his conversion rate. Each of these goals is likely to result in behaviour that is sub-optimal in the context of the system as a whole.</p>
<p>The sales coordinator&rsquo;s goal is to keep the salesperson fully utilised. In other words, it is her responsibility to ensure that every available appointment slot is filled. (An empty appointment slot represents an opportunity cost equivalent to the average Throughput / Appointment).</p>
<p>As you&rsquo;ve no doubt guessed, the marketing coordinator is responsible for both the size and the quality of the opportunity buffer. The buffer should be maintained at its optimal size (measured in days&iexcl;&macr; worth of appointments). It should also be composed of opportunities that are likely to yield the highest Throughput / Appointment.</p>
<p>Now that we have established an objective (and systemically congruent) goal for each person in our sales process, performance indicators are pretty much self evident:</p>
<table cellspacing="0" cellpadding="0">
<tbody>
<tr>
<th>Function</th>
<th>Goal</th>
<th>Performance Indicator</th>
</tr>
<tr valign="top">
<td><strong>Sales Process </strong></td>
<td>Maximise yield on Salesperson</td>
<td>Throughput / Available Appointment Slot</td>
</tr>
<tr valign="top" class="odd">
<td><strong>Salesperson</strong></td>
<td>Maximise yield on Appointments</td>
<td>Throughput / Appointment</td>
</tr>
<tr valign="top">
<td><strong>Sales Coordinator </strong></td>
<td>Ensure salesperson is fully utilised</td>
<td>% of Optimal Utilisation<br />
            (Optimal Utilisation is 100%)</td>
</tr>
<tr valign="top" class="odd">
<td><strong>Marketing Coordinator</strong>
</td>
<td>Maintain opportunity buffer at optimal size.<br />
Maximise value of opportunity buffer</td>
<td>% of Optimal Days.<br />
<img src="http://www.salesprocessengineering.net/wp-content/uploads/image/sigma.gif" alt="" />{Throughput / Appointment Slots x Probability}*</td>
</tr>
</tbody>
</table>
<p>*<img src="http://www.salesprocessengineering.net/wp-content/uploads/image/sigma.gif" alt="" /> means sum of. Throughput, Appointment Slots and Probability are all estimates. Probability refers to the probability of your converting that opportunity.</p>
<h3>Management just got easier</h3>
<p>Well there it is: an objective sales process management structure!</p>
<p>Each person&rsquo;s goal (and the accompanying performance indicator) is congruent with the goal of the system as a whole &iexcl;&ordf; and, accordingly, is reality based.</p>
<p>Each performance indicator is quantitative, rather than qualitative, meaning that no subjective interpretation of results is required.</p>
<p>Each person has only one or two performance indicators (one is optimal), meaning that there is no confusion as to what she should be doing, and how she will be judged.</p>
<p>Each person is likely to have a clear understanding of the contribution she makes to the success (or otherwise) of the system as a whole. As well as being good for morale, this discourages the development of political factions.</p>
<h3>Creating a productive environment</h3>
<p>As I&rsquo;m sure you&rsquo;ve already realised, an objective management structure will make an enormous contribution to organisational productivity.</p>
<p>However, there are three more initiatives we recommend you implement in order to create a truly productive environment.</p>
<ol>
<li>Use run charts. It&rsquo;s one thing to allocate a performance indicator to a team member. It&rsquo;s another to find a way to use this information to positively influence her behaviour. If you remind yourself that a performance indicator is just feedback from the system, the solution is obvious: plot it on a graph. Better still, have each team member plot her performance indicator on a run chart. An example of a run chart follows. This was generated within Excel, however, traditional plotting paper does as good a (and some would argue, better) job. <img src="http://www.salesprocessengineering.net/wp-content/uploads/image/runchart_sm.gif" alt="" /></li>
<li>Eliminate budgets and bonuses. Managers traditionally have attempted to motivate their teams with a cocktail of artificial stimulants. Budgets, bonuses, performance reviews, quotas and management exhortations are tactics invented by management to cope with the lack of an objective management structure. You&rsquo;ll find that, if you simply pay your team members what they&rsquo;re worth &mdash; and have each discuss his or her run chart at a weekly management meeting &iexcl;&ordf; your requirement for these artificial stimulants will rapidly dissipate.</li>
<li>Replace the word maximum with optimum. In this discussion I have taken a shortcut (for the sake of simplicity) and allowed myself to use the word maximum on a couple of occasions. I&rsquo;ve referred to maximising the yield on the constraint and to maximising the value of the opportunity buffer.</li>
</ol>
<p>My preference is, in both cases that you replace the word maximise with optimise.</p>
<p>We&rsquo;ve already discovered that every process (and system) is constrained. What this means is that, if you scale a process, you will eventually reach a point of diminishing returns.</p>
<p>In the case of maximising the yield on the constraint, you may find the constraint moves (which is generally undesirable), or that your ability to grow your business is constrained (it takes time to recruit and train new staff).</p>
<p>In the case of maximising the value of your opportunity buffer, you&rsquo;re likely to find that, past a certain point, increased promotional costs are likely to overwhelm any increase in opportunity value.</p>
<p>Now, in both instances, it will take some experimentation to determine those optimas. However, in the short term, I suggest you aim only for incremental improvements in these (and similar) situations. From a systemic perspective, it is far healthier to aim first for stability, and second for incremental improvement, than it is to set stretch goals. (The latter approach is guaranteed to wreak havoc elsewhere in the system.)</p>
<p>My thanks to James Powell (Viago), who provided technical assistance for this article. Viago assists organisations to apply TOC to production processes. <a href="www.viago.com.au" target="_blank">www.viago.com.au</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.salesprocessengineering.net/2008/07/22/how-to-build-an-objective-management-structure-for-your-sales-process/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>How to build a high-throughput sales process</title>
		<link>http://www.salesprocessengineering.net/2008/07/18/how-to-build-a-high-throughput-sales-process/</link>
		<comments>http://www.salesprocessengineering.net/2008/07/18/how-to-build-a-high-throughput-sales-process/#comments</comments>
		<pubDate>Fri, 18 Jul 2008 11:42:35 +0000</pubDate>
		<dc:creator></dc:creator>
				<category><![CDATA[Applying Sales Process Engineering]]></category>
		<category><![CDATA[measurement]]></category>
		<category><![CDATA[opportunity management]]></category>
		<category><![CDATA[relationship acquisition]]></category>
		<category><![CDATA[sales]]></category>
		<category><![CDATA[sales process]]></category>
		<category><![CDATA[throughput]]></category>
		<category><![CDATA[toc]]></category>

		<guid isPermaLink="false">http://www.salesprocessengineering.net/2008/07/18/how-to-build-a-high-throughput-sales-process/</guid>
		<description><![CDATA[Applying the Theory of Constraints to the design, resourcing and management of the sales process [Presented at: TOCICO Conference, Miami 2004] Introduction The traditional sales process is hard to manage and all but impossible to scale. This paper introduces a radical new approach to sales process design, resourcing and management. The result of this approach [...]]]></description>
			<content:encoded><![CDATA[<h3><img alt="the goal" align="right" src="http://www.salesprocessengineering.net/wp-content/uploads/image/the_goal.jpg" />Applying the Theory of Constraints to the design, resourcing and management of the sales process</h3>
<p>[Presented at: TOCICO Conference, Miami 2004]</p>
<h3>Introduction</h3>
<p>The traditional sales process is hard to manage and all but impossible to scale.</p>
<p>This paper introduces a radical new approach to sales process design, resourcing and management.</p>
<p>The result of this approach is a process where:</p>
<ol>
<li>Salespeople consistently perform five appointments a day, five days a week.</li>
<li>Appointments are programmed into salespeople&rsquo;s diaries in descending order of probable contribution.</li>
<li>A buffer of sales opportunities is generated and maintained, without requiring any involvement of salespeople.</li>
<li>Budgets, targets, bonuses and commissions are eliminated and all activities are synchronised (in real-time) with the goal* of the organisation.</li>
</ol>
<h3>The problem with the sales process</h3>
<p>Most sales processes are not processes in any useful sense of the word.</p>
<p>In a production context, the word process conjures up images of a production line &mdash; a series of tightly-coordinated activities that deftly converts raw materials into finished goods.</p>
<p>A typical sales process hardly fits this description.</p>
<p>A typical sales process consists of a number of individuals, each of whom is responsible for the entire sales function (and for a number of non-sales activities). Rather than following any formal procedure, these individuals engage in a broad range of ad hoc activities &mdash; using intuition to make resource allocation decisions.</p>
<p>A typical sales process is not dissimilar to a manufacturing process prior to the industrial revolution:</p>
<ol>
<li>All tasks are performed by skilled technicians.</li>
<li>There is minimal automation.</li>
<li>Each technician operates in parallel with others &mdash; rather than in series. Accordingly, each worker is responsible for his own end-to-end process.</li>
<li>There is enormous variation in output.</li>
<li>Because there are no economies of scale, the system is difficult to scale.</li>
<li>Technicians receive performance pay, meaning that they are inclined to behave like sub-contractors</li>
<li>There are no disincentives for technicians to set up their own competitive businesses.</li>
</ol>
<p align="center"><img alt="the goal" src="http://www.salesprocessengineering.net/wp-content/uploads/image/ParallelSerial.gif" /></p>
<p>(Technically, it makes sense to apply the word &#8216;process&#8217; only to the latter configuration in the diagram above.)</p>
<p>Fortunately, if we are looking to increase the productivity of the sales process, modern manufacturing provides us with clear guidance.</p>
<h3>Applying TOC to the sales process</h3>
<p>TOC&rsquo;s five focusing steps* advise us to begin by identifying the constraint.</p>
<p>Because the salesperson is the traditional sales process&rsquo;s only resource, it&rsquo;s obvious that the salesperson is the capacity constrained resource (CCR).</p>
<p>To determine how to exploit the CCR, we&rsquo;ll perform a simple time and motion study.</p>
<p>A review of a typical salesperson&rsquo;s time and activities is likely to reveal the following breakdown of activities:</p>
<p align="center"><img alt="the goal" src="http://www.salesprocessengineering.net/wp-content/uploads/image/TandMotion.gif" /></p>
<p>As illustrated, a typical salesperson conducts just two business-development appointments a week.</p>
<p>The balance of his time is allocated to:</p>
<ol>
<li>Project management: managing the delivery of prior sales</li>
<li>Customer service: receiving and processing repeat transactions</li>
<li>Opportunity management and clerical tasks: activity programming, diary management, data entry and literature fulfilment</li>
<li>Social activities: appointments with no formal business objective, as well as a range of overtly non-commercial activities (often involving sport)</li>
<li>Prospecting: identifying sales opportunities</li>
</ol>
<p>The following table ranks these activities by time allocated (descending order) and by the contribution each activity makes to Throughput*.</p>
<table cellspacing="0" cellpadding="0">
<tbody>
<tr>
<td>
<p><strong>Activity</strong></p>
</td>
<td valign="top">
<p align="center"><strong>Time allocated</strong></p>
</td>
<td valign="top">
<p align="center"><strong>Contrib. to T&rsquo;put</strong></p>
</td>
</tr>
<tr>
<td valign="top">
<p>Project management</p>
</td>
<td valign="top">
<p align="center">1</p>
</td>
<td valign="top">
<p align="center">NA</p>
</td>
</tr>
<tr>
<td valign="top">
<p>Customer service</p>
</td>
<td valign="top">
<p align="center">2</p>
</td>
<td valign="top">
<p align="center">NA</p>
</td>
</tr>
<tr>
<td valign="top">
<p>Opportunity management and clerical tasks</p>
</td>
<td valign="top">
<p align="center">3</p>
</td>
<td valign="top">
<p align="center">3</p>
</td>
</tr>
<tr>
<td valign="top">
<p>Social activities</p>
</td>
<td valign="top">
<p align="center">4</p>
</td>
<td valign="top">
<p align="center">NA</p>
</td>
</tr>
<tr>
<td valign="top">
<p>Prospecting</p>
</td>
<td valign="top">
<p align="center">5</p>
</td>
<td valign="top">
<p align="center">2</p>
</td>
</tr>
<tr>
<td valign="top">
<p>Business-development appointments</p>
</td>
<td valign="top">
<p align="center">6</p>
</td>
<td valign="top">
<p align="center">1</p>
</td>
</tr>
</tbody>
</table>
<p>Where the contribution to Throughput is concerned, project management, customer service and social activities are marketed as not applicable. This is because it simply does not make sense to treat these activities as part of the sales process*.</p>
<p>While the exclusion of social activities from the sales process is contentious, we do so for two reasons:</p>
<ol>
<li>We consistently find that we can get a better return on scarce resources from commercial activities than we can from social activities.</li>
<li>Even if social relationships are an antecedent of commercial relationships (which is debatable**), such relationships should be regarded by management as a contingent liability.</li>
</ol>
<p>Of the three remaining activities, business-development appointments obviously make the greatest contribution to Throughput.</p>
<p>These appointments are a higher-probability activity than prospecting. While opportunity management and clerical tasks are necessary, they do not make a direct contribution to Throughput.</p>
<p>Because the conduct of business-development appointments is the salesperson&rsquo;s most productive activity, we will establish the appointment slot as our unit of constraint. In our experience, a salesperson&rsquo;s maximum sustainable capacity is likely to be five appointments a day.*</p>
<p>For this reason, the pie chart on the preceding page, displays time allocated to activities in terms of appointment slots consumed.</p>
<p>It should now be obvious that:</p>
<ol>
<li>Our sales process will be at its most productive when we have maximised Throughput per appointment slot available (T/ASA).</li>
<li>The measure of the contribution of our salesperson to the process as a whole will be Throughput per appointment slot consumed (T/ASC).</li>
</ol>
<p>Accordingly, our focus should now be on:</p>
<ol>
<li>Ensuring that our salesperson is fully utilised (all his available appointment slots are consumed).</li>
<li>Programming activities into our salesperson&rsquo;s diary so as to maximise T/ASC.</li>
</ol>
<h3>A word on programming</h3>
<p>In our experience, neither salespeople nor management are ever likely to have considered a formal approach to the programming of sales activities.</p>
<p>Consequently, salespeople&rsquo;s time tends to be programmed by salespeople themselves &mdash; with intuition as the prevailing method.</p>
<p>Unfortunately, as is illustrated by the popularity of casinos, the human brain does not excel at performing estimates where probability is involved. The result is that low-probability activities are likely to be given priority over higher-probability activities. (Salespeople over-estimate the value of the unknown.)</p>
<p>This has a deleterious effect on both process throughput and conversion rates.*</p>
<h4>The sales coordinator</h4>
<p>In order to maximise both the utilisation and the productivity of the CCR (the salesperson), we focus the salesperson exclusively on business-development appointments and add an upstream resource called a sales coordinator.</p>
<p>The sales coordinator is responsible for ensuring that the salesperson is fully utilised at all times (five business-development appointments a day, five days a week).</p>
<p>Consequently, the sales coordinator takes total control of the salesperson&rsquo;s diary (just as a personal assistant would take control of an executive&rsquo;s diary).</p>
<p>In order to maximise the salesperson&rsquo;s productivity (T/ASC) the sales coordinator allocates appointments in the descending order of their probable contribution. Because the sales coordinator&#8217;s intuition is no more capable of estimating this contribution than the salesperson&rsquo;s, these critical programming decisions are made using a formula provided by management.</p>
<p align="center"><img alt="the goal" src="http://www.salesprocessengineering.net/wp-content/uploads/image/Resourcing1.gif" /></p>
<h4>Feeding the constraint</h4>
<p>As suggested previously, we are only interested in the salesperson performing business-development appointments.</p>
<p>These are appointments with a commercial agenda that has been approved in advance by the potential client.</p>
<p>At some stage, the sales coordinator is likely to find it difficult to schedule appointments that comply with this precondition.</p>
<p>This is because, prior to agreeing to such an appointment, the potential client (prospect) must acknowledge a requirement for the product or service that the salesperson is representing.</p>
<p>While, for most organisations, there is no shortage of prospects, there is a shortage of prospects with a current acknowledged need (this is what we call a sales opportunity).</p>
<p>At this point, we are in danger of the constraint shifting from the salesperson to the sales coordinator.</p>
<p>In order to prevent this from happening, we must:</p>
<ol>
<li>Identify the source of &mdash; and a method to generate &mdash; sales opportunities.</li>
<li>Build a buffer of these opportunities (an opportunity buffer) upstream from the sales coordinator.</li>
</ol>
<p align="center"><img alt="the goal" src="http://www.salesprocessengineering.net/wp-content/uploads/image/Resourcing2.gif" /></p>
<h3>The source of sales opportunities: four theories</h3>
<p>We find that most organisations have designed their sales process based upon one of four theories concerning the (primary) source of sales opportunities:</p>
<ol>
<li>That sales opportunities are a raw material (and, therefore, abundant)</li>
<li>That salespeople create sales opportunities (as a result of their prospecting activities)</li>
<li>That promotional campaigns generate sales opportunities</li>
<li>That existing clients are the source of sales opportunities (either directly, or via referrals)</li>
</ol>
<p>While there is a set of circumstances in which each of these theories is appropriate, few organisations find themselves complying with those circumstances.</p>
<p>The result, for most organisations, is a chronic shortage of sales opportunities. This persistent scarcity of sales opportunities, in turn, encourages organisations to design their sales processes to maximise conversion rates, at the expense of process volume.</p>
<p>The theory that sales opportunities are a raw material is appropriate only for those organisations with a production &mdash; rather than a sales process &mdash; constraint.</p>
<p>The theory that salespeople are the primary source of sales opportunities is applicable only in situations where salespeople can prospect and sell concurrently (e.g. door-to-door sales). In other situations, prospecting is such a resource-intensive activity that it consumes the greater majority of a salesperson&rsquo;s available time.</p>
<p>The theory that promotional campaigns are the primary source of sales opportunities is applicable only to organisations that change their products regularly (entertainment promoters, infomercial marketers, property developers etc). This is because promotional campaigns that directly generate sales opportunities tend to suffer from rapidly-diminishing returns.</p>
<p>The theory that existing clients are the primary source of sales opportunities is appropriate only for organisations with an enormous, under-exploited client base (telecoms, utilities etc). For other organisations, this theory results in a sales process that is a self-contained (self-limiting) system.</p>
<p align="center"><img alt="the goal" src="http://www.salesprocessengineering.net/wp-content/uploads/image/ClientsAsSource.gif" /></p>
<h3>Relationships as a source of sales opportunities</h3>
<p>Curiously, for most organisations, it is true that clients are the primary source of sales opportunities. That said, if the objective is to increase process output at anything other than an incremental rate, it doesn&rsquo;t make sense to look to existing clients to drive this growth.</p>
<p>Our solution is to recognise relationships as the primary source of sales opportunities.</p>
<p>Our interest, then, is not just in customer relationships, but in relationships with the organisation&rsquo;s marketplace as a whole, where this marketplace consists of:</p>
<ol>
<li>Customers</li>
<li>Potential customers</li>
<li>Centers of influence</li>
</ol>
<p>We have observed that, in most instances, there is a predictable, linear correlation (suggesting cause and effect) between the number of relationships an organisation has under management and the volume of inbound, unsolicited sales opportunities.</p>
<p>This phenomenon is dependent upon:</p>
<ol>
<li>A base of relationships that is large enough to be representative of the marketplace</li>
<li>Some kind of periodic and relevant communication with these relationships</li>
</ol>
<p>Of course, this observation supports marketers&rsquo; concept of brand equity. However the marketing community&rsquo;s pseudo-scientific treatment of this concept renders it all but useless.</p>
<p>Considering the significance of this observation, a more systematic approach is appropriate.</p>
<p>Accordingly, if relationships under management are a scalable source of sales opportunities, it makes sense to:</p>
<ol>
<li>Build a database that is as representative as possible of the wider marketplace.</li>
<li>Communicate periodically with individuals on this database, with communications designed to stimulate the emergence of sales opportunities.</li>
</ol>
<h3>The Relationship-centric Sales Process</h3>
<p>This approach results in the following sales process.</p>
<p align="center"><img alt="the goal" src="http://www.salesprocessengineering.net/wp-content/uploads/image/RelCenProcess.gif" /></p>
<p>In summary, this process functions as follows.*</p>
<ol>
<li>Promotional dollars are invested in the acquisition of relationships &mdash; rather than in the direct acquisition of sales opportunities. Relationships are acquired by giving away packaged information (generally a book, white paper, or similar), in exchange for contact information. Because of the relative size of most organisations&rsquo; marketplaces, and the attractiveness of the offer, these campaigns are less prone to diminishing returns.</li>
<li>Respondents are added to a database, subscribed to a periodical and invited to regular events. (Events are, by far, the most effective method for the stimulation of inbound sales opportunities.)</li>
<li>Inbound sales opportunities are managed by the sales coordinator &mdash; where opportunity management consists simply of programming opportunities into the salesperson&rsquo;s diary, in line with an appropriate strategy. (A strategy is the sequence of steps used to convert sales opportunities into sales.)</li>
</ol>
<h4>The promotional coordinator</h4>
<p>Now that we understand the nature of the activities required to generate sales opportunities, we can complete the resourcing of our sales process.</p>
<p>Upstream from the opportunity buffer we add a resource we call a promotional coordinator.</p>
<p>The promotional coordinator is responsible for maintaining the opportunity buffer at its optimal size.</p>
<p>In order to achieve this requirement, the promotional coordinator manages a portfolio of relationship-acquisition and -management campaigns.</p>
<p>We now can be confident that the salesperson is both fully and productively utilised &mdash; and, consequently, that he will remain the capacity constrained resource.</p>
<p align="center"><img alt="the goal" src="http://www.salesprocessengineering.net/wp-content/uploads/image/Resourcing3.gif" /></p>
<h3>Managing the sales process</h3>
<p>Conceptually, there is little difference between the management of a production process and the management of the sales process pictured on the previous page.</p>
<p>What differences there are, stem from the uncertainty associated with Throughput and intangible nature of both relationships and opportunities.</p>
<h3>Throughput</h3>
<p>Obviously, where a sales process is concerned, we are dealing with probable, rather than actual Throughput.</p>
<p>Accordingly, Throughput must be discounted for probability (or risk).</p>
<p>We must also acknowledge that the whole-of-life value of one sales transaction may be greater than the value of the initial transaction.</p>
<p>For this reason, Opportunity Throughput (TO) is equal to the risk-adjusted, net present value of the sales opportunity.</p>
<p align="center"><img alt="the goal" src="http://www.salesprocessengineering.net/wp-content/uploads/image/Formula1.gif" /></p>
<h3>Probability</h3>
<p>Traditionally, probability is estimated (subjectively) by salespeople. If the opportunity management process consists of one or more standardised strategies this is no longer necessary. All we have to do is select process milestones (stages) and determine the historical probability for opportunities at each stage.</p>
<p>The table below shows a typical set of stages with associated probabilities.</p>
<table cellspacing="0" cellpadding="0">
<tbody>
<tr>
<td>
<p><strong>Stage</strong></p>
</td>
<td>
<p align="center"><strong>%</strong></p>
</td>
</tr>
<tr>
<td valign="top">
<div align="left">
<table id="AutoNumber20" bordercolor="#111111" cellspacing="0" align="left" border="0">
<tbody>
<tr>
<td valign="top">1.</td>
<td valign="top">Best-practice briefing pending (first appointment)</td>
</tr>
</tbody>
</table></div>
</td>
<td valign="top">
<p align="center">8%</p>
</td>
</tr>
<tr>
<td valign="top">
<div align="left">
<table id="AutoNumber20" bordercolor="#111111" cellspacing="0" align="left" border="0">
<tbody>
<tr>
<td valign="top">2.</td>
<td valign="top">Executive briefing pending</td>
</tr>
</tbody>
</table></div>
</td>
<td valign="top">
<p align="center">23%</p>
</td>
</tr>
<tr>
<td valign="top">
<div align="left">
<table id="AutoNumber20" bordercolor="#111111" cellspacing="0" align="left" border="0">
<tbody>
<tr>
<td valign="top">3.</td>
<td valign="top">Proposal pending</td>
</tr>
</tbody>
</table></div>
</td>
<td valign="top">
<p align="center">38%</p>
</td>
</tr>
<tr>
<td valign="top">
<div align="left">
<table id="AutoNumber20" bordercolor="#111111" cellspacing="0" align="left" border="0">
<tbody>
<tr>
<td valign="top">4.</td>
<td valign="top">Proposal customisation meeting pending</td>
</tr>
</tbody>
</table></div>
</td>
<td valign="top">
<p align="center">67%</p>
</td>
</tr>
<tr>
<td valign="top">
<div align="left">
<table id="AutoNumber20" bordercolor="#111111" cellspacing="0" align="left" border="0">
<tbody>
<tr>
<td valign="top">5.</td>
<td valign="top">Instruction to proceed pending</td>
</tr>
</tbody>
</table></div>
</td>
<td valign="top">
<p align="center">98%</p>
</td>
</tr>
</tbody>
</table>
<p>&nbsp;</p>
<h3>Buffer size</h3>
<p>The opportunity buffer consists of all sales opportunities &mdash; where these opportunities are at various stages of the opportunity management process.</p>
<p>You could visualise the opportunity buffer as an inventory of pending appointments. If, however, multiple appointments are required to close each appointment, you would have to remember that each appointment is likely to be connected to one or more others.</p>
<p>We can estimate the minimum number of opportunities that are required to keep the salesperson fully utilised by multiplying his daily capacity by the average opportunity cycle time, and then dividing the result by the average number of appointments consumed by each opportunity (some opportunities will never progress to first appointment, while others will consume multiple appointments).</p>
<p>Because Murphy will strike from time to time, this buffer needs to contain protective capacity. Experimentation has lead us to the conclusion that protective capacity should be an additional 50% of the minimum capacity.</p>
<p>The following example relates to the five-stage opportunity management process referenced previously. (It should provide some indication of the volume of concurrent opportunities that can be processed by a single salesperson.)</p>
<table cellspacing="0" cellpadding="0">
<tbody>
<tr>
<td colspan="2">
<p align="center"><strong>Optimal buffer size</strong></p>
</td>
</tr>
<tr>
<td valign="top">
<p>CCR capacity (/day)</p>
</td>
<td valign="top">
<p align="right">5</p>
</td>
</tr>
<tr>
<td valign="top">
<p>Opportunity cycle time (days)</p>
</td>
<td valign="top">
<p align="right">42</p>
</td>
</tr>
<tr>
<td valign="top">
<p>Avg appointments/opportunity</p>
</td>
<td valign="top">
<p align="right">1.85</p>
</td>
</tr>
<tr>
<td valign="top">
<p>Opportunities required for 100% utilisation [5 x 42 / 1.85]</p>
</td>
<td valign="top">
<p align="right">114</p>
</td>
</tr>
<tr>
<td valign="top">
<p>Buffer size (opportunities) [114 x 1.5]</p>
</td>
<td valign="top">
<p align="right">170</p>
</td>
</tr>
</tbody>
</table>
<p>&nbsp;</p>
<h3>Programming appointments</h3>
<p>You&rsquo;ll recall that we wish to replace intuition with a more objective method for programming appointments.</p>
<p>We can do this by:</p>
<ol>
<li>Estimating the contribution that each sales opportunity will make if it is allocated to an appointment slot.</li>
<li>Indexing the opportunity buffer, based upon this probable contribution.</li>
</ol>
<p>We start by revisiting our stages and adding the following:</p>
<p>Appointments pending: This is an estimate of the number of additional appointments that will be required to win the opportunity (this number cannot be less than one).</p>
<p>Maximum days: Because opportunities atrophy over time, this figure determines the point at which we will apply an additional discount. (These numbers are cumulative.)</p>
<table cellspacing="0" cellpadding="0">
<tbody>
<tr>
<td>
<p><strong>Stage</strong></p>
</td>
<td>
<p align="center"><strong>Appts Pending</strong></p>
</td>
<td>
<p align="center"><strong>Max Days</strong></p>
</td>
</tr>
<tr>
<td valign="top">
<div align="left">
<table cellspacing="0" align="left" border="0">
<tbody>
<tr>
<td valign="top">1.</td>
<td valign="top">Best-practice briefing pending (first appointment)</td>
</tr>
</tbody>
</table></div>
</td>
<td valign="top">
<p align="center">3</p>
</td>
<td valign="top">
<p align="center">28</p>
</td>
</tr>
<tr>
<td valign="top">
<div align="left">
<table id="AutoNumber22" cellspacing="0" align="left" border="0">
<tbody>
<tr>
<td valign="top">2.</td>
<td valign="top">Executive briefing pending</td>
</tr>
</tbody>
</table></div>
</td>
<td valign="top">
<p align="center">2</p>
</td>
<td valign="top">
<p align="center">42</p>
</td>
</tr>
<tr>
<td valign="top">
<div align="left">
<table cellspacing="0" align="left" border="0">
<tbody>
<tr>
<td valign="top">3.</td>
<td valign="top">Proposal pending</td>
</tr>
</tbody>
</table></div>
</td>
<td valign="top">
<p align="center">1</p>
</td>
<td valign="top">
<p align="center">56</p>
</td>
</tr>
<tr>
<td valign="top">
<div align="left">
<table cellspacing="0" align="left" border="0">
<tbody>
<tr>
<td valign="top">4.</td>
<td valign="top">Proposal customisation meeting pending</td>
</tr>
</tbody>
</table></div>
</td>
<td valign="top">
<p align="center">1</p>
</td>
<td valign="top">
<p align="center">70</p>
</td>
</tr>
<tr>
<td valign="top">
<div align="left">
<table id="AutoNumber25" cellspacing="0" align="left" border="0">
<tbody>
<tr>
<td valign="top">5.</td>
<td valign="top">Instruction to proceed pending</td>
</tr>
</tbody>
</table></div>
</td>
<td valign="top">
<p align="center">1</p>
</td>
<td valign="top">
<p align="center">84</p>
</td>
</tr>
</tbody>
</table>
<p>&nbsp;</p>
<p>We estimate the relative value of each opportunity using the following formula:</p>
<p align="center"><img alt="the goal" src="http://www.salesprocessengineering.net/wp-content/uploads/image/Formula2.gif" /></p>
<p>Overdue days is calculated by subtracting the max days value that is associated with the current stage from actual days (the number of days the opportunity has been open thus far.) The result must be a whole number*.</p>
<p>The following table is an example of three opportunities indexed using this method.</p>
<p>Assuming the same geographic region, the sales coordinator will program these opportunities into the salesperson&rsquo;s diary in the order dictated by the index.</p>
<table cellspacing="0" cellpadding="0">
<tbody>
<tr>
<td>
<p align="center"><strong>T</strong></p>
</td>
<td>
<p align="center"><strong>Stage</strong></p>
</td>
<td>
<p align="center"><strong>%</strong></p>
</td>
<td>
<p align="center"><strong>TO</strong></p>
</td>
<td>
<p align="center"><strong>Pend Appts</strong></p>
</td>
<td>
<p align="center"><strong>O&rsquo;due Days</strong></p>
</td>
<td>
<p align="center"><strong>Relative Value</strong></p>
</td>
<td>
<p align="center"><strong>Index</strong></p>
</td>
</tr>
<tr>
<td valign="top">
<p align="right">$25,000</p>
</td>
<td valign="top">
<p align="center">2</p>
</td>
<td valign="top">
<p align="center">23%</p>
</td>
<td valign="top">
<p align="right">$5,750</p>
</td>
<td valign="top">
<p align="center">2</p>
</td>
<td valign="top">
<p align="center">0</p>
</td>
<td valign="top">
<p align="right">$2,875</p>
</td>
<td valign="top">
<p align="center">2</p>
</td>
</tr>
<tr>
<td valign="top">
<p align="right">$12,000</p>
</td>
<td valign="top">
<p align="center">4</p>
</td>
<td valign="top">
<p align="center">67%</p>
</td>
<td valign="top">
<p align="right">$8,040</p>
</td>
<td valign="top">
<p align="center">1</p>
</td>
<td valign="top">
<p align="center">0</p>
</td>
<td valign="top">
<p align="right">$8,040</p>
</td>
<td valign="top">
<p align="center">1</p>
</td>
</tr>
<tr>
<td valign="top">
<p align="right">$25,000</p>
</td>
<td valign="top">
<p align="center">1</p>
</td>
<td valign="top">
<p align="center">8%</p>
</td>
<td valign="top">
<p align="right">$2,000</p>
</td>
<td valign="top">
<p align="center">3</p>
</td>
<td valign="top">
<p align="center">5</p>
</td>
<td valign="top">
<p align="right">$111</p>
</td>
<td valign="top">
<p align="center">3</p>
</td>
</tr>
</tbody>
</table>
<p>&nbsp;</p>
<h3>Performance indicators</h3>
<p>We discussed earlier that the performance indicator for the sales process as a whole is Throughput per appointment slot available (T/ASA).</p>
<p>If we reflect on the contribution each team member must make to maximise T/ASA, it is easy to derive an objective and a performance indicator for each.</p>
<p align="center"><img alt="the goal" src="http://www.salesprocessengineering.net/wp-content/uploads/image/Resourcing3-2.gif" /></p>
<table cellspacing="0" cellpadding="0">
<tbody>
<tr>
<td>
<p><strong>Resource</strong></p>
</td>
<td>
<p><strong>Objective</strong></p>
</td>
<td>
<p><strong>KPI</strong></p>
</td>
</tr>
<tr>
<td valign="top">
<p>Salesperson</p>
</td>
<td valign="top">
<p>Maximise Throughput for appointments conducted</p>
</td>
<td valign="top">
<p>T/ASC*</p>
</td>
</tr>
<tr>
<td valign="top">
<p>Sales coordinator</p>
</td>
<td valign="top">
<p>Maintain salesperson at 100% utilisation</p>
</td>
<td valign="top">
<p>Utilisation<br />
            (% of optimal)</p>
</td>
</tr>
<tr>
<td valign="top">
<p>Promotional coordinator</p>
</td>
<td valign="top">
<p>Maintain opportunity buffer at optimal size</p>
</td>
<td valign="top">
<p>Buffer size<br />
            (% of optimal)</p>
</td>
</tr>
</tbody>
</table>
<p>&nbsp;</p>
<p>Each of these performance indicators should then be plotted on a run chart &mdash; providing each team member with a real-time, objective view of the contribution his activities are making to the goal of the system as a whole.*</p>
<p align="center"><img alt="the goal" src="http://www.salesprocessengineering.net/wp-content/uploads/image/runchart.gif" /></p>
<p>This objective approach allows us to dispense with targets, budgets, bonuses and commissions, performance reviews and management exhortations.</p>
<p>The sales process is now easy to manage and, consequently, easy to scale.</p>
<h4>The result</h4>
<p>The application of TOC to the sales process results in radical changes to process design, resourcing and management:</p>
<ol>
<li>Responsibility for all tasks other than the conduct of appointments is institutionalised.</li>
<li>Non-constrained resources are applied to the acquisition and management of relationships and, accordingly, to the generation of sales opportunities.</li>
<li>The opportunity-management process is standardised &mdash; and optimised, so as to maximise the return on the unit of constraint (appointment slots).</li>
<li>Sales process cycle-time is reduced &mdash; often resulting in an increase in conversion rates.</li>
<li>Salespeople require only product knowledge and communication skills (consequently, they are easier to recruit and retain).</li>
<li>Commissions and bonuses cease to be necessary and the staffing mix shifts in favour of (lower-paid) sales support staff.</li>
<li>Significant increases in Throughput can be expected for similar Operating Expenses and Investment.</li>
</ol>
]]></content:encoded>
			<wfw:commentRss>http://www.salesprocessengineering.net/2008/07/18/how-to-build-a-high-throughput-sales-process/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>When higher conversion equals lower sales</title>
		<link>http://www.salesprocessengineering.net/2008/07/07/when-higher-conversion-equals-lower-sales/</link>
		<comments>http://www.salesprocessengineering.net/2008/07/07/when-higher-conversion-equals-lower-sales/#comments</comments>
		<pubDate>Tue, 08 Jul 2008 06:21:29 +0000</pubDate>
		<dc:creator></dc:creator>
				<category><![CDATA[Measures and General Management]]></category>
		<category><![CDATA[Slaying Sacred Cows]]></category>
		<category><![CDATA[flawed logic]]></category>
		<category><![CDATA[measurement]]></category>
		<category><![CDATA[qualification]]></category>
		<category><![CDATA[sales]]></category>
		<category><![CDATA[throughput]]></category>

		<guid isPermaLink="false">http://www.salesprocessengineering.net/2008/07/07/when-higher-conversion-equals-lower-sales/</guid>
		<description><![CDATA[I&#8217;ve discussed in the past that an assumption that underpins the design and management of most sales processes is that conversion (rate) is the primary driver of sales. The Sales Process Engineering method recognises this assumption as erroneous. In most all sales processes, opportunity flow (volume) is the primary driver, not conversion. It&#8217;s quite easy [...]]]></description>
			<content:encoded><![CDATA[<p>I&#8217;ve discussed in the past that an assumption that underpins the design and management of most sales processes is that conversion (rate) is the primary driver of sales.</p>
<p>The Sales Process Engineering method recognises this assumption as erroneous.</p>
<p>In most all sales processes, opportunity flow (volume) is the primary driver, not conversion.</p>
<p>It&#8217;s quite easy to see why.</p>
<p>Imagine a typical salesperson who processes about 10 opportunities a month and assume that this salesperson wins 50% of those opportunities. Now, consider how much potential there is for this person to increase sales by improving conversion.</p>
<p>Perhaps, with significant effort, this person could increase conversion rates by a percentage point or two. Let&#8217;s be generous<br />
and assume 10 points. Now, this person is generating 6 sales a month.</p>
<p>Now, consider the potential to increase sales by improving opportunity flow. If this person divests of low-yielding activities<br />
and dedicates their time to business-development appointments they will easily process 10 times the volume of sales opportunities each month (yep, that&#8217;s 100).</p>
<p>Let&#8217;s assume conversion rates drop by half (to 25%). Obviously, this person is now generating 25 sales a month.</p>
<p>So, opportunity flow should have primacy over conversion. Or, to express the relationship in TOC terms, opportunity flow is the goal and conversion a necessary condition.</p>
<p>But the relationship between conversion and sales is even more complex than this.</p>
<p>The reality is that small increase in conversion is likely to actually come at the expense of a *huge* decrease in opportunity<br />
flow.</p>
<p>The traditional approach to conversion improvement is for the salesperson to assume responsibility for more and more activities. The salesperson schedules and conducts every appointment; prepares every document; designs the solution; walks the client&#8217;s job through production; supervises implementation; and even manages the account on an ongoing basis.</p>
<p>Obviously, as the salesperson assumes responsibility for an increasing activity load, more and more of their capacity becomes unavailable for business-development activities.</p>
<p>It&#8217;s not just that the activities themselves consume the salesperson&#8217;s capacity, the fact that the salesperson has to<br />
synchronise numerous disparate tasks across multiple opportunities adds a significant overhead (one of the evils of multitasking).</p>
<p>So the relationship between conversion and opportunity flow is non-linear. An incremental increase in conversion will result in a geometric decrease in opportunity flow.</p>
<p>All the more reason to shift your focus from maximising conversion to maximising opportunity flow.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.salesprocessengineering.net/2008/07/07/when-higher-conversion-equals-lower-sales/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Chris gets it!</title>
		<link>http://www.salesprocessengineering.net/2008/07/07/chris-gets-it/</link>
		<comments>http://www.salesprocessengineering.net/2008/07/07/chris-gets-it/#comments</comments>
		<pubDate>Tue, 08 Jul 2008 06:07:25 +0000</pubDate>
		<dc:creator></dc:creator>
				<category><![CDATA[Applying Sales Process Engineering]]></category>
		<category><![CDATA[Measures and General Management]]></category>
		<category><![CDATA[measurement]]></category>
		<category><![CDATA[sales]]></category>
		<category><![CDATA[sales process]]></category>
		<category><![CDATA[throughput]]></category>

		<guid isPermaLink="false">http://www.salesprocessengineering.net/2008/07/07/chris-gets-it/</guid>
		<description><![CDATA[I just had a call from a client who owns a make-to-order manufacturing firm (building materials) in New Zealand. Chris was agitated because he had just realised that, last week, across his sales team, 20 appointment slots had gone unfilled, due either to cancellations or a failure to schedule appointments. He had calculated that these [...]]]></description>
			<content:encoded><![CDATA[<p>I just had a call from a client who owns a make-to-order manufacturing firm (building materials) in New Zealand.</p>
<p>Chris was agitated because he had just realised that, last week, across his sales team, 20 appointment slots had gone unfilled, due either to cancellations or a failure to schedule appointments.</p>
<p>He had calculated that these empty slots had cost him (conservatively) $16,000.</p>
<p>Chris now wants to do &#8220;whatever it takes&#8221; to ensure that these (occasional)holes are plugged.</p>
<p>I&#8217;ve got to say that it&#8217;s so gratifying to hear an executive complain about lost Throughput. (Most are way too busy obsessing about ways to shave operating expenses.)</p>
<p>Tell me, were your salespeople fully loaded with business- development appointments last week? If they performed 20 or less each, have you calculated the opportunity cost of their under-utilisation?</p>
<p>I suspect the opportunity cost dwarfs whatever operating expenses you might need to incur to shift the constraint firmly to your sales team.</p>
<p><em>(Disclaimer: obviously, this comment doesn&#8217;t apply if you are deliberately maintaining production or NPD as your system constraint.)</em></p>
]]></content:encoded>
			<wfw:commentRss>http://www.salesprocessengineering.net/2008/07/07/chris-gets-it/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Why sales training can decrease conversion rates!</title>
		<link>http://www.salesprocessengineering.net/2008/07/06/why-sales-training-can-decrease-conversion-rates/</link>
		<comments>http://www.salesprocessengineering.net/2008/07/06/why-sales-training-can-decrease-conversion-rates/#comments</comments>
		<pubDate>Mon, 07 Jul 2008 06:58:15 +0000</pubDate>
		<dc:creator></dc:creator>
				<category><![CDATA[Slaying Sacred Cows]]></category>
		<category><![CDATA[constraint]]></category>
		<category><![CDATA[measurement]]></category>
		<category><![CDATA[qualification]]></category>
		<category><![CDATA[salespeople]]></category>
		<category><![CDATA[throughput]]></category>

		<guid isPermaLink="false">http://www.salesprocessengineering.net/2008/07/06/why-sales-training-can-decrease-conversion-rates/</guid>
		<description><![CDATA[Question: What&#8217;s the primary driver of conversion rate? Answer: In most cases, it&#8217;s not sales skill! The primary driver is most often what we call Opportunity Cycle Time: the time it takes to close an opportunity. What that means is that, if you want to improve conversion rates, you should look for a way to [...]]]></description>
			<content:encoded><![CDATA[<p>Question: What&#8217;s the primary driver of conversion rate? Answer: In most cases, it&#8217;s not sales skill! The primary driver is most often what we call Opportunity Cycle Time: the time it takes to close an opportunity. What that means is that, if you want to improve conversion rates, you should look for a way to reduce Opportunity Cycle Time *before* you consider sales training. Now the easiest way to reduce cycle time is to schedule salespeople&#8217;s appointments for them. (You can also reengineer the Opportunity Management process.) Left to their own devices, salespeople will always program low-contribution activities over high-contribution ones (they&#8217;ll program the processing of an inbound enquiry over a follow-up call to someone who has been sent a proposal). This is because humans naturally overvalue uncertainty (if this weren&#8217;t the case, none of us would gamble). So consider the effects of sales training. As well as equipping salespeople with negotiation skills, sales training encourages them to be more opportunistic. This exacerbates their inclination to miss-program activities and, as a consequence, increases average Opportunity Cycle Time!</p>
]]></content:encoded>
			<wfw:commentRss>http://www.salesprocessengineering.net/2008/07/06/why-sales-training-can-decrease-conversion-rates/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Gordon Ramsay and TOC</title>
		<link>http://www.salesprocessengineering.net/2008/07/02/gordon-ramsay-and-toc/</link>
		<comments>http://www.salesprocessengineering.net/2008/07/02/gordon-ramsay-and-toc/#comments</comments>
		<pubDate>Thu, 03 Jul 2008 06:40:56 +0000</pubDate>
		<dc:creator></dc:creator>
				<category><![CDATA[Applying Sales Process Engineering]]></category>
		<category><![CDATA[constraint]]></category>
		<category><![CDATA[sales]]></category>
		<category><![CDATA[sales process]]></category>
		<category><![CDATA[throughput]]></category>

		<guid isPermaLink="false">http://www.salesprocessengineering.net/2008/07/02/gordon-ramsay-and-toc/</guid>
		<description><![CDATA[I was impressed to see Gordon Ramsay explain TOC basics to a failing restaurateur in his new reality show &#8220;Ramsay&#8217;s Kitchen Nightmares&#8221; the other night. Ramsay is the gruff, Scottish, Michelin-star-winning, celebrity chef. His show tracks his attempts to knock poor-performing restaurants into shape with his unique mix of screamed expletives, gentle reasoning and some [...]]]></description>
			<content:encoded><![CDATA[<p>I was impressed to see Gordon Ramsay explain TOC basics to a failing restaurateur in his new reality show &#8220;Ramsay&#8217;s Kitchen Nightmares&#8221; the other night.</p>
<p>Ramsay is the gruff, Scottish, Michelin-star-winning, celebrity chef. His show tracks his attempts to knock poor-performing restaurants into shape with his unique mix of screamed expletives, gentle reasoning and some sound business principles.</p>
<p>The other night he asked a restaurateur to explain why, on the one hand, she was promoting a cheap burger on her blackboard, while on the other, her menu items were ridiculously overpriced.</p>
<p>She explained that, because she was loosing money, her accountant and banker had encouraged her to raise prices &#8212; which she did. The problem is that this reduced cashflow. So, to generate cash to pay wages, she had to offer discounted blackboard items!</p>
<p>Predictably, Ramsay instructed her to phone her accountant and advise him that he is an a*******. But what was more interesting was the solution he proposed.</p>
<p>Ramsay instructed her to re-price her menu, serve smaller meals and focus on selling three courses to diners, rather than one.</p>
<p>But here&#8217;s the good bit. Because the restaurant&#8217;s weeknights were quiet, he told her to switch her focus from selling food to selling tables. His solution was to sell each table for 10 pounds &#8212; a fixed menu &#8212; and then sell each table multiple times in the one night.</p>
<p>While Ramsay has probably never heard of TOC, he&#8217;s smart enough to know that tables are typically a restaurant&#8217;s constraint &#8212; and, consequently, that the key to maximising the profitability of a restaurant is to maximise Throughput per table.</p>
<p>If you&#8217;ve seen the show, you&#8217;ll know that Ramsay often fails to rescue the restaurants he takes on. In the case of this show, when he returned a few weeks after his initial stay, the restaurant was doing well &#8212; particularly weeknights. From memory, on the particularly weeknight that Ramsay visited the restaurant was so busy that it had turned it&#8217;s tables three times each! And the restaurateur reported that she was, at last, making money.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.salesprocessengineering.net/2008/07/02/gordon-ramsay-and-toc/feed/</wfw:commentRss>
		<slash:comments>3</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 18:41:54 -->
