<?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; measurement</title>
	<atom:link href="http://www.salesprocessengineering.net/tag/measurement/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>The Machine &gt; Part 1 &gt; Chapter 6: The end of commissions, bonuses and other artificial management stimulants</title>
		<link>http://www.salesprocessengineering.net/2011/04/27/the-machine-part-1-chapter-6-the-end-of-commissions-bonuses-and-other-artificial-management-stimulants/</link>
		<comments>http://www.salesprocessengineering.net/2011/04/27/the-machine-part-1-chapter-6-the-end-of-commissions-bonuses-and-other-artificial-management-stimulants/#comments</comments>
		<pubDate>Thu, 28 Apr 2011 00:03:50 +0000</pubDate>
		<dc:creator>Justin Roff-Marsh</dc:creator>
				<category><![CDATA[Measures and General Management]]></category>
		<category><![CDATA[Slaying Sacred Cows]]></category>
		<category><![CDATA[The Machine (book)]]></category>
		<category><![CDATA[commission]]></category>
		<category><![CDATA[flawed logic]]></category>
		<category><![CDATA[measurement]]></category>

		<guid isPermaLink="false">http://www.salesprocessengineering.net/2011/04/27/the-machine-part-1-chapter-6-the-end-of-commissions-bonuses-and-other-artificial-management-stimulants/</guid>
		<description><![CDATA[If it’s true that sacred cows make the best hamburgers, then we’re in for quite a feast! I’ve chosen to close Part One of this book with a frontal assault on the juiciest bovine of all: the unassailable belief that salespeople should be paid commissions. And while I’m at it, I’ll take aim at bonuses, [...]]]></description>
			<content:encoded><![CDATA[<p>If it’s true that <em>sacred cows make the best hamburgers,</em> then we’re in for quite a feast!</p>
<p>I’ve chosen to close Part One of this book with a frontal assault on the juiciest bovine of all: the unassailable belief that salespeople should be paid commissions. And while I’m at it, I’ll take aim at bonuses, targets and other <em>artificial management stimulants.</em></p>
<h3>A litmus test</h3>
<p>This discussion is important for two reasons.</p>
<p>First, commissions and their bedfellows will definitely handicap the performance of the reengineered sales environment I’ve gone to great lengths to describe.</p>
<p>Second, this discussion will force us to confront the significant implications of <em>Sales Process Engineering: </em>both locally and organization wide.</p>
<p>If you are brave enough to follow in the footsteps of our <em>quiet revolutionaries</em> it’s critical that you truly appreciate the <em>essence</em> of SPE. It’s not enough to believe that SPE will work; you must also understand – at the most fundamental level – <em>exactly</em> <em>why</em> it will work. (And if you don’t, it almost certainly won’t!)</p>
<p>So, I’m proposing that you use the (emotionally-charged) question of salespeople’s commissions as a kind of litmus test. If, by the end of this chapter, you are comfortable that there is no place for commissions in a reengineered sales environment, it’s safe for you to proceed.</p>
<p>If, however, this conclusion still does not sit comfortably with you, it makes more sense to treat this book as an exercise in creative thinking (and leave your sales function well alone).</p>
<h3>When commissions make sense</h3>
<p>At its most fundamental level, SPE involves the transitioning of the responsibility for sales from autonomous agents to a centrally-coordinated team.</p>
<p>When sales <em>actually is</em> performed by autonomous agents, it does makes sense to pay these agents on a commission basis (a percentage of the revenue they generate).</p>
<p>So, if we imagine a computer hardware manufacturer that sells desktop and notebook computers to consumers, via big-box retailers; it’s clear that these arms-length retailers should be paid on a commission basis.</p>
<p>And, if we think about this example, we can identify two conditions that accord well with commission-based pay:</p>
<ol>
<li>These retail agents sell from stock – meaning that there is no requirement for them to interact with the hardware manufacturer on a transaction-by-transaction basis (which certainly would not be the case in an <em>engineer-to-order</em> environment)</li>
<li>These retail agents are <em>truly</em> autonomous – they march to their own drumbeats (and they own the relationship with the ultimate customer)</li>
</ol>
<p>But what happens to the case for commission-based pay when these conditions are <em>not</em> in place?</p>
<p>As we discussed in Chapter 2, when we transition from a <em>make-to-stock</em> to an <em>engineer-to-order</em> environment, the case for autonomy becomes weaker. Increasingly, the performance of the organization as a whole becomes more a function of the quality of integration between sales and production.</p>
<p>And, because <em>autonomy</em> and <em>teamwork</em> are polar opposites, as the case for autonomy becomes weaker, we reach a point where we <em>have to</em> make a clean switch from one to the other (there’s simply no such thing as an autonomous team member!).</p>
<h4><strong>The wrong question</strong></h4>
<p>We now arrive at the critical question. We should not begin this discussion by asking: <em>does commission make sense?</em> Rather, we should ask: <em>should we sell via autonomous agents or via a centrally-coordinated team?</em></p>
<p>Once we answer this question, our position on commissions becomes obvious.</p>
<h3>Commissions: the case against</h3>
<p>In order to understand why, let’s briefly revisit the history of manufacturing.</p>
<p>There was a time (before the industrial revolution) when almost all labor was paid on a piece-rate. Piece-rate pay is the manufacturing equivalent of commission. Rather than being paid in units of time, a piece-rate worker is paid in units of output. (A sewer, for example, might receive 20c for each garment processed.)</p>
<p>Today, however, piece-rate pay is almost extinct. (And, I suspect by now, you have a good idea why!)</p>
<p>What happened is that management discovered that, as the complexity of the environment increased, there was a critical threshold beyond which scheduling decisions had to be made centrally.</p>
<p>Of course, beyond this threshold, piece-rate pay had to be eliminated because it drove workers to work as fast as possible and not to subordinate to the schedule. (Remember, because of the combination of <em>dependency </em>and <em>variability</em> you never maximize the output of a system by maximizing the rate-of-work of each system resource.)</p>
<p>Commissions (or any kind of performance pay) are inappropriate in the reengineered sales environments described in this book for exactly the same reason that piece-rate pay is now inappropriate in manufacturing environments.</p>
<p>And this conclusion does not just apply to the sales function in isolation. As we discussed in Chapter 4, in many organizations it is not healthy for sales to be the organizational constraint. So, in these cases, irrespective of the structure of the sales function, the organization as a whole will perform better when sales is <em>not</em> operating at 100% utilization.</p>
<p><span id="more-596"></span></p>
<p>I wish this could be my last word on that subject. However, there’s a number of persistent objections to my position that we must first put to bed:</p>
<ol>
<li>Ours is a <em>mixed environment: </em>salespeople are not fully autonomous – meaning that a mix of salary and commission is justified</li>
<li>Even if we don’t need the compensation plan to determine salespeople’s rate of work, we still need performance pay to maximize salespeople’s <em>quality</em> of work (in other words, without commissions, what would motivate salespeople to actually sell?)</li>
<li>Commissions enable us to mitigate against the uncertain nature of salespeople’s performance and keep costs under control</li>
<li>The theory may make sense, but good salespeople will simply not be prepared to work in an environment without commissions</li>
</ol>
<h4><strong>The fallacy of a mixed environment</strong></h4>
<p>I’ve heard many executives argue that it’s beneficial for their salespeople to be <em>partly autonomous. </em>But I’ve never heard anyone argue that it’s beneficial for salespeople to be <em>partly team members</em>.</p>
<p>Perhaps it’s because the latter phrasing exposes the folly of this position!</p>
<p>I’ve already stressed that it is impossible for salespeople to be team members and autonomous agents at the same time. However, an astute reader might argue that this is possible in theory (if not in <abbr style="border-bottom: navy 1px dotted;" title="Yes, I know that to propose a dichotomy between theory and practice is to make a mockery of the former!">practice</abbr>).</p>
<p>Your salespeople <em>can</em> be capable team members <em>and</em> operate autonomously if (and only if) the rest of the organization has the capacity to subordinate to individual salespeople.</p>
<p>At first glance, this condition may not appear to be particularly onerous. However, when we consider the enormous variability in salespeople’s output, we recognize that effective subordination would require a huge amount of redundancy in customer service, engineering and production. (Remember, we’re considering true <em>sales</em> here, not repeat <em>transactions</em>.)</p>
<p>The fact that this is commercially unrealistic in most organization tends not to stop management from pursuing a <em>mixed</em> sales environment. And, the consequences are as unpleasant as they are predictable:</p>
<ol>
<li>Management encourages salespeople to operate autonomously</li>
<li>Salespeople proceed from the assumption that <em>more sales is always better</em> (the tacit assumption is that the rest of the organization can keep up)</li>
<li>On average, the sales team as a whole sells less than the organization has the capacity to produce</li>
<li>However, because new accounts are won infrequently (after all, salespeople spend the greater majority of their time processing transactions), the load on the rest of the organization is irregular</li>
<li>On the (not infrequent) occasions that customer service, engineering or production does not have the capacity to honor commitments made by salespeople, on-time performance tends to be compromised (although, the commitments that have been made to new accounts are often met, at the expense of existing ones)</li>
<li>Periodically, management attempts to improve the financial performance of the organization with additional incentives and special promotions</li>
<li>These incentives tend to increase the lumpiness of the deal flow – meaning that, over time, peak sales increase, at the expense of average sales</li>
</ol>
<p>The bottom-line is that contradictions cannot persist indefinitely. Your salespeople cannot be both autonomous agents <em>and</em> team members. They cannot be responsible only for sales outcomes <em>and</em> simultaneously be expected to attend sales meetings and maintain the organization’s CRM. And customers cannot belong to both salespeople <em>and</em> to your organization.</p>
<h4><strong>Commissions and the <em>quality</em> of work</strong></h4>
<p><em>If salespeople don’t have the opportunity to earn commission, then why would they sell?</em></p>
<p>I wish I had a dollar for every time I’ve been asked this question by an incredulous executive. You would think the onus should be on the defender of performance pay to present an argument.</p>
<p>After all, receptionists answer the phone when it rings, in spite of the fact that they receive no incremental pay. Your financial controller does a good job of paying bills on time, in spite of the fact that they receive no rebate on each check signed. And even senior executives perform important tasks, absent special incentives (I’m assuming that no one is paying you to read this book!).</p>
<p>Why should salespeople differ from almost every other worker on the planet?</p>
<p>The answer to the question four paragraphs above is simple: absent the opportunity to earn a commission, salespeople will still sell <em>because they are salespeople. </em>(Just as receptionists answer the phone <em>because they are receptionists</em>.)</p>
<p>I often wonder if those executives who ask that question are really enquiring into the motivation of their team members or if they are providing an (unsolicited) insight into their own pathology!</p>
<p>In <em>Drive</em>, his excellent best-seller, Daniel Pink presents a powerful case against performance pay. His conclusion – backed-up by many experiments from the social sciences – is that external rewards retard the performance of knowledge workers and have a positive effect <em>only</em> in situations where workers are performing mindless, repetitive tasks.</p>
<p>In other words, if your team members are responsible for activities any more complex than licking stamps, <em>the work itself is their reward</em>.</p>
<p>Interestingly, Pink’s conclusion points to an interesting defense of performance pay in the traditional sales environment. Consider these two points:</p>
<ol>
<li>In most environments the <em>volume</em> of sales appointments has a far greater influence on sales output than the qualitative performance of the salesperson</li>
<li>In almost all environments, salespeople generate their own appointments as a result of mindless and repetitive <em>prospecting </em>activities (internet research, cold calling, etc)</li>
</ol>
<p>With these points in mind, commissions may be defensible in <em>traditional</em> sales environments, not because they motivate salespeople to sell, but because they motivate them to prospect!</p>
<p>Of course, in our case, this argument is moot because we are definitely going to free salespeople of the requirement to generate their own sales meetings.</p>
<h4><strong>Commissions as a hedge against non-performance</strong></h4>
<p>The obvious problem with the argument that performance pay provides management with a hedge against the costs associated with salespeople’s non-performance is that the same argument could be applied to everyone in the organization.</p>
<p>But, then sales <em>is</em> a special case for a couple of reasons:</p>
<ol>
<li>The performance of salespeople is highly variable</li>
<li>It is easy to isolate the contribution that a salesperson makes (this would not be so easy in the case of a line worker)</li>
</ol>
<p>As we’ll discuss shortly, SPE inverts these two reasons:</p>
<ol>
<li>The output of the sales function ceases to be highly variable</li>
<li>While it’s easy to measure the capability of a salesperson, it is difficult (if not impossible) to isolate the contribution that person’s activity make to the organization as a whole</li>
</ol>
<p>First, however, let’s consider the wider (and more terrifying) implications of performance pay.</p>
<p><strong>Management abdicates</strong></p>
<p>We’ve discussed earlier that you cannot manage an autonomous agent (these two concepts are antagonistic). Performance pay makes this contradiction explicit! In other words, when a significant component of a salesperson’s pay is performance based, management has formally abdicated its responsibility for sales.</p>
<p>In so doing, management has telegraphed to salespeople that <em>selling is optional! </em>It is now up to individual salespeople whether or not they generate sales – and in what quantity.</p>
<p style="margin-left: 30px;">If a salesperson is <em>capable</em> of selling, the real cost of their non-performance is <em>not </em>their salary, it’s the profits that the organization does not earn when production is sitting idle!</p>
<p style="margin-left: 30px;">If a salesperson is <em>not</em> capable of selling, the real cost of their non-performance is <em>still</em> not their salary, it’s the sales opportunities that are lost that could have been won if they were attended to by a more capable individual.</p>
<p><strong>Variability diminished</strong></p>
<p>If sales appointments are the primary driver of sales (and it’s rare that they are not), we can significantly reduce the variability of sales by:</p>
<ol>
<li>Fixing the volume of sales appointments (the same number of appointments, week after week)</li>
<li>Increasing the volume of appointments (as the appointment volume increases, the variability of the entire sales function <abbr style="border-bottom: navy 1px dotted;" title="Google: &quot;regression to the mean&quot;">reduces</abbr>)</li>
</ol>
<p>Of course, our standard model does this by ensuring that salespeople do <em>nothing</em> other than sales appointments and by ensuring that each salesperson performs ten-times the volume of appointments they would perform in a typical sales environment.</p>
<p><strong>Capability</strong></p>
<p>Many of our silent revolutionaries report an increase in salespeople’s capability. There are three contributing factors here:</p>
<ol>
<li>Predictably, when organizations reduce the size of their sales teams, they retain their more capable salespeople</li>
<li>When salespeople do nothing other than sell – four appointments a day, five days a week – they get good at it (or they rapidly conclude that sales is not the right career for them)</li>
<li>With control over salespeople – and with accurate and current data – sales management finds it easy to institute a process of ongoing improvement</li>
</ol>
<h4><strong>Salespeople’s position on commissions</strong></h4>
<p>If there’s one thing I’ve learned in the last 10 years or so, it’s that sales managers are uniformly terrible at predicting their salespeople’s reaction to our standard model.</p>
<p>Almost without exception, sales managers predict outrage from their team members – perhaps even a mass exodus of talent! And the one component of our model sales managers predict will be the most offensive is the elimination of commissions.</p>
<p>In reality, salespeople’s reaction to this proposition tends to be shocking for exactly the opposite reason. It’s shocking how comfortable salespeople are to give up both their autonomy and their variable compensation plan!</p>
<p>The reason salespeople tend to be so compliant is very simple.</p>
<p>Salespeople (contrary to popular opinion) do not live in a parallel universe. They are a part of the same dysfunctional reality that is causing the rest of the organization (including management) so much pain.</p>
<p>Salespeople may have different theories about the source of their particular set of issues – and they may propose different initiatives as a remedy to these issues – but, when presented with the evidence, salespeople recognize (often faster than management) that a significant number of sales problems, production problems and management problems can be tracked back to the same root cause (their autonomous mode of operation).</p>
<p>And make no mistake; salespeople have more than their fair share of complaints:</p>
<ol>
<li>They hate the volume of clerical and customer-service work that prevents them from engaging meaningfully with potential and existing customers</li>
<li>They don’t enjoy spending their evenings in hotels entering data in the CRM, generating expense reports and writing proposals</li>
<li>The resent the continual conflict over the allocation of commissions (particularly when accounts span multiple territories)</li>
<li>They hate having to advise clients that their promises will not be met – and they resent the fact that they have to live with the continuous uncertainty over production performance</li>
<li>They don’t enjoy the underlying – and constant – conflict in their relationships with production, customer service engineering, management and even finance</li>
</ol>
<p>It may be true that salespeople are in love with the notion of <em>the salesperson as a lone crusader,</em> but salespeople are also realists. They quickly recognize that, on balance, the proposed environment will be infinitely more rewarding to work in.</p>
<p style="margin-left: 30px;">Sure, they sacrifice their autonomy but, so what? They each get a dedicated executive assistant (sales coordinator) who will free them to do nothing but sell.</p>
<p style="margin-left: 30px;">And sure, they have to transition from commission to a salary but, what of it? Salespeople understand that the dynamics of the environment in which they operate rob them of the financial upside they signed-on for. And, the truth be known, salespeople have never been entirely comfortable with the notion that they are innately lazy: prepared only to do the right thing on the promise of an incremental financial inducement.</p>
<h3>The new compensation plan</h3>
<p>So, it’s out with commissions and in with a new compensation plan.</p>
<p>But there’s not much to the new plan. The idea is simple: <em>we pay people what they are worth</em> (perhaps a little more).</p>
<p>And that’s it!</p>
<p>In practice, you should pay salespeople enough to ensure that compensation is no longer a regular topic of conversation – and then <em>insist</em> that they perform the activities required for the organization to achieve its objectives.</p>
<p>So here, from management’s perspective, is the fundamental difference between the two compensation plans:</p>
<p style="margin-left: 30px;">With performance pay, we make optimal performance <em>optional</em> – and then we attempt to exert control through a compensation plan that underlines salespeople’s autonomy with every pay check!</p>
<p style="margin-left: 30px;">With salaries, we take the discussion of money off the table. Salespeople willingly subordinate to a central schedule. And they perform necessary activities because they are asked to (and, because those activities are congruent with both salespeople’s job descriptions and the reasonable interests of the organization).</p>
<p>This new plan, then, is not even new: it’s exactly the same plan we use to compensate everyone else in the organization!</p>
<p>And when it comes to calculating salespeople’s salaries, there are no surprises here either. As with all employees, there are two considerations:</p>
<ol>
<li>Replacement cost (how much would you have to pay for another person with a comparable set of capabilities?)</li>
<li>Asking price (how much will you have to pay the current candidate to ensure that the compensation plan is no longer a regular topic of conversation?)</li>
</ol>
<p>It should go without saying that it would be foolish to propose that salespeople (or any team members, for that matter) take a cut in pay when you transition to this new model.</p>
<p>Most of our silent revolutionaries shift their salespeople to a salary that is equal to, or slightly greater than, their average total earnings (typically judged over a three-year period).</p>
<p>If you think about it, both parties are getting a terrific deal here.</p>
<ol>
<li>Salespeople are receiving a not-insignificant pay rise. Obviously <em>the potential</em> to earn a figure is worth nowhere as much as the same figure, <em>guaranteed</em>.</li>
<li>Management is increasing the volume of <em>effective</em> work performed by each salesperson by <em>ten times</em>. To achieve the same increase in a typical sales environment, management would have to add nine more salespeople for every one they currently employ! In the new model, the cost is limited to an incremental increase in the salesperson’s compensation and the cost of a sales coordinator.</li>
</ol>
<h3>The other artificial management stimulants</h3>
<p>This debate about commissions is like Hydra (the many-headed monster). You successfully lop-off one head and another appears.</p>
<p>I fear that, even if I’ve done a reasonable job of convincing you that there’s no place for commissions in the reengineered environment, your very next question might be: <em>but, what about bonuses</em>.</p>
<p>My observation is that bonus plans have a couple of problems:</p>
<ol>
<li>Because the bonus is remote from the positive behaviors that drive the desired outcome, the first installment of a bonus is a pleasant surprise and subsequent installments are viewed as entitlements</li>
<li>Bonuses suggest to team members that they are responsible for outcomes when, in fact, managers should own this responsibility – accordingly, they tend to dis-empower managers</li>
</ol>
<p>It is certainly true that some degree of variability is required where compensation is concerned. However, my position is that standard salaries provide the necessary flexibility. As your team members become more capable, their market value increases, meaning that you are obliged to grant them pay rises when (or ideally before) they <abbr style="border-bottom: navy 1px dotted;" title=" It’s worth bearing in mind that labor is a particularly efficient market. Most employees know exactly what their fellow team members are earning as well as what they could earn at an alternative employer.">request</abbr> them.</p>
<p>I suggest that there is absolutely nothing wrong with the traditional contract between employers and employees. Employees want to be able to perform rewarding work in a secure environment. If they were really seeking uncertainty and boundless riches they would not have signed-on to be employees in the first place.</p>
<p>The other stimulants (targets and quotas) are problematic for the same reasons as commissions and bonuses. They tend to suggest that team members <em>own </em>outcomes.</p>
<p>In a team environment, the <em>team</em> cannot own the responsibility for anything! There is no collective consciousness – only a group of individuals. It is critical, therefore, that the manager owns the responsibility for the desired outcome and that team members own the responsibility only for the activities assigned to them.</p>
<p>Here, a military example is illuminating. Imagine, rather than allocating discrete responsibilities to each of his units a commander were simply to assemble all his troops and exhort them to <em>take Berlin!</em></p>
<h3>Reinventing management</h3>
<p>On the subject of management, it’s important to recognize that the transition to a reengineered sales environment is extremely difficult for sales managers.</p>
<p>As a result of this transition, sales managers find themselves in a position where <em>down is up</em> and <em>up is down</em>. If sales managers were to refer to a list they had compiled before the transition of <em>everything they know for sure about sales</em>, almost every statement on that list will now be false.</p>
<p>Consequently, it is not sufficient to reengineer the general sales environment. You must also rebuild from scratch the sales manager’s method of operation.</p>
<p align="center">* * * *</p>
<p>You now have a sound understanding of the theory that underpins Sales Process Engineering. Part Two of this book will show you how to convert all this theory into practice.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.salesprocessengineering.net/2011/04/27/the-machine-part-1-chapter-6-the-end-of-commissions-bonuses-and-other-artificial-management-stimulants/feed/</wfw:commentRss>
		<slash:comments>8</slash:comments>
		</item>
		<item>
		<title>The evil of time-and-material billing</title>
		<link>http://www.salesprocessengineering.net/2010/07/16/the-evil-of-time-and-material-billing/</link>
		<comments>http://www.salesprocessengineering.net/2010/07/16/the-evil-of-time-and-material-billing/#comments</comments>
		<pubDate>Fri, 16 Jul 2010 14:01:21 +0000</pubDate>
		<dc:creator>Justin Roff-Marsh</dc:creator>
				<category><![CDATA[Measures and General Management]]></category>
		<category><![CDATA[measurement]]></category>
		<category><![CDATA[process improvement]]></category>

		<guid isPermaLink="false">http://www.salesprocessengineering.net/2010/07/16/the-evil-of-time-and-material-billing/</guid>
		<description><![CDATA[Okay, perhaps evil is a bit of an exaggeration, but whenever I encounter an environment where time is tracked and billed, I see tremendous inefficiencies and value-destruction. Let’s consider why. Imagine you have something to sell – a widget, say. Tell me, for how much should you sell it? The answer to that question is [...]]]></description>
			<content:encoded><![CDATA[<p>Okay, perhaps <em>evil </em>is a bit of an exaggeration, but whenever I encounter an environment where time is tracked and billed, I see tremendous inefficiencies and value-destruction.</p>
<p>Let’s consider why.</p>
<p>Imagine you have something to sell – a widget, say. Tell me, for how much should you sell it?</p>
<p>The answer to that question is more obvious than you think. To calculate the optimal sale price you <em>don’t </em>need to know: </p>
<ol>
<li>Raw material cost </li>
<li>Labor hours </li>
<li>Overhead allocation ratios </li>
</ol>
<p>You don’t need to know any of that because the answer is: <em>you should sell that widget for as much as you can get!</em></p>
<p>That’s right, the optimal sale price is not determined by internal factors, it’s determined solely by what the market is prepared to bear. You cannot – let me say it again, CANNOT – <em>calculate</em> the price of a product.</p>
<p>All you can do it estimate it. And you must recognize that, in most situations (certainly in those environments where we’re most likely to see T&amp;M billing) it’s simply <em>impossible </em>to estimate the the price with a high degree of accuracy.</p>
<p>The primary assumption behind time-and-material billing (T&amp;M) is that you can calculate the price of something by simply counting the number of minutes required to produce it.</p>
<p>But you can’t. Effort does not equal value. In many cases, <em>it doesn’t even approximate it!</em></p>
<p>One of the problems with time is that it’s inherently measurable. Because it can be counted in intervals as small as a minute, we’re lulled into the false impression that we are <em>calculating </em>(as opposed to <em>estimating</em>) value.</p>
<h3>The alternative</h3>
<p>How then should we estimate value? And how should we track productivity?</p>
<p>If we use time to estimate, it’s important to recognize that we’re using time as a proxy (a yardstick) for value.&#160; Time <em>does not </em>equal value.</p>
<p>My advice, where time is concerned, is not to estimate time in increments any smaller than half a day. In other words, do not ask, <em>how many hours will this job take?, </em>ask <em>how many half days?</em> </p>
<p>Where short-duration tasks are concerned, my preference is to ignore them altogether. Just factor them into the multiplier you are using for half-day slots!</p>
<p>I’d rather, however, that you find some other proxy for value. We’re working with a bookkeeping firm currently. When I challenged them to identify a better proxy for value than time they came up with a great one – <em>transactions </em>(debits and credits). It’s obvious that the volume of transactions processed is a greater determinate of client value than time consumed.</p>
<p>And how do we track productivity? Well, we start by burning timesheets!</p>
<p>You DO NOT make money out of expending effort. You make money out of delivering value. And the connection (in most cases) between these two factors is very tenuous.</p>
<p>Timesheets encourage team members to be busy. This drives multitasking, and the hogging of work that could otherwise be passed-off to lower-paid people. Both destroy value. Furthermore the maintenance of time-tracking systems, consumes enormous resources and the completion of timesheets insults your team members at 10-minute intervals.</p>
<p>You need to recognize that individual jobs (or projects) do not make you money. Your <em>portfolio </em>of work makes you money. Once you realize this, you can focus on managing the portfolio, rather than the jobs.</p>
<p>You don’t make money by keeping your team busy. You make money by delivering jobs. And the two are NOT the same thing. People work best in fits and starts. And team work necessitates <em>relay-racer </em>behavior (person B hovers, waiting for person A to finish his work – and then sprints to hand-off the job to person C). </p>
<p>You need to mobilize your team to <em>get jobs out</em>. Think of the pit crew in a Formula 1 team. Timesheets are not conducive to this environment.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.salesprocessengineering.net/2010/07/16/the-evil-of-time-and-material-billing/feed/</wfw:commentRss>
		<slash:comments>14</slash:comments>
		</item>
		<item>
		<title>End-of-the-month syndrome and three fallacious assumptions</title>
		<link>http://www.salesprocessengineering.net/2010/06/06/end-of-the-month-syndrome-and-three-fallacious-assumptions/</link>
		<comments>http://www.salesprocessengineering.net/2010/06/06/end-of-the-month-syndrome-and-three-fallacious-assumptions/#comments</comments>
		<pubDate>Sun, 06 Jun 2010 13:55:41 +0000</pubDate>
		<dc:creator>Justin Roff-Marsh</dc:creator>
				<category><![CDATA[Measures and General Management]]></category>
		<category><![CDATA[Slaying Sacred Cows]]></category>
		<category><![CDATA[commission]]></category>
		<category><![CDATA[measurement]]></category>
		<category><![CDATA[performance pay]]></category>

		<guid isPermaLink="false">http://www.salesprocessengineering.net/?p=390</guid>
		<description><![CDATA[Alejandro C&#233;spedes wrote to me the other day with the following question: Hi Justin Just wanted to ask if you&#8217;ve designed a way of managing the sales budget of a company.&#160; In other words, how to review if the salespeople are meeting the budget or not.&#160; Most companies are affected by the end-of-the-month syndrome, and [...]]]></description>
			<content:encoded><![CDATA[<p>Alejandro C&eacute;spedes wrote to me the other day with the following question:</p>
<p style="margin-left: 30px">Hi Justin</p>
<p style="margin-left: 30px">Just wanted to ask if you&#8217;ve designed a way of managing the sales budget of a company.&nbsp; In other words, how to review if the salespeople are meeting the budget or not.&nbsp; Most companies are affected by the end-of-the-month syndrome, and at the same time, salespeople &ndash; once they meet that month&rsquo;s budget &ndash; are not interested in selling more.&nbsp; They&#8217;d rather stay still and avoid cannibalizing next month&rsquo;s sales.</p>
<p style="margin-left: 30px">Thanks <br />
Alejandro</p>
<p>&nbsp;Here&rsquo;s my response:</p>
<p style="margin-left: 30px">Alejandro</p>
<p style="margin-left: 30px">Good to hear from you!</p>
<p style="margin-left: 30px">Here are the two steps we take to eliminate these problems:</p>
<p style="margin-left: 30px"><strong>Eliminate monthly budgets</strong> &ndash; in favor of a T/cu type measure (Throughput per appointment-slot-consumed).</p>
<p style="margin-left: 30px"><strong>Eliminate commissions</strong>. Pay people what they are worth and make performance compulsory.</p>
<p style="margin-left: 30px">Justin</p>
<p>Alejandro&rsquo;s question was a reminder of just how dysfunctional most sales functions really are. His email set me thinking: why have managers (us) historically designed the sales environment this way.&nbsp; (Presumably, it&rsquo;s not because we&rsquo;re daft, or ill-intentioned.)&nbsp; Among the assumptions that underpin the design of the sales function, there must be some that are false &hellip; what are they?</p>
<h3>Three fallacious assumptions</h3>
<p>Here are some assumptions that I suspect will fail to emerge unscathed from an exposure to reality.&nbsp; Feel free to critique my selection, or suggest your own.</p>
<p><strong>Salespeople should be responsible for sales</strong>. Really? In how many organizations do salespeople <em>actually </em>have significant control over sales? What percentage of <em>your </em>transactions are the result of your salespeople:</p>
<ol>
<li>Originating <em>their own </em>opportunities (as opposed to responding to an inbound enquiry)?</li>
<li>Prosecuting these opportunities <em>single handed, </em>without assistance from engineering, estimating or management?</li>
</ol>
<p>If salespeople aren&rsquo;t responsible for generating the greater majority of sales (all by themselves), wouldn&rsquo;t it make more sense to hold them responsible for just the activities that they actually do perform?</p>
<p>Of course, in our model, we have salespeople performing <em>only </em>business-development meetings &ndash; nothing else.&nbsp; (Marketing originates opportunities, project leaders design solutions, etc). This means that they are accountable for <em>only </em>what they do in these meetings.&nbsp; &ldquo;Sales&rdquo; is management&rsquo;s responsibility.&nbsp; Just like &ldquo;production&rdquo; is the responsibility of your production manager &ndash; not a lathe operator or a claims processor.</p>
<p><strong><em>Monthly </em>is a sensible measurement frequency for sales</strong>. It&rsquo;s true that we calculate our profitability monthly. But does it follow that all internal processes should also be measured just once every 30 days.&nbsp; Consider your on-time-delivery performance, for example: should you stop and calculate this just once a month? Of course not. It should be calculated for <em>every </em>delivery.</p>
<p>We calculate profitability monthly because profitability is the consequence of a number of events that occur at different frequencies (and out of synchronization with one another). A more frequent calculation would probably generate <em>less </em>information, not more.</p>
<p>If the responsibility of the salesperson is to maximize the velocity of sales opportunities (and, yes, it should be) &ndash; and, if the salesperson&rsquo;s effort is expended in discrete packets called <em>appointments &ndash;</em><em> </em>why wouldn&rsquo;t we calculate the progress of <em>each </em>opportunity, relative to <em>each </em>appointment?</p>
<p>As with on-time-delivery performance, you may choose to view the resulting number in the form of a rolling average, but that doesn&rsquo;t alter the fact that the relevant time-horizon for the activity in question is an <em>appointment slot</em>, not <em>a month.</em></p>
<p><strong>Commissions drive positive behaviors</strong>.&nbsp; I had lunch with a director of a large (publicly listed) technology company in Sydney the other day. After hearing my position on salespeople and commissions, he asked about the negative consequences of eliminating commissions (replacing them with salaries).</p>
<p>I answered his question &ndash; as I usually do &ndash; with my own question. I asked him if he could first detail the positive behaviors, exhibited by salespeople, that he would be comfortable to attribute to the existing commission plan.</p>
<p>As usual, this question (an innocent one, I&rsquo;m sure you&rsquo;ll agree!) was met with a silence you could cut with a knife. He admitted that there were no positive behaviors &ndash; <em>only </em>negative ones! And he concluded, of his own volition, that it was probably more appropriate to try and find a justification for the <em>existence </em>of the commission plan than it was to look for a reason to <em>not </em>eliminate it.</p>
<p>As I&rsquo;ve suggested before, if sales are important for your firm, I suggest that you identify the critical behaviors that contribute to sales, and then make them compulsory (commissions signal to salespeople that these behaviors are optional).</p>
<p>Please comment.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.salesprocessengineering.net/2010/06/06/end-of-the-month-syndrome-and-three-fallacious-assumptions/feed/</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
		<item>
		<title>Customer surveys: data, yes; intelligence, no</title>
		<link>http://www.salesprocessengineering.net/2010/04/15/customer-surveys-data-yes-intelligence-no/</link>
		<comments>http://www.salesprocessengineering.net/2010/04/15/customer-surveys-data-yes-intelligence-no/#comments</comments>
		<pubDate>Thu, 15 Apr 2010 10:13:29 +0000</pubDate>
		<dc:creator>Justin Roff-Marsh</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[strategy]]></category>

		<guid isPermaLink="false">http://www.salesprocessengineering.net/2010/04/15/customer-surveys-data-yes-intelligence-no/</guid>
		<description><![CDATA[Late last night I was in conference with a potential client in South Africa (I’m in Australia, right now). Towards the end of our conversation, he asked if I thought much market intelligence could be gleaned from customer surveys. I answered (almost instinctively), data, yes; but, intelligence, no. When pressured for a more coherent answer, [...]]]></description>
			<content:encoded><![CDATA[<p>Late last night I was in conference with a potential client in South Africa (I’m in Australia, right now).</p>
<p>Towards the end of our conversation, he asked if I thought much market intelligence could be gleaned from customer surveys.</p>
<p>I answered (almost instinctively), <em>data, yes; but, intelligence, no</em>.</p>
<p>When pressured for a more coherent answer, I explained that I had never seen customer survey responses that provide any market intelligence. Never. Never. Never!</p>
<p>My position is that, to qualify as <em>intelligence, </em>survey results must be:</p>
<ol>
<li>Unexpected (if you know the answer already, why ask the question?)</li>
<li>Actionable (if data doesn’t cause you to do something differently then where’s the benefit?)</li>
</ol>
<p>Think about the survey results you’ve seen.&#160; How often have you been surprised?&#160; And how often have you been motivated to take some specific action?</p>
<p>Now, of course, I’m not advocating ignorance. Market intelligence is critical. You shouldn’t try to survive without it. It’s just that surveys are a pretty poor way of generating intelligence.</p>
<p>Here’s the thing …</p>
<p>In your business, <em>you bank behavior, not attitudes</em>.</p>
<p>My advice then, is stop measuring attitudes and, instead, measure behavior. Run controlled experiments. Change offers, change headlines, change opportunity-management workflows (not all at once, of course) and measure the impact of changes on, enquiries, conversions and, ultimately, sales.</p>
<p>Now, those who make their living from surveys will argue that attitude is an antecedent to behavior. I’m sure that in most cases it is. And in some, it definitely isn’t (how many smokers genuinely believe that their’s is an intelligent choice?)</p>
<p>But even if this claim is true, this position contains another assumption: that surveys actually measure attitudes. Do they?</p>
<p>Before you answer that question, consider another: which do you think is the more accurate predictor of a client’s future behavior:</p>
<ol>
<li>Their current attitude</li>
<li>Their prior behavior</li>
</ol>
<p>Tell me if you disagree but, to my mind, it’s a no contest! </p>
<p>And behavior is much sexier than attitude for another reason too: it’s inherently <em>measureable </em>(in a much more objective sense than the surveyor&#8217;s <em>1-5 scale</em>).</p>
<p>If you value market intelligence, can the surveys. Objective management is a philosophy, not a once-a-year event!</p>
]]></content:encoded>
			<wfw:commentRss>http://www.salesprocessengineering.net/2010/04/15/customer-surveys-data-yes-intelligence-no/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>Why better planning equals poorer execution</title>
		<link>http://www.salesprocessengineering.net/2010/04/05/why-better-planning-equals-worse-execution/</link>
		<comments>http://www.salesprocessengineering.net/2010/04/05/why-better-planning-equals-worse-execution/#comments</comments>
		<pubDate>Tue, 06 Apr 2010 07:27:55 +0000</pubDate>
		<dc:creator>Justin Roff-Marsh</dc:creator>
				<category><![CDATA[Measures and General Management]]></category>
		<category><![CDATA[Slaying Sacred Cows]]></category>
		<category><![CDATA[measurement]]></category>
		<category><![CDATA[planning]]></category>
		<category><![CDATA[toc]]></category>

		<guid isPermaLink="false">http://www.salesprocessengineering.net/2010/04/05/why-better-planning-equals-worse-execution/</guid>
		<description><![CDATA[Recently I posted a quick-and-dirty guide to process improvement. One particularly difficult question that I skipped over in that post was this one: When you are mapping your workflow, how do you determine the ideal level of granularity?&#160; In other words, how much detail is too much? Conventional wisdom is that: Planning and execution are [...]]]></description>
			<content:encoded><![CDATA[<p>Recently I posted a <a target="_blank" href="http://www.salesprocessengineering.net/2010/03/12/a-quick-and-dirty-approach-to-process-improvement/">quick-and-dirty guide to process improvement</a>. One particularly difficult question that I skipped over in that post was this one:</p>
<p style="margin-left: 30px">When you are mapping your workflow, how do you determine the ideal level of granularity?&nbsp; In other words, how much detail is too much?</p>
<p>Conventional wisdom is that:</p>
<ol>
<li>Planning and execution are two discrete activities (remember this assumption)</li>
<li>The key to good execution is lots and lots of planning (which tends to mean planning at a very granular level)</li>
</ol>
<p>Conventional wisdom is wrong, however.&nbsp; And this is evidenced by the many examples of poor execution we encounter on a day-to-day basis.</p>
<p>My argument (and this is classic <a target="_blank" href="http://www.salesprocessengineering.net/toc/">TOC</a>) is that, above a very low <em>detail </em>threshold, more planning actually means worse execution!</p>
<p>In other words, in most cases, to execute better, you should plan only at a high (non-granular) level.</p>
<h4>The relationship between granularity and confidence</h4>
<p>Let&rsquo;s imagine that we are planning a simple workflow &ndash; getting to work in the morning.&nbsp; Here&rsquo;s a high-level (low-detail) plan:</p>
<ol>
<li>Get out of bed</li>
<li>Shower</li>
<li>Get dressed</li>
<li>Drive to work</li>
<li>Log-in to computer</li>
</ol>
<p>And here&rsquo;s the low-level (high-detail) one:</p>
<ol>
<li>Upon awakening, check to see if alarm is sounding</li>
<li>If so, deactivate alarm</li>
<li>If not, check to see if current time is greater than [<em>alarm time</em> minus 10 minutes]</li>
<li>If so, cancel alarm and get out of bed</li>
<li>If not, go back to sleep</li>
<li>And so on &hellip;</li>
</ol>
<p>Imagine that you completed the second (low-level) plan, and then compared it with the first &ndash; and answered this question for each plan?</p>
<p style="margin-left: 30px">Rate your degree of confidence that reality will <em>play-out </em>as specified in the plan? In other words, how confident are you that each of these activities will be performed in exactly the sequence specified?</p>
<p>My guess is that you will be <em>highly confident </em>where the first plan is concerned &ndash; and <em>not-at-all confident </em>in the case of the second.</p>
<p>In fact, it&rsquo;s probably worse than that. In the case of the second plan, you will likely be certain that reality <em>will not </em>play out as specified by the plan.</p>
<p>The irony is that the second plan creates a perception of <em>accuracy, </em>in spite of the fact that your confidence in the plan is practically zero!</p>
<h4>Finding the inflection point (essential <em>and </em>non-commutative)</h4>
<p>It&rsquo;s tempting to assume that there&rsquo;s a linear relationship between granularity and confidence (that they vary in direct proportion).&nbsp; And, if that&rsquo;s the case, there&rsquo;s no correct answer to the critical <em>how much detail</em> question.</p>
<p>The reality is that the relationship is definitely non-linear: as the granularity of the plan increases incrementally, beyond a critical <em>detail threshold, </em>your confidence in the plan plunges rapidly towards zero.</p>
<p>Here&rsquo;s why:</p>
<ol>
<li>All the activities in the first plan are essential (you simply can&rsquo;t skip any)</li>
<li>Each activity (relative to its predecessor or successor) is <abbr style="border-bottom: navy 1px dotted" title="Washing and drying clothes resembles a noncommutative operation; washing and then drying produces a markedly different result to drying and then washing.">non-commutative</abbr> &ndash; meaning that you can&rsquo;t swap the sequence without dramatically changing the outcome</li>
</ol>
<p>However, with a slight increase in granularity, these two conditions cease to apply: not all activities are essential and the outcome can conceivably be delivered with an alternative sequence of activities.</p>
<p style="margin-left: 30px">So, my suggestion is that you should plan only to the level of detail where you are confident that all activities are (a) essential and (b) non-commutative (relative to their neighbors).</p>
<h4>Semantics are important!</h4>
<p>I can almost feel your incredulity at this point! How can a plan at this high level of detail be sufficient for execution?</p>
<p>And your reaction is warranted &hellip; because it can&rsquo;t be!</p>
<p>The high-level plan that I&rsquo;m recommending is sufficient for planning &ndash; but <em>not </em>sufficient for execution.&nbsp; The thing is that planning must continue <em>after </em>the creation of <em>the plan</em>!</p>
<p>To clear the confusion we need two words for planning:</p>
<ol>
<li>Pre-plan planning (the planning phase, terminating with THE PLAN) &ndash; let&rsquo;s call this <em>planning</em></li>
<li>Post-plan planning (the execution phase) &ndash; let&rsquo;s call this <em>fine-tuning</em></li>
</ol>
<p>So, in summary, here&rsquo;s the solution:</p>
<ol>
<li>Create a plan that contains <em>only </em>the degree of detail that enables you to be <em>highly confident </em>that reality will play-out as prescribed</li>
<li>Accept that the level of detail in the plan is insufficient for execution</li>
<li>Manage prioritization decisions on a <em>day-to-day </em>basis to ensure that reality tracks to the plan</li>
</ol>
<p>In the post referenced above (<a target="_blank" href="http://www.salesprocessengineering.net/2010/03/12/a-quick-and-dirty-approach-to-process-improvement/">quick-and-dirty approach</a>), I talked about the importance of centralizing scheduling and building a management information system (MIS).</p>
<p>If you re-read that article it should be clear now that both of these initiatives are essential for the management of execution.&nbsp; It should also be clear that the MIS should be designed to enable management to fine-tune the prioritization of <em>low-level </em>tasks so as to ensure the compliance of the undertaking with the <em>high-level </em>plan.</p>
<p>(<em>Execution management </em>is outside the scope of this posting. To explore the subject further, read my brief overview of <em><a href="http://www.salesprocessengineering.net/spe/criticalchain/">Critical Chain Project Management</a>.</em>)</p>
]]></content:encoded>
			<wfw:commentRss>http://www.salesprocessengineering.net/2010/04/05/why-better-planning-equals-worse-execution/feed/</wfw:commentRss>
		<slash:comments>6</slash:comments>
		</item>
		<item>
		<title>A quick-and-dirty approach to sales operations process improvement</title>
		<link>http://www.salesprocessengineering.net/2010/03/12/a-quick-and-dirty-approach-to-process-improvement/</link>
		<comments>http://www.salesprocessengineering.net/2010/03/12/a-quick-and-dirty-approach-to-process-improvement/#comments</comments>
		<pubDate>Sat, 13 Mar 2010 02:45:11 +0000</pubDate>
		<dc:creator>Justin Roff-Marsh</dc:creator>
				<category><![CDATA[Measures and General Management]]></category>
		<category><![CDATA[customer service]]></category>
		<category><![CDATA[inside sales]]></category>
		<category><![CDATA[measurement]]></category>
		<category><![CDATA[process improvement]]></category>

		<guid isPermaLink="false">http://www.salesprocessengineering.net/2010/03/12/a-quick-and-dirty-approach-to-process-improvement/</guid>
		<description><![CDATA[As you know, we build a lot of sales processes, here at Ballistix.&#160; You may not know that we build almost as many customer-service teams, inside-sales teams, pre-production teams and even small project teams (in knowledge-based environments). The work we do in these non-traditional (for us) environments is very gratifying and, often times, generates enormous [...]]]></description>
			<content:encoded><![CDATA[<p>As you know, we build a lot of sales processes, here at Ballistix.&nbsp; You may not know that we build almost as many <i>customer-service </i>teams, <i>inside-sales </i>teams, <i>pre-production </i>teams and even small <i>project </i>teams (in knowledge-based environments).</p>
<p>The work we do in these non-traditional (for us) environments is very gratifying and, often times, generates enormous payback for our clients.</p>
<p>So that just started me thinking.&nbsp; Can I generalize from our approach to the sales environment &#8212; and from the work we do in other environments &#8212; to come up with a general approach to process improvement?&nbsp; My plan is not to write the book on process engineering (others have done that); rather, it&#8217;s to provide a step-by-step method that you can implement with your notebook computer in one hand, a coffee in the other, and look of gleeful masterly in your eye!</p>
<p>Here&#8217;s that method; in five simple steps.</p>
<h3>1. Define the goal and necessary conditions</h3>
<p>What is the goal of this environment?&nbsp; And what are the conditions that must be met in order for your achievement of that goal to be valid?</p>
<p>Sadly, answering these questions does not really power you forward.&nbsp; However, they must be answered because the answers provide the context required to answer <i>all the other </i>questions you&#8217;ll encounter as we work through this process.</p>
<p>So, if you&#8217;re building a customer service team, your goal might be to: <i>resolve customer issues rapidly</i>.</p>
<p>Necessary conditions might include: <i>the maintenance of sufficient protective capacity to ensure resolution times are within customer tolerances </i>and <i>the avoidance of unnecessary expenditure.</i></p>
<p>Nothing too fancy here!&nbsp; Just the basics.</p>
<h3>2. Map it</h3>
<p>This is the fun bit.</p>
<p>You&#8217;ll need a copy of Microsoft Visio (Google: <i>Visio free trial</i>) or a sheet of graph paper and writing implements.</p>
<p>The trick here is knowing what to chart.&nbsp; You want to map a <i>high-level</i> workflow only.&nbsp; You&#8217;ll know if it&#8217;s high-level because:</p>
<ol>
<li>You&#8217;ll only need three symbols (an activity box, a <i>state </i>(input/output)<i> </i>circle and a connector (line)</li>
<li>The workflow will be linear: no loops or recursions</li>
<li>Everyone involved will complain that it&#8217;s too simple</li>
</ol>
<p>Here&#8217;s an example of what the finished result will look like.</p>
<p><a target="_blank" href="http://www.salesprocessengineering.net/wp-content/uploads/image/SampleWorkflow.jpg"><img alt="" align="textTop" width="600" height="101" src="http://www.salesprocessengineering.net/wp-content/uploads/image/SampleWorkflow.jpg" /></a></p>
<p style="text-align: left"><small>[click image to view full size]</small></p>
<h3>2. Division of labor</h3>
<p>You saw this one coming!</p>
<p>As part of creating the workflow, you should consider division of labor (who does what?).&nbsp; You can see in the image above, that each role as been assigned a <i>swim-lane</i>.</p>
<p>Generally speaking, you&#8217;ll multiply productivity by:</p>
<ol>
<li>Eliminating multitasking</li>
<li>Having specialists perform work that corresponds with their expertise</li>
</ol>
<p>However, you need to balance the theoretical productivity improvements with some practical concerns:</p>
<ol>
<li>The possible cost of additional personnel</li>
<li>The multiplication in process complexity as the number of hand-offs increases</li>
</ol>
<p>Here are the general guidelines I use:</p>
<ol>
<li>Split activities that are obviously dissimilar (<i>technical drawings </i>and <i>booking flights</i>, for example)</li>
<li>Split activities that are performed in the field from those that are performed in the office</li>
<li>Split pure telephone work from clerical work (for example, rather than having clerks chase the pre-requisites required for their work, have a dedicated phone person who <i>manages pre-requisites</i>)</li>
<li>Split work that requires high-level decision-making from <i>pure-vanilla </i>work</li>
</ol>
<p>More importantly, you should consider which resource in your team is likely to become the constraint (bottleneck) as volume increases.&nbsp; You should focus your attention here first.&nbsp; For example, if you are processing mortgage applications and you have a person with specialist knowledge who has the potential to be a bottleneck, consider routing all plain-vanilla work (and phone work, etc) around this person.</p>
<p>Also, bear in mind that some people are <i>specialist generalists</i>.&nbsp;&nbsp; In other words, they add value by being across a lot of stuff!&nbsp; Managers fit into this category &#8212; as do customer-service representatives.&nbsp; So be careful not to kill the goose that lays the golden egg.</p>
<p><span id="more-126"></span></p>
<h3>4. Centralize scheduling</h3>
<p>It&#8217;s here that you earn your keep!&nbsp; If there&#8217;s one defining characteristic of EVERY process we build at Ballistix, it&#8217;s that we always have a dedicated process coordinator.&nbsp; A person whose <i>sole </i>responsibility is to coordinate the workflow &#8212; but who is not actively involved in any of the core activities within the workflow.</p>
<p>I would go so far as to suggest that you don&#8217;t have a process until you have a person who&#8217;s sole responsibility is to keep the wheels turning day after day.</p>
<p>In our traditional (field) sales environments, this person is the sales coordinator.&nbsp; A person who sits behind each salesperson and who operates essentially as that person&#8217;s Executive Assistant.&nbsp; In an <i>inside </i>environment (customer service, inside sales, pre-production, etc), we&#8217;re more likely to have one person coordinating a larger team.&nbsp; In many cases, this person will also take responsibility for <i>pre-requisite management</i> (see earlier discussion).</p>
<p>Here are the activities a coordinator would typically perform:</p>
<ol>
<li>Chair daily (or twice-daily) work-in-process (WIP) meetings</li>
<li>Determine case (job) and task priorities</li>
<li>Overview the general operation (flow) of the environment</li>
<li>Ensure data integrity (accuracy and currency) in your CRM and/or ERP</li>
<li>Manage <i>management-information system </i>(see next section)</li>
</ol>
<p>In most cases we recruit young, smart, sassy graduates to fill coordinator roles.&nbsp; Generally, you don&#8217;t want an engineer in this role.&nbsp; In fact, it&#8217;s better to retain an engineer to design the environment so as to ensure that you don&#8217;t need an engineer to coordinate it!&nbsp; Of course the design of a robust environment is exactly the subject of this article.</p>
<h3>5. Management-information system (MIS)</h3>
<p>You know what they say: <i>if you can&#8217;t measure it, you can&#8217;t manage it</i>.</p>
<p>Well, I wish <i>they </i>wouldn&#8217;t say that.&nbsp; This maxim is often interpreted as an exhortation to <i>measure everything</i>.&nbsp; And if you measure everything, you&#8217;re measuring nothing.</p>
<p>What I mean is that no data is bad, but too much data is just as bad.&nbsp; What we need is <i>information</i>.</p>
<p><a target="_blank" href="http://www.salesprocessengineering.net/toc/">Eli Goldratt</a> defines <i>information</i> as <i>the answer to the question asked &#8230; </i>and I like that!&nbsp; It means that rather than starting with measurements, we should start with questions.</p>
<p>Here are some questions that I think should be answered in every environment:</p>
<ol>
<li>When should I release work to the team (if you release work as it appears, the team will certainly multitask itself into a total logjam within days!)?</li>
<li>What completion date should I quote for this case (and be confident that it will be delivered on time)?</li>
<li>When must I expedite a case to ensure its on-time completion?</li>
<li>When should I avoid the temptation to tamper and leave well alone?</li>
<li>What is the load on all team members?</li>
<li>When the flow is disrupted, what is the most common cause of that disruption?</li>
</ol>
<p>Now, obviously, this list is not exhaustive but these answers are, to my mind, the critical ones.&nbsp; So, do you think the standard reports in your ERP or CRM are designed to answer these questions for you?&nbsp; Of course not!&nbsp; Those reports are designed to satiate the noisy <i>measure everything </i>brigade.</p>
<p>So, you need to build your own MIS.&nbsp; Two ways to do it:</p>
<ol>
<li>A physical, production-style <i>buffer board</i></li>
<li>A fancy, electronic <i>business-intelligence </i>system that generates real-time reports from the data sitting in your CRM/ERP&#8217;s data-store</li>
</ol>
<p>Let&#8217;s talk about the first option.</p>
<p>You want a board that represents time and capacity (we&#8217;ll just work with two dimensions for now!)&nbsp; We&#8217;ll track time on the horizontal access with TODAY on the far left and X-DAYS on the far right (where x is the maximum lead-time of a healthy case).&nbsp; So time moves from right to left &#8212; just like you&#8217;re on a train, looking out the window. The vertical axis is designed to limit the number of cases that can occupy any one time-slot.</p>
<p>The coordinator creates a magnetic card for each job.&nbsp; Each card contains the list of tasks within the workflow.&nbsp; Cards also have stickers attached &#8212; where each sticker indicates a pre-requisite.&nbsp; At regular intervals the coordinator moves all jobs one time-slot to the left &#8212; to indicate the passage of time.&nbsp; Additionally, stickers are removed as pre-requisites are collected and tasks are checked as they are completed.</p>
<p>We would generally complement the buffer board with an Excel workbook that auto-generates the cards &#8212; and that enables the coordinator to track the completion dates of key milestones so that we retain a rudimentary history of jobs once they leave the board.</p>
<p>Here&#8217;s an example of a client&#8217;s buffer board.&nbsp; Pretty? No.&nbsp; Effective? Definitely!</p>
<p><a target="_blank" href="http://www.salesprocessengineering.net/wp-content/uploads/image/SampleBufferBoard.jpg"><img alt="" align="textTop" width="300" height="184" src="http://www.salesprocessengineering.net/wp-content/uploads/image/SampleBufferBoard.jpg" /></a></p>
<p><small>[click image to view full size]</small></p>
<p style="text-align: left">So how about the second option?, I can hear you asking.&nbsp; Can&#8217;t it be electronic?&nbsp; We so like electronic.</p>
<p style="text-align: left">Well, yes it can and, in some environments (high volume, high complexity) it has to be.&nbsp; But <i>electronic </i>costs real money.&nbsp; And another disadvantage of electronic is that it tends to be less visible &#8212; less accessible.&nbsp; We resolve this in some environments by displaying key metrics on plasma screens &#8230; but now we&#8217;re talking even more money!</p>
<p style="text-align: left">To create an electronic MIS, you build the reports in Excel (our drug of choice), Crystal Reports, Cognos or similar.&nbsp; You then integrate the reports with the data from your CRM or ERP (or often both).</p>
<p>Of course, with electronic, <i>if you can dream it, you can do it </i>&#8230; but this tends to create as many problems as it solves.</p>
<p>Following are some samples of some of the prettier reports that our clients&#8217; MIS&#8217;s contain.</p>
<p><a target="_blank" href="http://www.salesprocessengineering.net/wp-content/uploads/image/SampleMIS1.jpg"><img alt="" align="left" width="127" height="100" src="http://www.salesprocessengineering.net/wp-content/uploads/image/SampleMIS1.jpg" /></a></p>
<p><a target="_blank" href="http://www.salesprocessengineering.net/wp-content/uploads/image/SampleMIS2.jpg"><img alt="" align="bottom" width="103" height="100" src="http://www.salesprocessengineering.net/wp-content/uploads/image/SampleMIS2.jpg" /></a></p>
<p><a target="_blank" href="http://www.salesprocessengineering.net/wp-content/uploads/image/SampleMIS3.jpg"><img alt="" align="left" width="243" height="100" src="http://www.salesprocessengineering.net/wp-content/uploads/image/SampleMIS3.jpg" /></a></p>
<p><a target="_blank" href="http://www.salesprocessengineering.net/wp-content/uploads/image/SampleMIS4.jpg"><img alt="" align="baseline" width="175" height="100" src="http://www.salesprocessengineering.net/wp-content/uploads/image/SampleMIS4.jpg" /></a></p>
<p><small>[click images to view full size]</small>&nbsp;</p>
<p>The best advice I can give you with respect to the design of the MIS, I&#8217;ve left until last.</p>
<p>Don&#8217;t start by designing the reports, start by designing the WIP meeting.&nbsp; That&#8217;s right, determine the questions that you must answer, in what sequence to have a fast, productive, daily (or twice-daily) WIP meeting and then design your MIS to deliver the necessary data in exactly that sequence.</p>
<p>These five steps cover a lot of ground, but I think they&#8217;ll provide a valuable framework for your next process-improvement initiative.&nbsp; If you&#8217;d like me to <i>fill in some gaps</i>, use the comments link at the start of this article to ask questions.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.salesprocessengineering.net/2010/03/12/a-quick-and-dirty-approach-to-process-improvement/feed/</wfw:commentRss>
		<slash:comments>8</slash:comments>
		</item>
		<item>
		<title>The triple bottom line: two parts nonsense</title>
		<link>http://www.salesprocessengineering.net/2009/03/19/the-triple-bottom-line-two-parts-nonsense/</link>
		<comments>http://www.salesprocessengineering.net/2009/03/19/the-triple-bottom-line-two-parts-nonsense/#comments</comments>
		<pubDate>Thu, 19 Mar 2009 03:24: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[measurement]]></category>

		<guid isPermaLink="false">http://www.salesprocessengineering.net/2009/03/19/the-triple-bottom-line-two-parts-nonsense/</guid>
		<description><![CDATA[Here&#8217;s a favorite post of mine from our old Yahoo group &#8230; Philosophies collide! I was presenting a workshop in Darwin (Australia) recently when the manager of a (government-funded) organization objected that our methods focus only on the financial bottom line &#8212; and that they are not conducive with the concept of triple-bottom-line management. Now, [...]]]></description>
			<content:encoded><![CDATA[<p>Here&#8217;s a favorite post of mine from our old Yahoo group &#8230;</p>
<h3>Philosophies collide!</h3>
<p>I was presenting a workshop in Darwin (Australia) recently when the manager of a (government-funded) organization objected that our methods focus only on the financial bottom line &#8212; and that they are not conducive with the concept of <i>triple-bottom-line </i>management.</p>
<p>Now, I must have had my head in the sand for some time because, up until then, I had never heard of this peculiar concept.</p>
<p>The idea is that an organization shouldn&#8217;t strive to improve just one bottom line (the financial one), rather it should also pursue the improvement of two (equally important) additional bottom lines: an environmental one and a social one.</p>
<p>Now, thinking readers will have already recognized two obvious objections to the triple bottom line:</p>
<ol>
<li>Division of labor (As Adam Smith pointed out, the economy as a whole benefits most when organizations specialize).</li>
<li>Practicality (there can be no single standard of &#8216;environmental good&#8217; or &#8216;social good&#8217;; only multiple measures that will ultimately conflict with one another)</li>
</ol>
<p>But the argument that I presented in Darwin was simpler &#8212; and I suspect stronger &#8212; than either of these.&nbsp; And it it was pure TOC!</p>
<p>In TOC terms, the concept of the <i>triple bottom line </i>amounts to an argument that the organization should pursue multiple goals.</p>
<p>Is this possible?</p>
<p>Well, we know that a business is a system (a goal-seeking system).&nbsp; This means that a business is not a collection of independent parts &#8212; all the parts are connected (directly or indirectly) to one another (a part that wasn&#8217;t connected one way or another would not be part of the system).</p>
<p>We know that each of the parts of the (business) system has finite capacity: accordingly, the system has a whole has finite capacity.&nbsp; (If this wasn&#8217;t the case, it would have achieved it&#8217;s goal in the instance in which it came into existence!)</p>
<p>So, with these facts in mind, let&#8217;s think what happens when a business attempts to pursue multiple goals simultaneously.&nbsp; Inevitably, the pursuit of each goal requires a different allocation of resources from that finite resource pool.&nbsp; (This is called &#8216;resource contention&#8217;.)</p>
<p>The only way to resolve resource contention is to rank the three goals in order of priority.</p>
<p>The only way to perform this ranking is to nominate one of these goals as <i>The Goal</i>, and the others as <i>Necessary Conditions</i>.&nbsp; There is simply <i>no other alternative</i> in a finite-capacity system.</p>
<p>For this reason, I propose that a business cannot pursue multiple goals and that the notion of a multiple-bottom-line is discredited!</p>
<h3>Post scripts</h3>
<p>In the TOC world, the following definitions apply (my wording):</p>
<p style="margin-left: 40px">The Goal: the output the system is designed to produce (measured in units called <i>Throughput</i>).</p>
<p style="margin-left: 40px">Necessary Conditions: conditions that must be complied with in order for the achievement of the goal to be valid.&nbsp;</p>
<p style="margin-left: 40px">Necessary conditions are bi-modal (you either comply or you don&#8217;t).&nbsp;If we&#8217;re dealing with a typical business, the goal is to maximize the return on shareholder funds.&nbsp; An example of a necessary condition is &#8216;cashflow&#8217;.&nbsp; Maintaining adequate cash-on-hand is critical.&nbsp; More cash than that which is adequate provides no additional benefit.</p>
<p>Sadly, the workshop delegate was not happy with my answer.&nbsp; He left (in a huff) in the lunch break.&nbsp; By the way, he was correct to object that our method is not conducive with triple-bottom-line management.&nbsp; It isn&#8217;t.&nbsp; But neither is reality!</p>
]]></content:encoded>
			<wfw:commentRss>http://www.salesprocessengineering.net/2009/03/19/the-triple-bottom-line-two-parts-nonsense/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<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>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 establish a clear cause and effect relationship between business marketing promotional expenditure and sales</title>
		<link>http://www.salesprocessengineering.net/2008/07/20/how-to-establish-a-clear-cause-and-effect-relationship-between-promotional-expenditure-and-sales/</link>
		<comments>http://www.salesprocessengineering.net/2008/07/20/how-to-establish-a-clear-cause-and-effect-relationship-between-promotional-expenditure-and-sales/#comments</comments>
		<pubDate>Sun, 20 Jul 2008 11:17:41 +0000</pubDate>
		<dc:creator>Ballistix-jason</dc:creator>
				<category><![CDATA[Measures and General Management]]></category>
		<category><![CDATA[measurement]]></category>
		<category><![CDATA[opportunity management]]></category>
		<category><![CDATA[promotions]]></category>
		<category><![CDATA[relationship acquisition]]></category>
		<category><![CDATA[sales]]></category>

		<guid isPermaLink="false">http://www.salesprocessengineering.net/2008/07/20/how-to-establish-a-clear-cause-and-effect-relationship-between-promotional-expenditure-and-sales/</guid>
		<description><![CDATA[and how to fast-track the growth of your business in the process. Over lunch, a CEO recently admitted to me that his financial controller was using his organisation&#8217;s profits to build quite a substantial commercial property portfolio. When I asked if this was best use of his organisation&#8217;s free cashflow, he smiled, &#34;How did I [...]]]></description>
			<content:encoded><![CDATA[<h2><img align="right" alt="" src="http://www.salesprocessengineering.net/wp-content/uploads/image/business_graph_image.jpg" />and how to fast-track the growth of your business in the process.</h2>
<p>Over lunch, a CEO recently admitted to me that his financial controller was using his organisation&rsquo;s profits to build quite a substantial commercial property portfolio.</p>
<p>When I asked if this was best use of his organisation&rsquo;s free cashflow, he smiled, &quot;How did I know you&rsquo;d ask that question?</p>
<p>&quot;The fact is,&quot; he continued, &quot;the availability of capital is not currently a constraint on our growth.&quot;</p>
<p>&quot;It might not be a constraint on your organic growth,&quot; I argued, &quot;but I still think that money could be better invested in new client acquisition.&quot;</p>
<p>We spent the rest of that lunch scribbling on napkins. Together, we discovered that a dollar invested in promotional expenditure was actually providing this CEO&rsquo;s organisation with a better-than 900% return on investment!</p>
<p>By the time coffee was served, we&rsquo;d agreed that his organisation&rsquo;s sales process could provide a much more favourable return on capital than even the bluest of blue-chip commercial property investments.</p>
<p>In our experience, this holds true for most organisations. Unfortunately, most are reluctant to invest in their sales processes because (unlike other business processes) it&rsquo;s impossible to calculate a return on investment.</p>
<h3>Science versus art</h3>
<p>If you&rsquo;re a follower of our Relationship-centric Marketing methodology, you&rsquo;ll know that a sales process has inputs and outputs &mdash; just like any other business process.</p>
<p>You&rsquo;ll know that a sales process (as the word process implies) consists of a sequence of simple, interrelated steps &mdash; just like any other business process.</p>
<p>And you&rsquo;ll know, at least in theory, that each step in a sales process can be measured, managed and optimised &mdash; just like any other business process.</p>
<p>This article explains the science (and more importantly, the mathematics) behind sales process management. It will show you how to take control of your sales process and use it to fast-track the growth of your organisation.</p>
<p>If you didn&rsquo;t pay much attention to mathematics at school, you may find this article tough-going at times. But please be sure to persevere.</p>
<p>I&rsquo;m sure you&rsquo;ll discover that your sales process is harbouring significant growth potential!</p>
<h3>Management by numbers</h3>
<p>If you think about it, the word management presupposes measurement. The fact is, if you can&rsquo;t measure it, you simply can&rsquo;t manage it.</p>
<p>So, to manage a sales process (or any process for that matter), we need to know what to measure. Generally speaking, we will measure inputs, outputs and time. Specifically, we&rsquo;ll measure:</p>
<ul>
<li>Throughput (output/time)</li>
<li>Productivity (output/inputs)</li>
</ul>
<p>We&rsquo;ll measure these key performance indicators (KPIs) for the process as a whole, and then we&rsquo;ll break the sales process into its key components (sub-processes) and devise a set of KPIs for each component.</p>
<p>It&rsquo;s worth remembering that your sales process is actually a component of a much larger system: your entire business. In the context of your business as a whole, revenue is a measure of throughput, and gross profit is a measure of productivity. The problem with these indicators is that they are trailing indicators: that is, they tell you more about what you have done in the past than they do about what you should do in the future.</p>
<p>Because your sales process is the first step in your entire organisational process, the information you collect from monitoring these performance indicators can be used to enable real-time process optimisation.</p>
<p>As we dissect and analyse the sales process, we&rsquo;ll make references to a fictitious company we&rsquo;ll call Correlex. Correlex is an engineering firm that consults to property developers. Correlex&rsquo;s clients all pay a retainer of $450 a month to access its consulting services. References to Correlex will appear in indented sections, with a green sidebar, just like this one.</p>
<h3>Measuring the process as a whole</h3>
<p>The objective of your sales process is obviously to generate sales.</p>
<p>This process must be designed and managed to ensure that it delivers a sufficient volume of sales in exchange for a commercially realistic investment.</p>
<p>For simplicity&rsquo;s sake, we&rsquo;ll assume that the objective of our sales process is to acquire new clients. But don&rsquo;t worry, we will be sure to take follow-on sales (and even referrals) into account.</p>
<p>Accordingly, the two global indicators in which we&rsquo;re most interested are:</p>
<ul>
<li>Client acquisition rate (new clients per month).</li>
<li>Client acquisition cost (cost per new client).</li>
</ul>
<p>When we&rsquo;re measuring client acquisition cost, we&rsquo;re dividing the amount we invested in the acquisition of relationships by the number of clients acquired as a result of that expenditure.</p>
<p>When we calculate this figure, we only take into account the variable costs associated with the promotional campaign that acquired each particular client relationship. With a promotional campaign, variable costs are typically media costs. We do not factor in the fixed costs associated with that promotional campaign (the cost of creating the campaign). Nor do we include the fixed costs associated with the rest of the sales process (e.g. the cost of managing the relationship with the potential client).</p>
<p>We ignore fixed costs because these are the cost of operating your sales process, rather than process inputs.</p>
<p>Our client acquisition cost is most useful for monitoring the performance of our relationship acquisition campaigns. It&rsquo;s important to remember that, unless you have a very short sales cycle, client acquisition cost tends to be longer-term performance indicator. (The term sales cycle refers to the average time span between the acquisition of a relationship and the consummation of a sale.) We&rsquo;ll uncover a short-term indicator when we examine the relationship acquisition step of the sales process.</p>
<p>When the CEO of Correlex reviews his organisation&rsquo;s sales process, he discovers that, averaged over the last 12 months, Correlex acquired two new clients each month.</p>
<p>To determine his average client acquisition cost, he divides his total variable promotional costs by the number of clients he acquired over this period.</p>
<p>In the last 12 months, Correlex had advertised in the Financial Review, and in a number of specialist publications. It had also run 4 direct mail campaigns. Accordingly, its variable promotional costs consisted of the cost of media for the advertising campaigns, and the cost of mail processing for the direct mail campaigns.</p>
<p>In total, Correlex invested $9,600 in order to acquire 24 new clients: an average client acquisition cost of $400.</p>
<p>$9,600 / 24 = $400</p>
<h4>Optimisation</h4>
<p>It&rsquo;s obviously important to know how many sales your organisation is making. It&rsquo;s also nice to know how much each sale is costing you in promotional expenditure.</p>
<p>But, in isolation, this information is not particularly useful.</p>
<p>What you need to be able to do, is compare your actual performance with your optimal performance.</p>
<p>A common mistake in process management is to establish absolutes as targets. For example, it would be tempting to assume that the objective of your sales process is to generate as many sales as possible, for the lowest possible promotional expenditure.</p>
<p>The reality is that sales and promotional expenditure are interrelated. (You can&rsquo;t have one without the other.) A singular focus on either maximising sales or minimising promotional costs is likely to sub-optimise the performance of your sales process. The key is to determine the optimal relationship between promotional expenditure and sales.</p>
<p>Accordingly, you now need to determine the optimal figures for each of your global KPIs.</p>
<p>Client acquisition rate is easy. Obviously, your optimal figure is determined by the capacity of your production and distribution processes. (There&rsquo;s little point generating sales that can&rsquo;t possibly be fulfilled.)</p>
<p>However, your client acquisition cost requires a little more thought.</p>
<p>As the graph below illustrates, as your promotional expenditure increases, the number of clients you acquire should also increase. However, with the increased promotional expenditure, the profitability of each client relationship suffers.</p>
<p>In theory, your optimal client acquisition cost is the point where these two lines intersect.</p>
<p align="center"><img alt="" src="http://www.salesprocessengineering.net/wp-content/uploads/image/opt_client_acq_cost.gif" /></p>
<p>In practice, it will take some experimentation (and careful measurement) to calculate your optimal acquisition cost.</p>
<p>The starting point for this calculation is the determination of the lifetime value of a client. (Your optimal client acquisition cost will be a percentage of this figure.)</p>
<p>It is difficult to overemphasise the importance of performing this calculation. Without an understanding of the dollar value of a client, it is simply impossible to effectively manage your sales process.</p>
<p>In our experience, because most organisations have no way to value a client relationship, most grossly underestimate the amount that they are prepared to invest in client acquisition.</p>
<p>This under-investment in client acquisition seriously retards the growth of many organisations.</p>
<p>The publishing industry is one industry that does understand the concept of lifetime value. Typically publishers of magazines and other periodicals are prepared to invest at least 100% of the first year&rsquo;s subscription revenue in order to acquire a new subscriber!</p>
<h3>Valuing a client relationship</h3>
<p>In financial terms, a client relationship is simply an annuity income stream.</p>
<p>It follows that you can value a client relationship, just as you can value any other kind of annuity (income-producing investment).</p>
<p>You value an annuity using a net present value calculation. (Net present value is the sum of a series of future payments, discounted for the cost of capital.)</p>
<p>To calculate the lifetime value of a client, determine the gross profit you earn in an average year from an average client, then multiply this by the figure in the annuity table below that corresponds to the number of years you retain this average client.</p>
<p align="center"><img alt="" src="http://www.salesprocessengineering.net/wp-content/uploads/image/amortisation.gif" /></p>
<p>This table shows how much a series of $1 payments, to be paid at the end of each year for a specified number of years into the future, is currently worth, with interest at different rates, compounded annually. In other words, the table shows what you should be willing to pay, today, in order to receive a certain series of future payments of $1 each.</p>
<p>As you already know, Correlex sells a consulting service for $450 a month.</p>
<p>To calculate the lifetime value of an average client, it must multiply the gross profit in a transaction by the number of times Correlex transacts with an average client over the lifetime of the client relationship.</p>
<p>On average, Correlex retains a client for three years. Its gross profit is 70% (or $315).</p>
<p>It chooses to account for cost of capital at its overdraft rate, 9%.</p>
<p>Correlex calculates the net present value of a client relationship by first calculating its annual gross profit, and then multiplying this figure by the appropriate multiplier from the table above:</p>
<p>Average annual gross profit: $450 x 12 x 70% = $3,780</p>
<p>Net present value: $3,780 x $2.53 = $9,563</p>
<p>The CEO of Correlex is surprised to see just how valuable a client relationship is.</p>
<p>Prior to performing this calculation, he was considering reducing his promotional expenditure ($400 per client seemed like a lot &mdash; especially for an engineering firm).</p>
<p>Now, however, he suspects that he has been underspending on client acquisition!</p>
<p>Accordingly, he decides to set his optimal client acquisition cost at a (conservative) $900. He also resolves to watch his KPIs carefully and review this figure in six months&rsquo; time.</p>
<p>As explained, your optimal client acquisition cost will be a percentage of the lifetime value of a client. The actual percentage will depend on the fixed costs associated with your sales process (and your sales volume). It will almost certainly be more than 10%. It may even be as high as 50%.</p>
<p>(While the idea of investing 50% of the lifetime value of a client in client acquisition may seem ludicrous, it&rsquo;s important to remember that, once an organisation has passed its break-even point, it&rsquo;s effectively enjoying a 100% return on this promotional expenditure. Try earning that in the bank!)</p>
<p>Before he can finalise his global performance indicators, the CEO of Correlex must determine his optimal client acquisition rate. A quick call to his operations manager confirms that Correlex is capable handling four new clients a month.</p>
<p align="center"><img alt="" src="http://www.salesprocessengineering.net/wp-content/uploads/image/kpi4.gif" /></p>
<p>These indicators provide Correlex&rsquo;s CEO with an overview of the relationship between his sales process&rsquo;s inputs and outputs.</p>
<p>His suspicion that he is underspending on promotion is supported by the fact that Correlex is growing at 50% of its optimal rate.</p>
<p>Because your global KPIs are longer-term indicators, they do not enable you to manage your sales process on a day-to-day basis.</p>
<p>To do this, we need to divide your sales process into its key components, and then devise a set of performance indicators for each.</p>
<p>You&rsquo;ll remember that a sales process consists of three components:</p>
<ul>
<li>Relationship acquisition</li>
<li>Relationship management</li>
<li>Opportunity management</li>
</ul>
<p>Let&rsquo;s start with the final component of the sales process and work backwards.</p>
<h3>Opportunity management</h3>
<p>The objective of your opportunity management process is to convert sales opportunities into sales (remember, we&rsquo;re assuming that a sale is a new client). This process will generally involve salespeople, operating either in the field, or from a call centre (or both).</p>
<p>A sales opportunity is typically an expression of interest in a specific product or service, generated as a result of your opportunity management process. (Sales opportunities are often called leads.)</p>
<p>As with your sales process as a whole, we are primarily interested in the throughput and the productivity of your opportunity management process.</p>
<p>Accordingly, we will begin by measuring:</p>
<ul>
<li>Client acquisition rate (clients per month)</li>
<li>Opportunity conversion rate (sales/opportunities x 100)</li>
</ul>
<p>Of course, the throughput of the opportunity management process (client acquisition rate) will be identical to the throughput of your sales process as a whole.</p>
<p>Your conversion rate is the percentage of sales opportunities that convert into sales.</p>
<p>The CEO of Correlex already knows his client acquisition rate.</p>
<p>What he doesn&rsquo;t know, is how many sales opportunities his consultants require in order to make each sale.</p>
<p>A survey of his consultants&rsquo; sales figures indicates that, on average, his consultants convert one in every 2.9 sales opportunities into sales. (Accordingly, his conversion rate is 35%.)</p>
<p>But these sales figures also reveal an interesting phenomenon. Correlex&rsquo;s CEO observes that conversion rates vary considerably from consultant to consultant. He also notices that there seems to be an inverse relationship between acquisition rate and conversion rate for individual consultants.</p>
<p>In other words, the consultants who acquire the most new clients tend not to have the highest conversion rates, and visa versa.</p>
<p>He wonders why &hellip;</p>
<h3>Optimising conversion rates</h3>
<p>Contrary to popular belief, the primary influencer of conversion rate is not the skill of salespeople.</p>
<p>Rather, it is the design of the opportunity management process.</p>
<p>In our experience, opportunity management processes are best designed with a view to minimising the time between the emergence of a sales opportunity and closure of that opportunity (a sales opportunity is closed when it is won, lost or abandoned).</p>
<p>Increasing the throughput of a sales process may result in lower conversion rates, but this is not necessarily a bad thing!</p>
<p>Sales managers typically manage their salespeople as if a conversion rate of 100% is achievable.</p>
<p>In reality, 100% is rarely an optimal conversion rate. The reason is that, as conversion rates go up, throughput goes down.</p>
<p>Ask yourself, which would you prefer: a salesperson who conducts 5 appointments a day, with a 40% conversion rate; or a salesperson who conducts 3 (highly qualified) appointments a week, with a 95% conversion rate? (Hint: salesperson A generates 10 sales a week, where salesperson B generates less than 3.)</p>
<p>You can take the following steps to increase the throughput of your sales process:</p>
<ul>
<li>Break the opportunity management process into a number of logical steps.</li>
<li>Ensure all sales opportunities follow the same process.</li>
<li>At each step in the opportunity management process, be sure to up-sell to the next step.</li>
<li>Actively manage open opportunities.</li>
</ul>
<p>You can manage individual (open) opportunities with a simple tabular report, like the one below. Normally, a sales team will work through this report in its weekly sales meeting. The key indicators to watch are the number of open opportunities and average days open. (If you sell a number of products with different price points, you may prefer to monitor the dollar value of opportunities).</p>
<p align="center"><img alt="" src="http://www.salesprocessengineering.net/wp-content/uploads/image/opp_rpt_sm.gif" /></p>
<p>Most CRM systems produce such a report; alternatively, you can create your own in Excel.</p>
<p>You can also use the weighted value and target close data from this report to produce sales forecasts.</p>
<p>Correlex&rsquo;s CEO reviews his consultants&rsquo; differing opportunity management processes. He identifies the consultant with the most efficient process and resolves to benchmark this process and make it the organisational standard.</p>
<p>This new benchmark calls for a conversion rate of 25% and an average days open of 45 days.</p>
<p>From these figures, he calculates that, at any one point in time, his organisation should have one and a half months&rsquo; worth of open opportunities:</p>
<p>Optimal monthly sales: 4</p>
<p>Opportunities required to make 10 sales: 4 / 25% = 16</p>
<p>Average days open: 45 (5 months)</p>
<p>Optimal open opportunities: 16 x 5 = 24</p>
<p align="center"><img alt="" src="http://www.salesprocessengineering.net/wp-content/uploads/image/kpi2.gif" /></p>
<h3>Relationship management</h3>
<p>The objective of your relationship management process is to generate a steady stream of sales opportunities from your relationships under management.</p>
<p>We do this by creating an automated communication program. This is a sequence of ongoing communications, where each communication is designed to add value to these relationships.</p>
<p>A typical communication program will consist of a monthly e-mail newsletter and bimonthly seminars or workshops.</p>
<p>We tend to take an indirect (longer-term) approach to the generation of sales opportunities. Our experience is that, if you can design the relationship management process to position your organisation as the leader in its particular field, sales opportunities will be forthcoming.</p>
<p>Events and other activities can be used to stimulate the flow of activities, but on many occasions, these activities will simply time-shift the emergence of opportunities &mdash; rather than creating opportunities you wouldn&rsquo;t otherwise have received.</p>
<p>You need to balance your need for sales opportunities against the requirement to add value to the relationships under your custodianship. There is a danger that, if you design your communications specifically to maximise the flow of sales opportunities, you may compromise the integrity of these relationships.</p>
<p>As with our other processes, we are primarily interested in monitoring throughput and productivity. Accordingly, our KPIs are as follows:</p>
<ul>
<li>Opportunities per month.</li>
<li>Opportunity realisation rate (monthly opportunities/relationships).</li>
</ul>
<p>Opportunity realisation rate advises you of the correlation between the number of relationships you have under management (the size of your database) and the number of sales opportunities these relationships produce each month.</p>
<p>Correlex has 1,500 contacts on its database. Because all of these contacts are recipients of Correlex&rsquo;s monthly e-mail newsletter, it referrs to them as subscribers.</p>
<p>On average, Correlex receives 12 sales opportunities a month from its subscriber database.</p>
<p>These 12 opportunities represent an opportunity realisation rate of 0.8%:</p>
<p>12 / 1,500 x 100 = 0.8%</p>
<p>In order to increase the flow of sales opportunities to the 16 per month required, Correlex&rsquo;s CEO realises he must acquire an additional 500 subscribers:</p>
<p>16 / 0.8% = 2,000</p>
<p align="center"><img alt="" src="http://www.salesprocessengineering.net/wp-content/uploads/image/kpi3.gif" /></p>
<h3>Relationship acquisition</h3>
<p>The objective of your relationship acquisition process is to acquire a steady stream of relationships with potential clients and centres of influence.</p>
<p>The input into this process is the investment in your relationship-acquisition campaigns (remember, we&rsquo;re only tracking variable costs). The output is obviously the relationships (or subscribers) you add to your database.</p>
<p>The precise management of this process is critical for two reasons:</p>
<ul>
<li>The flow of inbound opportunities is the key determinate of the throughput of the process as a whole.</li>
<li>In the absence of an objective performance measure, there is a high probability that you will either under- or over-spend on promotion.</li>
</ul>
<p>Our performance indicators for this process are:</p>
<ul>
<li>Relationship acquisition rate (relationships per month).</li>
<li>Relationship acquisition cost (cost per relationship).</li>
</ul>
<p>Relationship acquisition cost is calculated by dividing the variable cost of promotional campaigns by the number of new relationships acquired by those campaigns.</p>
<p>As with our global KPIs, these indicators don&rsquo;t mean much until we can compare actual and optimal figures.</p>
<p>Optimising your relationship acquisition process</p>
<p>The calculation of your optimal relationship acquisition rate is easy. This figure is determined by:</p>
<ul>
<li>Your target database size.</li>
<li>Your availability of promotional funds.</li>
<li>The capacity of your relationship acquisition process.</li>
</ul>
<p>The calculation of your optimal relationship acquisition cost requires a little more thought.</p>
<p>The amount that you are prepared to spend in order to acquire a new relationship must obviously relate to the value of such a relationship.</p>
<p>But how can you value one more name on your database?</p>
<p>The solution is to value relationships using exactly the same methodology we used to value clients.</p>
<p>Your database of subscribers provides you with a flow of sales opportunities.</p>
<p>You can value a sales opportunity by discounting your optimal client acquisition cost for your conversion rate. (In other words, if your conversion rate is 10%, a sales opportunity is worth 10% of your optimal client acquisition cost.)</p>
<p>Accordingly, to value one new subscriber, all you have to do is calculate the odds of that subscriber becoming a client over the life of their relationship with you.</p>
<p>While you can easily calculate the life of a client relationship, it&rsquo;s a little harder to calculate the life of a subscriber. In our experience, it&rsquo;s rare for subscribers to unsubscribe from our automated communications program.</p>
<p>For this reason, we arbitrarily choose to value subscribers over the same lifespan as clients. Accordingly, if the life of an average client is three years, we value subscribers over this same period.</p>
<p>The CEO of Correlex is prepared to invest $900 to acquire a new client.</p>
<p>Because his optimal conversion rate is 25%, a sales opportunity is worth $225.</p>
<p>$900 x 25% = $225</p>
<p>He knows that his automated communication program provides him with an opportunity realisation rate of 0.8% per month. Or, to put it another way, for each subscriber on his database, he will receive 0.8% of a new sales opportunity each month.</p>
<p>Because he arbitrarily decides to value subscribers over a three-year period (36 months), Correlex&rsquo;s CEO can calculate that there is a 28.8% likelihood of a new subscriber turning into a client over this period.</p>
<p>0.8% x 36 = 28.8%</p>
<p>If 28.8% of subscribers become clients, it follows that a new subscriber is worth $64.80:</p>
<p>$225 x 28.8% = $64.80</p>
<p>Therefore, this $64.80 is Correlex&rsquo;s optimal relationship acquisition cost.</p>
<p>Correlex&rsquo;s CEO decides to set his optimal relationships acquisition rate at 85 per month. This will allow him to easily hit his target of 2,000 subscribers within 12 months. (Even accounting for a particularly conservative unsubscribe rate of 42 a month.)</p>
<p align="center"><img alt="" src="http://www.salesprocessengineering.net/wp-content/uploads/image/kpi4.gif" /></p>
]]></content:encoded>
			<wfw:commentRss>http://www.salesprocessengineering.net/2008/07/20/how-to-establish-a-clear-cause-and-effect-relationship-between-promotional-expenditure-and-sales/feed/</wfw:commentRss>
		<slash:comments>1</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:59:39 -->
