Your Sales Champion’s Favorite Argument Is a Problem for the People Doing the Work
Your Sales Champion’s Favorite Argument Is a Problem for the People Doing the Work
Somewhere in your deck there is a slide your champion reads twice. Champion and sponsor name the same person in this piece: the internal advocate whose benefit the argument is built around. It is the one that promises them the thing they have been missing: one view, one number, one less Monday spent assembling it by hand. It is the slide that gets you the second meeting.
It is also, often, the slide that quietly moves work onto somebody else.
Your champion is not lying to you, and you are probably not lying to them. The problem is structural. The person with the budget to say yes is rarely the person who has to do the tagging, the re-entering, the double-checking, and the explaining when a number does not match what they saw on the floor. If you have not yet separated the buyer, the sponsor, the user, and the affected person, that is the earlier job; it is a prerequisite for this one. Once the roles are distinct, the harder question arrives: what do you do when their interests genuinely conflict?
The fix is not to weaken the argument or open with an apology. It is to trace the favored benefit all the way into the workflow, find out whose hands it lands in, and then decide whether you are looking at a misunderstanding you can clear up or a tradeoff that has to be chosen. That changes what you propose, sometimes what you scope, and occasionally whether you proceed at all.
Follow the argument into the work it requires
Take the strongest sentence in the deck and treat it as a claim about labor.
Here is an invented scenario, constructed for this article rather than drawn from a documented case. A regional facilities-services company — call it Meridian, fictional, no relation to any real firm — runs maintenance crews across 40 sites. Its operations director wants a single dashboard: work orders, status, incidents, all sites, refreshed through the day. Today that director learns about a slipped job on a Monday call. With the dashboard, they would learn the same afternoon. That is a real benefit, and worth paying for.
The vendor’s tool builds that dashboard from structured data. It does not read free text. So every closed work order has to be tagged. In this version of the story, that means eleven fields: site, asset class, fault category, priority, outcome, and the rest. The free-text note a supervisor writes today becomes a form.
Who fills it in? Twelve field supervisors, each closing about 60 work orders a week. If tagging adds four minutes per order — a conservative figure once you count choosing the right category and going back for the one you skipped — that is four hours a week per supervisor. Region-wide, 48 hours a week: roughly 1.2 full-time positions of new work, absorbed by people who already have a demanding job.
Run that arithmetic on your own deck. Take the promise, find the data it needs, count the fields, and multiply by the volume and the people. The number you get is usually smaller than the story in the slide and larger than anyone in the room was expecting.
The sponsor’s benefit is real. The burden is real. Neither cancels the other, and a slide that shows only the first is not exactly wrong so much as blurred.
Then apply the discipline of labels. Keep proposed efficiencies marked as proposed. “Supervisors won’t have to write notes anymore” might be true, but only if the tags capture what the notes carried, which is precisely what nobody has tested. A note reading valve sticking again, third time this month, same as 4B carries pattern information that eleven dropdowns may or may not preserve. The concise champion slide is a summary of the argument, not evidence about the workflow. Do not let it assert a saving you have not measured.
What the people doing the work would need to confirm
You need an account of the work from the people who do it, not from the sponsor describing them.
This is where decks go lazy in a specific, repeatable way. The seller had one call with the operations director, who said the crews would not mind because they already write this stuff down. That is a sponsor’s reconstruction. It is not a supervisor’s account. They are not the same evidence, and treating them as interchangeable is how you end up surprised in week three.
What you are trying to find out is narrow and concrete:
- Does the work actually repeat? Are supervisors entering the same information twice because the new tool and the existing system do not share records?
- Does the change remove discretion? Today a supervisor decides what is worth writing down. A required field list moves that decision to whoever designed the form.
- Do handoffs change? If a job sits “incomplete” until tags are filled, the next crew may be waiting on paperwork rather than on the asset.
- What does the end of a shift look like now? New burden tends to land at the worst possible hour, which is also the hour nobody in the buying process has ever seen.
Label what you actually have. If you watched a supervisor tag orders in a demo you ran, that is direct observation of a demo. If the sponsor told you it would be fine, that is a hypothesis from an interested party. If you are inferring from the tool’s data model that eleven fields must be filled, that is a reconstruction. A reasonable one, and still a reconstruction.
The temptation is to fill the gap with a quote. Do not. A fabricated line from an unnamed field supervisor makes the deck feel grounded and makes it worthless; if the real supervisor later disagrees, you have spent your credibility on a sentence you wrote for them. There is genuine public guidance on the mechanics of getting findings in front of decision-makers — the GOV.UK Service Manual’s page on sharing user research findings, which addresses who to share findings with. It is a communication route, useful for the logistics of a stakeholder briefing. It does not adjudicate competing interests, and it does not hand you the field evidence you are missing here.
Clearing up a misunderstanding is not the same as resolving a tradeoff
Before you rewrite anything, run one test: would correcting a factual assumption make the concern go away?
Sometimes yes. A supervisor believes the tool will send their free-text notes to the client verbatim, and it does not. That is a misunderstanding, and a clear explanation plus a permission setting resolves it. Take that fix. It is cheap and real.
Sometimes no. If the dashboard genuinely requires eleven tags, no amount of better framing removes the four minutes. The concern is not confusion. It is arithmetic. Clearer messaging makes the cost better understood, which is not remotely the same as making it smaller.
The failure mode here is diagnosing the affected people instead of the design. They’re resistant to change. They don’t see the business case. We need to bring them along. Each of those reframes a distributional question as a comprehension problem, and each flatters the person saying it. The supervisors may understand the business case perfectly. They may understand it better than the deck does, because they can see exactly who benefits and who fills in the form.
Keep the benefit and the burden in the same sentence. Not faster regional visibility, with some change management needed, but same-day incident visibility for the director, paid for by roughly four hours of tagging per supervisor per week. Both halves are true. A sentence that holds both is the smallest honest unit in a sales deck, and you can build the rest of the deck out of them.
Change the implementation, or change the scope, and say what each gives up
Once the cost is established as real, you have more than one move. Two are worth comparing side by side, because they fail in different ways.
Change how the benefit is produced. Meridian’s director mainly wants to know what is open and where. Fault-category trend analysis is a nice-to-have that crept in later. So cut the required tags from eleven to four — site, asset class, priority, outcome — the minimum the core dashboard view needs. Tagging drops to about a minute and a half per order, under two hours a week per supervisor. The burden falls by roughly two-thirds.
What did the sponsor lose? Cross-site fault patterns. If a particular pump model keeps failing across the estate, the four-field version may never surface it, and that capability was part of why the dashboard was attractive in the first place. Reducing implementation cost is not free here. It deletes a feature the sponsor wanted, and the deck has to say so rather than quietly dropping it and hoping no one asks.
Change the scope of adoption. Roll out only where the burden is already being paid. Two of Meridian’s 40 sites already keep structured logs to satisfy a client contract, so those crews tag by habit. Pilot there and the added work is close to zero — which is exactly why the pilot tells the director almost nothing about the other 38 sites. And those 38 were the ones producing the Monday-morning surprises. Coverage falls from 40 sites to two, and the escalation benefit barely materializes.
Both routes keep the sponsor’s goal visible while changing what it costs and who pays. Neither is costless, and the comparison is the deliverable. A director choosing between narrower data and narrower coverage is making a real decision. A director told we’ll handle change management is not deciding anything.
Keep pausing on the table
Sometimes the honest answer is that the proposal should not move yet, and decks are notoriously bad at saying so. Two different things get tangled here, and separating them is most of the work.
A missing fact. Nobody knows whether the tags will preserve what the free-text notes carried. That is an empirical question with an empirical answer: run a two-week tagging trial at one site, compare the resulting dashboard against the notes, and look at what got lost. This is not a values dispute. It is a gap you can close.
An unresolved decision. Even with perfect information, someone has to decide whether 48 hours a week of supervisor time is a fair price for the director’s same-day visibility. That is not a fact. It is a question about whose priorities prevail, and it belongs to whoever actually has the authority to answer it — quite possibly not the sponsor alone. If the supervisors are covered by a works agreement that defines their duties, the answer may run through a route the sponsor does not control.
Notice what pausing is and is not. It is not a stakeholder failure, and it is not you being difficult. It is the accurate state of a proposal whose gain still depends on a burden that no one who bears it has accepted. Say what has to change for the proposal to proceed — a decision about who tags, a funded tagging role, a trimmed field list — and let the organization decide. That is a legitimate outcome of a sales process, not a loss, and treating it as one is how sellers end up overselling their way into an implementation disaster.
Put the conflict back in the same document
The revised proposal does not get split into two decks: a hopeful one for the champion and a muted one for everyone else. That is the old failure with better manners. Consistency is the whole point. The sponsor’s summary and the supervisors’ briefing should be recognizably the same argument.
In the Meridian case, the revised version might read:
Same-day visibility of open work orders across the sites included in the pilot, beginning with two sites that already capture structured data. Field tagging is reduced to four required fields, about ninety minutes per supervisor per week. Two questions remain open: whether that tagging time is funded or reassigned, and whether fault-pattern reporting, which the four-field version cannot support, is required for the business case to hold. Decision requested: [name] to confirm by [date].
That is about a champion slide’s worth of text. It is concise, it still gives the sponsor something to want, and every affected person who reads it would recognize their own situation inside it. It also names what is unsettled, which is the part that lets a champion walk into a room you are not in and not get ambushed.
A champion-ready argument is not simply the one that survives the buying committee. It is the one that survives contact with the people who have to live inside it. Trace the benefit to the work, find out whose hands it lands in, and then decide which version of the truth you are selling — because the organization is going to meet the other version eventually, with or without your deck.
Frequently asked questions
How can a champion's favorite dashboard argument create hidden work?
If the benefit depends on structured data, someone must supply it. In the invented Meridian case, a dashboard that cannot read free text requires eleven tags per closed work order. Twelve field supervisors closing about sixty orders a week, at four minutes per order, creates four hours per supervisor per week and about forty-eight hours region-wide, roughly 1.2 full-time positions of new work.
What evidence should come from the people doing the work?
An account from the supervisors themselves, not from the sponsor describing them. Ask whether work repeats, whether discretion is removed, whether handoffs change, and what the end of a shift looks like. Label what is direct observation, sponsor hypothesis, or reconstruction, and do not fabricate a quote to fill the gap.
How do you tell a misunderstanding from a tradeoff?
Ask whether correcting a factual assumption would make the concern go away. If a supervisor wrongly believes free-text notes will go to the client verbatim, a clear explanation and a permission setting can resolve it. If the dashboard genuinely requires eleven tags, clearer messaging only makes the cost better understood; it does not make it smaller.
What are the two main ways to change the proposal once the burden is real?
Change how the benefit is produced, such as cutting required tags from eleven to four, which lowers tagging to about ninety minutes per supervisor per week but loses cross-site fault-pattern reporting. Or change adoption scope, such as piloting at two sites that already keep structured logs, where added work is near zero but coverage falls from forty sites to two and the escalation benefit barely materializes.
When is pausing the proposal the honest move?
When the gain still depends on a burden no one who bears it has accepted. Separate a missing fact, which a trial can close, from an unresolved decision about whose priorities prevail, which belongs to whoever has authority. State what has to change, such as who tags, a funded tagging role, or a trimmed field list, and let the organization decide.