<?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; salespeople</title>
	<atom:link href="http://www.salesprocessengineering.net/tag/salespeople/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>A strategy for coping with tough economic times</title>
		<link>http://www.salesprocessengineering.net/2009/02/20/a-strategy-for-coping-with-tough-economic-times/</link>
		<comments>http://www.salesprocessengineering.net/2009/02/20/a-strategy-for-coping-with-tough-economic-times/#comments</comments>
		<pubDate>Fri, 20 Feb 2009 07:34:38 +0000</pubDate>
		<dc:creator>Justin Roff-Marsh</dc:creator>
				<category><![CDATA[Applying Sales Process Engineering]]></category>
		<category><![CDATA[Slaying Sacred Cows]]></category>
		<category><![CDATA[commission]]></category>
		<category><![CDATA[salespeople]]></category>

		<guid isPermaLink="false">http://www.salesprocessengineering.net/2009/02/20/a-strategy-for-coping-with-tough-economic-times/</guid>
		<description><![CDATA[A slow economy does not have to mean fewer orders As the economy slows, it&#8217;s likely that your firm&#8217;s order flow will slow too. But, does it really need to? For you to answer this question in the affirmative, two conditions need to be in place: Your share-of-market needs to be considerable Your sales function [...]]]></description>
			<content:encoded><![CDATA[<h3>A slow economy does not have to mean fewer orders</h3>
<p>As the economy slows, it&rsquo;s likely that your firm&rsquo;s order flow will slow too.</p>
<p>But, does it really need to?</p>
<p>For you to answer this question in the affirmative, two conditions need to be in place:</p>
<ol>
<li>Your share-of-market needs to be considerable</li>
<li>Your sales function needs to be operating at (or close to) optimal efficiency</li>
</ol>
<p>So, think about it.&nbsp;Do these conditions hold true for your organization?</p>
<p>I suspect not.&nbsp;It&rsquo;s likely that your marketshare is much less than 50%.&nbsp;And it&rsquo;s highly unlikely that your sales function is operating at anywhere near optimal efficiency.</p>
<p>To validate my second claim, have your sales manager examine your salespeople&rsquo;s calendars and determine the number of true business-development appointments performed by your salespeople last week (it should be 15-20 each).</p>
<p>If these conditions do not hold for your organization, the implication is exciting.&nbsp;In theory, at least, it will be possible for you to maintain your order flow in these tough times, provided that:</p>
<ol>
<li>You can improve the performance of your sales function to the point where you can secure enough new accounts to compensate for any contraction in sales</li>
<li>You can do this without increasing your marketshare to unrealistic levels</li>
</ol>
<h3>An action plan (five simple steps)</h3>
<p>With this encouraging thought in mind, let&rsquo;s consider an action plan for coping with these tough economic times.</p>
<p><b>Step one</b> is to estimate how many appointments (in aggregate) you believe it is possible to generate for your sales team each week.</p>
<p>Remember, that the number of appointments you can generate is primarily a function of the appeal of your market proposition.&nbsp;A client of ours in Kentucky just eliminated a problem with appointment-setting by writing to clients offering them $500&rsquo;s worth of free merchandise.&nbsp;This offer was commercially viable because the value of new accounts was high and because the firm had under-utilized fulfilment capacity.&nbsp;This appealing proposition caused the number of prospects who accepted appointments when offered to increase from less than 1:20 to more than 1:3!</p>
<p><b>Step two </b>is to determine the optimal size of your sales team.&nbsp;This is simply the number of appointments you can generate each week, divided by 20 (each salesperson&rsquo;s future capacity).</p>
<p><b>Step three </b>is to figure out how to remove all activities from salespeople, other than field-based, face-to-face, business-development appointments.</p>
<p>So, activities that must be re-routed elsewhere include opportunity generation (promotions), appointment setting and calendar management, solution-design and proposal generation, customer service and all fulfilment-related tasks.</p>
<p><b>Step four</b> is to reconfigure your resourcing model.&nbsp;It&rsquo;s likely that you will discover that you need far fewer salespeople (even considering your increased appointment numbers) and more sales-support personnel.</p>
<p>Our approach to resourcing is to provide each salesperson with a dedicated sales coordinator (who manages opportunities and plans his or her calendar) and then route all other activities to a promotions person, customer-service personnel and technical experts who provide salespeople with field support.</p>
<p>In most cases it is possible to accomplish this reconfiguration with a negligible (if any) increase in operating expenses.</p>
<p><b>Step five</b> is to eliminate bonuses and commissions.</p>
<p>If you&rsquo;ve been waiting for the right time to eliminate this caustic practice, a down economy is such an opportunity.</p>
<p>While performance pay makes sense in environments where salespeople are truly autonomous, these environments are few and far between.</p>
<p>As organizations transition to <i>make-to-order </i>(or <i>engineer-to-order </i>environments), the requirement for tight integration between sales and fulfilment becomes critical.</p>
<p>Tight integration necessitates team work, and performance pay for individuals destroys the integrity of teams.</p>
<p>Furthermore, performance pay:</p>
<ol>
<li>Signals that optimal performance is optional</li>
<li>Causes your sales function to become more costly as it operates more efficiently</li>
</ol>
<h3>The bottom line</h3>
<p>Typically, when we implement these five steps in organizations, we increase each salesperson&rsquo;s activity level by 10 times.&nbsp;However, in most cases, we also reduce the size of the sales team.</p>
<p>A typical net result would be twice the volume of true business-development appointments, with minimal change in operating expenses.</p>
<p>If your current marketshare provides you with room for growth, this is a strategy worth considering in these slower times.</p>
<p style="margin-left: 40px">We recently published a document detailing three common scenarios: the application of SPE to different sized firms and it&#8217;s implications for sales activity and operating expenses.&nbsp; If you don&#8217;t currently have a copy of this document, send me an e-mail (<a href="mailto:justin.roffmarsh@ballistix.com">justin.roffmarsh@ballistix.com</a>) with &quot;Scenarios&quot; in the subject line.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.salesprocessengineering.net/2009/02/20/a-strategy-for-coping-with-tough-economic-times/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Performance pay: the case against</title>
		<link>http://www.salesprocessengineering.net/2008/07/07/performance-pay-the-case-against/</link>
		<comments>http://www.salesprocessengineering.net/2008/07/07/performance-pay-the-case-against/#comments</comments>
		<pubDate>Tue, 08 Jul 2008 06:59:03 +0000</pubDate>
		<dc:creator></dc:creator>
				<category><![CDATA[Measures and General Management]]></category>
		<category><![CDATA[commission]]></category>
		<category><![CDATA[measurement]]></category>
		<category><![CDATA[salespeople]]></category>

		<guid isPermaLink="false">http://www.salesprocessengineering.net/2008/07/07/performance-pay-the-case-against/</guid>
		<description><![CDATA[Few suggestions inflame passions faster than the suggestion that performance pay be abolished. It&#8217;s our contention, nonetheless, that, in an ideal environment, commissions and bonuses are likely to be in conflict with the goal of the organisation. Of course, traditional sales processes are not &#8217;ideal environments&#8217; and, as such, the traditional sales process serves as [...]]]></description>
			<content:encoded><![CDATA[<p>Few suggestions inflame passions faster than the suggestion that performance pay be abolished. It&rsquo;s our contention, nonetheless, that, in an ideal environment, commissions and bonuses are likely to be in conflict with the goal of the organisation. Of course, traditional sales processes are not &rsquo;ideal environments&rsquo; and, as such, the traditional sales process serves as an illustration of the conditions under which performance pay is, in fact, appropriate! Let&rsquo;s begin, accordingly, with the case forperformance pay.</p>
<h3>The case for performance pay</h3>
<p>Let&rsquo;s envisage a situation where performance pay definitely makes sense. The situation that springsto mind immediately is outsourcing &mdash; or more generally &mdash; the use of contractors. If you have outsourced a task to a contractor, it makes sense to compensate that contractor on a per-piece (or results) basis. Because you are outsourcing, you have no control over the contractor&rsquo;s production process (you can consider only inputsand outputs) and, as a consequence, it doesn&rsquo;t make sense for you to gamble on something over which you have no control. Most organisations understand this explicitly.&nbsp; This is why most contractors (including service providers) are under pressure to quote on a fixed-price &mdash; rather than a time-and-materials &mdash; basis. Now, if you consider the structure of a typical sales process (as discussed in the preceding article), you&rsquo;ll realise that the relationship between the salesperson and the organisation is more similar to a contractor-clientthan it is to an employer-employee relationship:</p>
<ol>
<li>Salespeople are responsible for the end-to-end sales process.</li>
<li>Management has limited (if any) access to objective process data.</li>
<li>Salespeople perceive that they own customer relationships (and in many cases they do!)</li>
</ol>
<p>In this environment, it certainly does make sense to pay salespeople as you would a contractor. But, as you well know, we maintain that this isnot an ideal environment. What we now have to consider is how the radically different environment we advocate impacts on the case for performance pay.</p>
<h3>The ideal environment</h3>
<p>In summary, the essential differences between a typical sales process, and the process we advocate are as follows:</p>
<ol>
<li>&nbsp;Salespeople are responsible only for the conduct of (sales) appointments.</li>
<li>All other tasks (including the sequencing of salespeople&rsquo;s appointments) are allocated to a sales support function.</li>
<li>Sales process management decisions are subordinated to the organisation&rsquo;s constraint.</li>
</ol>
<p>If you consider the first two points above, it&rsquo;s obvious that we are no longer outsourcing the sales process, in its totality, to the salesperson. In fact, we have simplified the role of the salesperson to the point where he performs only one task (appointments*).&nbsp; As well as increasing (massively) the productivity of the salesperson, the elimination of multitasking provides management with the ability to micro-manage the salesperson. The thing is, if a salesperson performs one simple task, over and over, management now has access to a statistically relevant quantity of objective data. This data-stream is the critical feedback loop that enables a process of continual improvement. Now that the salesperson can be measured and managed intelligently, the case for performance pay is no stronger for the salesperson than it is for any (and every) other employee. Which, of course, raises a very interesting question: wouldn&rsquo;t it make sense to provide every employee with performance-based compensation? Our consideration of point three (above) exposes the first of two fatal flaws in this common argument.</p>
<h3>Fatal flaw one: the optimum is rarely the maximum</h3>
<p>If you consider most performance-based compensation programs, their operation is simple.&nbsp; Employees&rsquo; pay is linked (directly or indirectly) to their productivity. Accordingly, the harder an employee works, the more he earns. This approach assumes that incremental increases in employee productivity are necessarily good for the organisation. Sadly, this assumption is dead wrong.&nbsp; The fact is, in any process, incremental productivity improvements in only one resource will impact on that process&rsquo;s output.&nbsp; (This critical resource is the process constraint.) Productivity improvements elsewhere will have either no positive impact, or even a negative impact, on process output.&nbsp; (I&rsquo;m referring now to non-constrained resources.) Consider a simple organisational process consisting of the following sequence of activities (each performed by a separate resource):</p>
<ol>
<li>Promotion (the generation of sales opportunities).</li>
<li>Sales (the conversion of sales opportunities to orders).</li>
<li>Fulfilment (the fulfilment of these orders).</li>
</ol>
<p>If you were managing this fictitious organisation, would you be likely to exhort the people responsible for these resources to produce at their maximum possible rates? I hope not! Presumably you&rsquo;d recognise that there is no benefit in Promotion producing sales opportunities that Sales can&rsquo;t process.&nbsp; And, similarly, there&rsquo;s no benefit in Sales generating orders that Fulfilment can&rsquo;t fulfil. To provide each of these individuals with a financial incentive to produce at maximum (individual) capacity will waste resources, unnecessarily inflate expenses, generate chaos and damage customer service. It&rsquo;s for this reason that the third attribute of an ideal environment (above) is that sales process management decisions are subordinated to the organisation&rsquo;s constraint. What this means is that the output of the various resources within our process should be synchronised with the maximum sustainable capacity of the process constraint. Performance pay is likely to have the exact opposite effect.</p>
<h3>Linking global rewards to global objectives</h3>
<p>Now, if you think about it, the flawed assumption that incremental increases in employee productivity are necessarily good for the organisation does not have to ring the death knoll for performance pay. It&rsquo;s possible to envisage a compensation program that links local rewards to global optima. For example, you could:</p>
<ol>
<li>Only reward team members at the process constraint for incremental increases in output.</li>
<li>Compensate team members at non-constrained resources for maintaining optimal (rather than maximal) output.</li>
</ol>
<p>Now, this (smarter) approach to performance pay overcomes the sub-optimisation* problem.&nbsp; It does, however, introduce two questionable assumptions of its own &mdash; and it fails to address the second fatal flaw in the argument for performance pay! Let&rsquo;s consider the two assumptions first. The first is that the process constraint will stay in the one location.&nbsp; If it moves (and from time to time it will), it will be necessary to reconfigure your compensation program.&nbsp; You will inevitably find yourself having to explain to team members at the prior constraint that they must now satisfy themselves with a lower rate of pay (this is particularly challenging when the team members involved are salespeople!). The second assumption is that it is beneficial for team members at the constraint to strive for maximum output.&nbsp; The reality is that what you want is not maximum output but maximum sustainable output.&nbsp; While it sounds like a heroic endeavour, the pursuit of &rsquo;stretch goals&rsquo; increases volatility and decreases average output.* It&rsquo;s time now to unveil performance pay&rsquo;s mostinsidious flaw: the assumption that pay drives performance.</p>
<h3>Fatal flaw two: pay does not drive performance</h3>
<p>At first glance, the assumption that people will work harder in the pursuit of a greater income looks innocent enough. After all, a donkey will chase a carrot, won&rsquo;t he? Well he will, until he&rsquo;s replete!&nbsp; From that point on, the donkey has no interest in the carrot whatsoever. In our experience, team members&rsquo; desire for additional money subsides rapidly once they are earning what they believe to be a fair market rate (assuming, of course, that their basic needs are met by that level of income). Furthermore, team members value the security of a fixed income more than they value the possibility of a higher (variable) income. But &mdash; and I&rsquo;m asked this question often &mdash; don&rsquo;t we want our employees to be entrepreneurial? The answer is &rsquo;no&rsquo;.&nbsp; We don&rsquo;t.&nbsp; As suggested previously, we will destroy our organisations if we turn them into a loose cooperative of contractors &mdash; all taking risks in the pursuit of a profit (this is, after all, the definition of &rsquo;entrepreneur&rsquo;). We want our organisations to be tightly synchronised, highly efficient and totally predictable.&nbsp; The donkey-and-carrot method of compensation is totally at odds with this objective.</p>
<h3>Market rate plus some</h3>
<p>Now I&rsquo;m not suggesting that the elimination of commissions should result in a drop in your team members&rsquo; average rates of pay. In fact, I would expect the opposite to occur in many cases. But I am prepared to suggest that, along with performance pay, we should eliminate the notion that performance and pay should be directly linked. A better method to apply to the calculation of salary is to estimate the replacement cost of an employee. This replacement cost should consist of the market rate for a person of comparable capability, plus a premium for the inevitable switching cost you would incur if you were to lose that team member. You&rsquo;ll find that this method provides a simpler and more rational basis for setting and renegotiating salaries.&nbsp; Obviously this method will result in an indirect link between productivity and salary (more productive employees will have a higher replacement cost). You&rsquo;ll also find that the offer of a good fixed salary (in place of the promise of untold riches) will result in a greater number of better quality respondents to your employment advertisements; particularly when you are recruiting salespeople!</p>
<h3>A caveat</h3>
<p>It&rsquo;s important to highlight that the elimination of performance pay is contingent upon the successful reengineering of the sales process. If your sales process (or any other process) is intelligently designed and objectively managed, the retirement of performance pay is likely to be a logical and painless eventuality. An attempt to reengineer a traditional sales process that begins with the&nbsp; heavy-handed suspension of performance pay is likely to have unpleasant consequences.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.salesprocessengineering.net/2008/07/07/performance-pay-the-case-against/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Is your salesperson really selling?</title>
		<link>http://www.salesprocessengineering.net/2008/07/07/is-your-salesperson-really-selling/</link>
		<comments>http://www.salesprocessengineering.net/2008/07/07/is-your-salesperson-really-selling/#comments</comments>
		<pubDate>Tue, 08 Jul 2008 06:39:58 +0000</pubDate>
		<dc:creator></dc:creator>
				<category><![CDATA[Measures and General Management]]></category>
		<category><![CDATA[measurement]]></category>
		<category><![CDATA[sales]]></category>
		<category><![CDATA[salespeople]]></category>

		<guid isPermaLink="false">http://www.salesprocessengineering.net/2008/07/07/is-your-salesperson-really-selling/</guid>
		<description><![CDATA[If you have a salesperson, I challenge you to try this simple &#8216;time and motion&#8217; study. Follow her around for a week and take note of the different activities in which she engages &#8211; and the percentage of her working hours that are devoted to each. My guess is that you&#8217;ll discover something like the [...]]]></description>
			<content:encoded><![CDATA[<p>If you have a salesperson, I challenge you to try this simple &lsquo;time and motion&rsquo; study. Follow her around for a week and take note of the different activities in which she engages &ndash; and the percentage of her working hours that are devoted to each. My guess is that you&rsquo;ll discover something like the following:</p>
<ol>
<li>Sixty percent of her time is spent prospecting (looking for someone to sell to).</li>
<li>Thirty percent of her time is spent face-to-face with qualified prospects (actually selling).</li>
<li>And 10% of her time is spent servicing existing accounts (looking after people to whom she has already sold).</li>
</ol>
<p>Now, ask yourself a question: is your salesperson investing her time in the most effective manner? To answer that question, let&rsquo;s examine each of the activities in which she engages, starting with &lsquo;servicing existing accounts&rsquo;. In my experience, using salespeople to perform customer service duties is a little like trying to kill a butterfly with a hammer: you waste resources, and make a hell of a mess in the process! The fact is, the best salespeople tend not to be great at customer service &ndash; and visa versa. Better to give your customer service duties to a full-time, telephone-based customer service person who&rsquo;ll do the job properly, for around half the salary. Your salesperson can now divide the time she saves between prospecting (now approximately 70% of her available time) and selling (now 30%). Let&rsquo;s take a look now at prospecting &ndash; is this activity really an effective use of your salesperson&rsquo;s time? If you&rsquo;re paying your salesperson $70,000 a year, and this person has 20 timeslots a week that she could theoretically fill with appointments, 14 of these slots are currently being spent looking for people to sell to in the remaining six! Or, to put it another way, each appointment is costing you (in salary alone) $243, instead of the $73 you&rsquo;d be paying per appointment if all of the available slots were filled. Is this so bad?</p>
<h3>The answer&rsquo;s no &hellip; and yes!</h3>
<p>No, it&rsquo;s not unrealistic to invest $243 to set an appointment for a $70,000 a year salesperson. But this calculation doesn&rsquo;t take &lsquo;opportunity cost&rsquo; into account. In other words, what&rsquo;s it costing in lost sales revenue to have your salesperson perform only six out of a possible 20 appointments? Let&rsquo;s assume that a typical customer is worth $10,000 to you (lifetime value) &ndash; and that your salesperson successfully &lsquo;closes&rsquo; one sale for each six appointments. Right now, your salesperson is performing six appointments a week &ndash; which equates to one sale, worth $10,000 (or $1,670 revenue per appointment). If you can find another way to invest that available $243 per appointment, such that each of your salesperson&rsquo;s 20 available timeslots is filled, your salesperson will now be performing an additional 14 appointments &ndash; lifting revenues to $33,400 a week. (That should just about cover your customer service person&rsquo;s salary!) Therefore, the &lsquo;opportunity cost&rsquo; of having your salesperson do her own prospecting is a massive $23,400 a week!</p>
<h3>But that&rsquo;s not the half of it!</h3>
<p>If your salesperson is no longer setting her own appointments, who is? And what&rsquo;s the likely impact on her closing ratio? Let&rsquo;s assume that you were to use advertising to generate inquiries &ndash; you&rsquo;ll find examples of lead-generation advertisements in this (and previous) editions of AdVerb. And let&rsquo;s assume that you give your new customer service person the job of setting appointments for your salesperson. Our experience is that responses to a lead-generation advertisement placed in a metropolitan newspaper are likely to cost you somewhere in the region of $30 each. If your customer service person appoints one in five, each appointment will cost you $150. So will your salesperson&rsquo;s closing rate suffer if her appointments are set for her? In our experience, no. The fact is, salespeople&rsquo;s closing rates typically more than double when appointments are set with respondents to a lead-generation campaign. And there&rsquo;s a simple reason why: those prospects who set appointments after responding to an advertisement &ndash; and then reading an information pack (usually the offer in a lead-generation advertisement) &ndash; are significantly better qualified than those appointed by a salesperson using traditional prospecting methods. If we assume that your salesperson&rsquo;s closing rate increases by only 50%, she is now making five sales a week, worth a total of $50,000. So let&rsquo;s take a look at what we&rsquo;ve achieved with our little hypothetical &lsquo;re-engineering&rsquo; exercise. Well, we&rsquo;ve increased your costs. A good telephone-based customer service person will cost around $35,000 a year. And your lead-generation campaign will cost you $150 per appointment. (Accordingly, your costs have risen by around $3,700 a week.) But we&rsquo;ve also increased your revenues &ndash; from $10,000 a week, to $50,000 a week. There are 40,000 good reasons to grab a notebook and a calculator &ndash; and spend a week spying on your salesperson (with her permission, of course)!</p>
]]></content:encoded>
			<wfw:commentRss>http://www.salesprocessengineering.net/2008/07/07/is-your-salesperson-really-selling/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Salespeople must sell!</title>
		<link>http://www.salesprocessengineering.net/2008/07/07/salespeople-must-sell/</link>
		<comments>http://www.salesprocessengineering.net/2008/07/07/salespeople-must-sell/#comments</comments>
		<pubDate>Tue, 08 Jul 2008 06:23:25 +0000</pubDate>
		<dc:creator></dc:creator>
				<category><![CDATA[Measures and General Management]]></category>
		<category><![CDATA[measurement]]></category>
		<category><![CDATA[opportunity management]]></category>
		<category><![CDATA[salespeople]]></category>

		<guid isPermaLink="false">http://www.salesprocessengineering.net/2008/07/07/salespeople-must-sell/</guid>
		<description><![CDATA[In a process built along the lines we advocate it is critical that salespeople pursue a &#8216;sale&#8217; at each business-development appointment. Now this sale may not be the achievement of the ultimate objective.&#160; In many cases it&#8217;s just permission to move to the next step in the (standardised) opportunity-management process. It may be that salespeople [...]]]></description>
			<content:encoded><![CDATA[<p>In a process built along the lines we advocate it is critical that salespeople pursue a &#8216;sale&#8217; at each business-development appointment. Now this sale may not be the achievement of the ultimate objective.&nbsp; In many cases it&#8217;s just permission to move to the next step in the (standardised) opportunity-management process. It may be that salespeople are conducting an initial appointment and selling the next step &#8212; an executive briefing.&nbsp; Or, in some cases, salespeople might choose to skip a step and convince the potential client to (say) request a proposal. But in either case, salespeople *must* sell.&nbsp; They must &#8216;ask for the sale&#8217;, where the sale may be the ultimate &#8212; or an intermediate &#8212; objective. Now, in a typical sales process, this tends not to happen.&nbsp; The opportunity-management process is an unstructured, ongoing dialogue. Obviously, this is sub-optimal, even in a typical sales process.&nbsp; But in a process designed around our principles, it&#8217;s a disaster! Remember, we&#8217;ve applied division of labour.&nbsp; This means that the selling must be performed by salespeople, and only salespeople. If salespeople, in the previous example, have sold an Executive Briefing, sales coordinators will call to schedule it &#8212; and only to schedule it (not to sell it). This means that the selling must have been done and done properly so that sales coordinators can focus on their job: which is scheduling. A common concern of management with respect to our method is that sales coordinators will not be capable salespeople.&nbsp; Well, management is right, they won&#8217;t. And they shouldn&#8217;t need to be. If you find that your sales coordinators need to sell, you need to confirm that (a) your opportunity management process consists of a sequence of discreet (concrete) steps and (b) that your salespeople really are selling.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.salesprocessengineering.net/2008/07/07/salespeople-must-sell/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Client retention: whose responsibility?</title>
		<link>http://www.salesprocessengineering.net/2008/07/07/client-retention-whose-responsibility/</link>
		<comments>http://www.salesprocessengineering.net/2008/07/07/client-retention-whose-responsibility/#comments</comments>
		<pubDate>Mon, 07 Jul 2008 07:02:51 +0000</pubDate>
		<dc:creator></dc:creator>
				<category><![CDATA[Measures and General Management]]></category>
		<category><![CDATA[flawed logic]]></category>
		<category><![CDATA[sales process]]></category>
		<category><![CDATA[salespeople]]></category>

		<guid isPermaLink="false">http://www.salesprocessengineering.net/2008/07/07/client-retention-whose-responsibility/</guid>
		<description><![CDATA[Whose responsibility, I wonder, is client retention? Most organisations believe it&#8217;s the salesperson&#8217;s. Consequently, many salespeople spend a disproportionate amount of their time on account management. &#8216;Account management&#8217; is a polite way of referring to a process that involves driving from client to client, drinking coffee and talking about the football. In the US, they [...]]]></description>
			<content:encoded><![CDATA[<p>Whose responsibility, I wonder, is client retention? Most organisations believe it&#8217;s the salesperson&#8217;s. Consequently, many salespeople spend a disproportionate amount of their time on account management. &#8216;Account management&#8217; is a polite way of referring to a process that involves driving from client to client, drinking coffee and talking about the football. In the US, they refer to this process as the &#8216;doughnut run&#8217;. But then, in the US, there are Crispy Creme stores in every major town! We have a hunch that account management is not an incredibly valuable activity because, periodically, a salesperson takes a vacation. When this happens the salesperson&#8217;s clients tend to keep spending. It&#8217;s amazing that salespeople can exert this degree of control over their clients even when they&#8217;re on vacation! Our take on client retention is that it&#8217;s not a sales function. The responsibility for client retention should vest with:</p>
<ol>
<li>Operations: whose job it is to maintain a frictionless client interface</li>
<li>New product development: whose job it is to maintain a steady stream of innovations and maintain the desirability of the service</li>
</ol>
<p>Accordingly, we tend to take account management away from salespeople and give it to an internal (phone-based) customer service team. This provides two benefits:</p>
<ol>
<li>We can increase, significantly, the frequency of customer contact (for the same payroll cost).</li>
<li>Because the customer service team members are sitting at a computer, they are in the position to discuss work-in-process and process additional transactions for clients on the spot. (In other words, they can provide some value.)</li>
</ol>
<p>Now, there&#8217;s a third (indirect) benefit: we can allocate the time saved in salespeople&#8217;s schedules to business-development appointments. But there&#8217;s an interesting twist here. In focusing on business development, salespeople do actually end up making a contribution to client retention &#8212; a far more meaningful contribution than they make with their traditional account management activities. By selling existing clients additional services, salespeople increase the value of the relationship to both parties and, as a consequence, increase the client&#8217;s switching cost. So, it transpires that salespeople *can* make a contribution to client retention &#8212; not by doing the job of operations &#8212; but by doing their own job, and selling existing clients more and more services.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.salesprocessengineering.net/2008/07/07/client-retention-whose-responsibility/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Why sales training can decrease conversion rates!</title>
		<link>http://www.salesprocessengineering.net/2008/07/06/why-sales-training-can-decrease-conversion-rates/</link>
		<comments>http://www.salesprocessengineering.net/2008/07/06/why-sales-training-can-decrease-conversion-rates/#comments</comments>
		<pubDate>Mon, 07 Jul 2008 06:58:15 +0000</pubDate>
		<dc:creator></dc:creator>
				<category><![CDATA[Slaying Sacred Cows]]></category>
		<category><![CDATA[constraint]]></category>
		<category><![CDATA[measurement]]></category>
		<category><![CDATA[qualification]]></category>
		<category><![CDATA[salespeople]]></category>
		<category><![CDATA[throughput]]></category>

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

		<guid isPermaLink="false">http://www.salesprocessengineering.net/2008/07/06/are-your-salespeople-really-delivering-spectacular-customer-service/</guid>
		<description><![CDATA[I heard an amusing story the other day. I was talking to the Managing Director of a large manufacturing firm, with a force of 100+ salespeople. He told me about how he recently went on a sales call with one of these salespeople. After the appointment, the two of them returned to the salesperson&#8217;s car. [...]]]></description>
			<content:encoded><![CDATA[<p>I heard an amusing story the other day. I was talking to the Managing Director of a large manufacturing firm, with a force of 100+ salespeople. He told me about how he recently went on a sales call with one of these salespeople. After the appointment, the two of them returned to the salesperson&#8217;s car. The salesperson drove out of the prospect&#8217;s driveway and parked his car around the corner. He then switched his mobile phone on and proceeded to take note of his voicemail messages: 27, in all! Many of these messages required the salesperson to do research (check on the status of a customer&#8217;s job, for example) and then return the callers&#8217; messages. The salesperson spent 20 minutes sitting in his car, in the sun, actioning these messages. The Managing Director related that he had to ask the salesperson to move his car into the shade: he was in danger of suffering from heat stroke! Now consider two party&#8217;s perspectives on this story: the salesperson&#8217;s and a typical customer&#8217;s. The salesperson perspective is that he is productive, efficient, hard working and engaged in the delivery of spectacular customer service. He is, after all, bending over backwards to service his clients&#8217; not-inconsiderable expectations. Now consider a typical customer&#8217;s perspective. Does the customer perceive that the organisation (for which the salesperson works) is delivering spectacular service? Whenever the customer has a problem or a question he has to phone a salesperson. The salesperson is rarely available which means he has to leave a message. Many times when the salesperson returns his call, the salesperson isn&#8217;t in a position to answer even the most simple questions, which means he has to wait an hour or so for the salesperson to do the necessary research and get back to him. Amusing, hey? Well it is, unless it&#8217;s happening in your organisation! When we&#8217;re working with an organisation, we divert salespeople&#8217;s mobile phones to their sales coordinators and give salespeople new SIM cards. Customers are not advised of salespeople&#8217;s new phone numbers. Sales coordinators field incoming calls from customers and either schedule an appointment, schedule a tele-conference or route them to the internal account-management team. When orders are received, the internal account manager sends the customer an e-mail, advising the customer that she will be managing the job, quoting an estimated delivery time (ETA), promising to follow-up if the ETA changes, and urging the customer to contact her by e-mail (or phone, if urgent) when necessary. The consequences are that:</p>
<ol>
<li>The volume of &#8216;how is my job going&#8217; calls is dramatically reduced</li>
<li>Customers&#8217; call the assigned account manager directly with questions</li>
<li>In almost all cases, customers&#8217; questions get answered on the spot (or by return of e-mail)</li>
<li>Salespeople have more time to spend face-to-face with customers (and potential customers)</li>
<li>Customers actually feel that the organisation is more &#8211; not less &#8211; accessible!</li>
</ol>
<p>Now, that&#8217;s customer service.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.salesprocessengineering.net/2008/07/06/are-your-salespeople-really-delivering-spectacular-customer-service/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Why salespeople should NEVER perform telephone follow-up</title>
		<link>http://www.salesprocessengineering.net/2008/07/02/why-salespeople-should-never-perform-telephone-follow-up/</link>
		<comments>http://www.salesprocessengineering.net/2008/07/02/why-salespeople-should-never-perform-telephone-follow-up/#comments</comments>
		<pubDate>Thu, 03 Jul 2008 06:42:56 +0000</pubDate>
		<dc:creator></dc:creator>
				<category><![CDATA[Applying Sales Process Engineering]]></category>
		<category><![CDATA[sales process]]></category>
		<category><![CDATA[salespeople]]></category>

		<guid isPermaLink="false">http://www.salesprocessengineering.net/2008/07/02/why-salespeople-should-never-perform-telephone-follow-up/</guid>
		<description><![CDATA[When I insist that Sales Coordinators &#8212; and never Salespeople &#8212; should make follow-up calls, there&#8217;s always a howl of protest from Salespeople. &#34;What about the relationship?&#34; is the instinctive response, followed by, &#34;but Sales Coordinators don&#8217;t&#160;have technical skills &#8212; or sales skills&#34;. Of course we can immediately discount the instinctive response (Executives have PA&#8217;s [...]]]></description>
			<content:encoded><![CDATA[<p><font face="Verdana" size="2">When I insist that Sales Coordinators &#8212; and never Salespeople &#8212; should make follow-up calls, there&#8217;s always a howl of protest from Salespeople.</font> <font face="Verdana" size="2">&quot;What about the relationship?&quot; is the instinctive response, followed by, &quot;but Sales Coordinators don&#8217;t&nbsp;have technical skills &#8212; or sales skills&quot;.</font> <font face="Verdana" size="2">Of course we can immediately discount the instinctive response (Executives have PA&#8217;s don&#8217;t they?), but it *is* worth considering the implications of a non-technical, non-salesperson performing follow-up calls.</font> <font face="Verdana" size="2">Obviously, if the salesperson&#8217;s assistant performs all follow-up calls, the content of these calls cannot be of a technical or sales nature.</font> <font face="Verdana" size="2">And that&#8217;s a very good thing!</font> <font face="Verdana" size="2">To understand why, consider why we&#8217;re making a follow-up call.</font> <font face="Verdana" size="2">The purpose of a follow-up call is simply to schedule (and sometimes to confirm) the next activity in the opportunity-management process.</font> <font face="Verdana" size="2">The call is not &#8212; and should never be &#8212; a sales call.&nbsp; The thing is, if you have (field-based) salespeople, we must assume that your product can&#8217;t (or shouldn&#8217;t) be sold on the phone.&nbsp; (If you can sell on the phone, get rid of your field-based salespeople and do just that.)</font> <font face="Verdana" size="2">Accordingly, we want to quarantine salesmanship (and technical discussions) in face-to-face meetings where they belong.&nbsp; If we fail to do this, there&#8217;s a very real danger that the opportunity-management process will devolve into an ongoing conversation!</font> <font face="Verdana" size="2">Now, consider what happens to the salesperson when she knows that her sales coordinator will make all follow-up calls.&nbsp; This forces her to ensure that she has closure at the end of each meeting.</font> <font face="Verdana" size="2">In practice, this means that she must get her client to agree to one of the three possible outcomes from each meeting (to proceed to the next activity in the opportunity management process, to repeat the current activity, or to abandon the opportunity).</font> <font face="Verdana" size="2">This means that the purpose of the follow-up call is simply to schedule this next activity.</font> <font face="Verdana" size="2">On occasion it will be necessary for the Sales Coordinator to confirm the next step in the opportunity-management process.&nbsp; (This might be because the prospect has to confer with another person before committing to the next step.)&nbsp; In this case, it is the responsibility of the salesperson to explain the various options open to the prospect and advise him that purpose of the Sales Coordinator&#8217;s follow-up call will simply be to confirm the appropriate option and then schedule it.</font> <font face="Verdana" size="2">This ensures that the Sales Coordinator maintains control over the opportunity-management process and is, of course, in keeping with our primary sales management objective: to maximise opportunity flow.</font></p>
]]></content:encoded>
			<wfw:commentRss>http://www.salesprocessengineering.net/2008/07/02/why-salespeople-should-never-perform-telephone-follow-up/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Sometimes salespeople SHOULD be autonomous agents!</title>
		<link>http://www.salesprocessengineering.net/2008/07/02/sometimes-salespeople-should-be-autonomous-agents/</link>
		<comments>http://www.salesprocessengineering.net/2008/07/02/sometimes-salespeople-should-be-autonomous-agents/#comments</comments>
		<pubDate>Thu, 03 Jul 2008 06:42:02 +0000</pubDate>
		<dc:creator></dc:creator>
				<category><![CDATA[Applying Sales Process Engineering]]></category>
		<category><![CDATA[sales process]]></category>
		<category><![CDATA[salespeople]]></category>

		<guid isPermaLink="false">http://www.salesprocessengineering.net/2008/07/02/sometimes-salespeople-should-be-autonomous-agents/</guid>
		<description><![CDATA[I guess I don&#8217;t really mind that people generally regard me as being opposed to salesperson autonomy (and, of course, performance pay). Antagonism is certainly more newsworthy than conformity! However, my position is not quite this simple, and a deeper understanding of the basic principle at stake here is more useful than the sound bite. [...]]]></description>
			<content:encoded><![CDATA[<p>I guess I don&#8217;t really mind that people generally regard me as being opposed to salesperson autonomy (and, of course, performance pay). Antagonism is certainly more newsworthy than conformity! However, my position is not quite this simple, and a deeper understanding of the basic principle at stake here is more useful than the sound bite. If you&#8217;ve viewed our multi-media presentation or read our whitepaper (you can get both free on our website), you&#8217;ll remember I present a simple cloud (conflict diagram). I suggest that managers typically equivocate between two approaches to the engagement of salespeople. On the one hand, management wants salespeople to be autonomous agents (think, sub-contractors). On the other, management wants salespeople to be team members (traditional employees). I argue that these two approaches are mutually exclusive: in reality a person marches to the beat of his own drum OR subordinates to the team&#8217;s drumbeat. I also argue that the case for autonomy is not as strong as is commonly assumed &#8212; providing management with the option to engage salespeople as true team members. Now the operative word here is &#8216;option&#8217;. My argument is not that autonomy &#8212; and everything that goes with it (including performance pay) &#8212; is necessarily bad. Rather, I argue that, what is destructive is management&#8217;s attempt to equivocate between two mutually-exclusive alternatives. (More on the consequences of equivocation in a moment.)</p>
<h3>The case for autonomy</h3>
<p>Imagine that you are an executive at Hewlett Packard. You have two divisions, one manufactures inexpensive computers for domestic customers (moms and dads). The other division engineers custom solutions for enterprise customers. Think about how you distribute your inexpensive computers. Do you have salespeople knocking on doors in the suburbs? Of course not, you distribute them via Harvey Norman (think, Circuit City if you&#8217;ve never heard of Harvey Norman). Now, Harvey Norman is an autonomous agent. They bring enormous value to the table for you: massive stores (and car parks), a captive audience, logistical capability and so on. Let&#8217;s call this value &#8216;infrastructure&#8217;. However, when we engage with Harvey Norman &#8212; an autonomous agent &#8212; we must sacrifice some of the benefits we&#8217;d enjoy if we managed sales internally. We can&#8217;t walk the floor at Harvey Norman and issue directives to sales clerks. It&#8217;s also unlikely that we can collect data at the most granular level like we can within our own organisation. So, there&#8217;s a trade off. And with less information and less control it&#8217;s inevitable that we will not be able to integrate (synchronise) production as tightly with our sales agent as we would if we owned the entire channel. And, as I hope you&#8217;ve already guessed, we compensate for this imperfect integration by maintaining inventory. In other words, we build domestic computers to replenish stock, as opposed to building to fulfil direct customer orders (like Dell does). As is always the case, poorer integration equals larger inventories. In this case (domestic computers) we&#8217;re quite comfortable with this trade-off. Ultimate sales are made by an autonomous agent &#8212; and we pay this agent on a piece-rate (performance pay) &#8212; and we&#8217;re better off, in-spite of the need to carry inventories.</p>
<h3>The case for team membership (integration)</h3>
<p>Let&#8217;s consider our other division. This division sells custom technology solutions to enterprise customers. These solutions &#8212; by virtue of their being custom &#8212; are engineered to order. You can see the problem already, can&#8217;t you? If these solutions are engineered to order, they cannot possibly be sold from inventory. If we can&#8217;t build inventories of stock to buffer imperfect integration between production and sales, then we&#8217;d better strive for perfect integration. Even though perfection is unachievable, it still shouldn&#8217;t be hard to see that there&#8217;s simply no comparison between the degree of integration we can achieve if we own the entire distribution channel as opposed to what&#8217;s possible when sales are handled by autonomous agents. In fact, it may well be that tight integration between sales and operations is the most effective way for you to gain advantage over your competitors. (If you operate in a pure engineer-to-order environment, please go back and read that sentence again!) So, in this case, it doesn&#8217;t make sense for sales to be outsourced to Harvey Norman or to any other variation on the &#8216;autonomous agent&#8217; theme. In this division (enterprise solutions), sales and production must both march to the beat of the one drum. However, when we take sales &#8216;in-house&#8217; we must recognise that we sacrifice the infrastructure that a Harvey Norman brings to the table. And, obviously, considering our market, we&#8217;re not particularly uncomfortable with this trade-off.</p>
<h3>Give and take</h3>
<p>In summary, then, when we distribute through autonomous agents we give up control but gain infrastructure. When we own the entire channel we give up infrastructure in favour of greater control.</p>
<h3>Equivocation</h3>
<p>I can almost hear you thinking, a typical salesperson is hardly comparable with a retail giant like Harvey Norman. And I&#8217;m glad you&#8217;re thinking that: it&#8217;s exactly my point! When we (management) equivocate between engaging salespeople as autonomous agents and team members, we end up with the worst of both worlds: limited control and negligible infrastructure. So, my position is not that salesperson autonomy is necessarily wrong. It&#8217;s that equivocation between autonomy and team membership is. You need to consider your organisation, and its market, and determine which approach to salesperson engagement is the more appropriate. After all, you can&#8217;t eat your cake and have it too.</p>
<h3>Clarification</h3>
<p>In many organisations it&#8217;s quite okay to have a mix of the two approaches within the one channel. For example, while it doesn&#8217;t make sense for the final link in Hewlett Packard&#8217;s distribution chain to be fully integrated, it&#8217;s likely that HP has a team of salespeople who call on Harvey Norman stores (channel managers). These channel managers should absolutely not be autonomous agents. Even though Harvey Norman is a good example, an autonomous sales agent can make sense even if they don&#8217;t bring quite the same scale to the table. For example, if we have a manufacturer client, we will often turn capital-city salespeople into true team members (as per our Sales Process Engineering model) and encourage our client to engage autonomous agents in regional areas &#8212; who may well be individuals who sell a range of non-competitive lines.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.salesprocessengineering.net/2008/07/02/sometimes-salespeople-should-be-autonomous-agents/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>How to deploy technical salespeople</title>
		<link>http://www.salesprocessengineering.net/2008/07/02/how-to-deploy-technical-salespeople/</link>
		<comments>http://www.salesprocessengineering.net/2008/07/02/how-to-deploy-technical-salespeople/#comments</comments>
		<pubDate>Thu, 03 Jul 2008 06:30:23 +0000</pubDate>
		<dc:creator></dc:creator>
				<category><![CDATA[Applying Sales Process Engineering]]></category>
		<category><![CDATA[sales process]]></category>
		<category><![CDATA[salespeople]]></category>

		<guid isPermaLink="false">http://www.salesprocessengineering.net/2008/07/02/how-to-deploy-technical-salespeople/</guid>
		<description><![CDATA[Often, when we work with organisations that sell technical products (especially in a make-to-order environment), we find that salespeople are technical experts. When you add the requirement for technical expertise into the normal (massively-multitasked) sales environment you inevitably find that salespeople are hard to find and difficult to train. Furthermore, the consequences of salespeople defecting [...]]]></description>
			<content:encoded><![CDATA[<p>Often, when we work with organisations that sell technical products (especially in a make-to-order environment), we find that salespeople are technical experts.</p>
<p>When you add the requirement for technical expertise into the normal (massively-multitasked) sales environment you inevitably find that salespeople are hard to find and difficult to train. Furthermore, the consequences of salespeople defecting to a competitor are severe.</p>
<p>Our approach to the deployment of technical salespeople is typically to pull them back from the front-line and have them provide technical support to front-line salespeople (we&#8217;ll either call them &#8216;technical experts&#8217; or &#8216;project managers&#8217;).</p>
<p>We like front-line salespeople (the ones performing 5 appointments a day, five days a week) to be generalists, not technical specialists. In other words their knowledge should be broad (across a range of products or service lines), not deep.</p>
<p>Once these salespeople have proposed a high-level solution, they can then introduce the technical experts to take a brief and design a solution. (See my recent post explaining why salespeople should not take briefs: <a href="http://finance.groups.yahoo.com/group/ballistix/message/79"><font color="#9136ad">http://finance.groups.yahoo.com/group/ballistix/message/79</font></a>).</p>
<p>This approach tends to suit both technical salespeople and their employers.</p>
<p>Technical salespeople would, in most cases, rather focus on solution design and project leadership.</p>
<p>And their employers benefit because this role produces a greater yield on technical salespeople&#8217;s skills, allows the payment of a higher salary and minimises the risk of defection.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.salesprocessengineering.net/2008/07/02/how-to-deploy-technical-salespeople/feed/</wfw:commentRss>
		<slash:comments>0</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:20 -->
