Why overselling backfires
A change case is the explanation of why something is being altered: why the old system is being replaced, why teams are being merged, why a function is moving to a central group. The temptation is to make it as attractive as possible. Every benefit is stated confidently, every cost is played down, and the whole thing is presented as obviously right.
The trouble is that the audience usually knows more about their own work than the authors of the case. If the message says a new tool will save time and people can see that the first month will be slower, they will conclude either that the authors do not understand the job or that they are not being straight. Either conclusion damages trust in everything that follows. An honest change case accepts a small loss of enthusiasm at the start in exchange for credibility later.
Start with the problem, not the solution
People respond better to a clear account of the problem than to a list of features. A useful case usually answers a few plain questions in this order:
- What is not working today, and for whom?
- How do we know? What has been observed, counted or reported?
- What is being proposed, in concrete terms?
- What will change in people’s day-to-day work?
- What will it cost, in money, effort and disruption?
- What is still uncertain?
If the answer to the second question is thin, say so. A performance baseline gathered before the change gives the case something firmer to stand on than opinion. Without one, wording such as “we believe” or “early indications suggest” is more accurate than a flat claim.
Separate what you know from what you hope
One of the most useful habits is to sort statements into three groups.
- Known: facts that can be checked, such as the contract ends on a certain date, or the current system is no longer supported by its supplier.
- Expected: outcomes that follow reasonably from the design but are not yet proven, such as fewer handoffs between teams.
- Hoped for: benefits that depend on other things going well, such as better morale or faster decisions.
Presenting the third group as if it belonged in the first is the commonest form of overselling. It is acceptable to state hopes, as long as they are labelled as hopes. Avoid precise figures for benefits unless they come from your own measurements; invented or borrowed numbers invite a challenge that the case cannot survive.
Be specific about costs
Costs are not only the purchase price. Total cost of ownership includes support, training, integration and the time people spend adjusting. For people, the cost is often a temporary drop in speed, new duties, loss of control over something they used to decide, or a change in who they report to.
Name these directly. A sentence such as “for the first few weeks, the new approval step will take longer than the current one” does more for trust than a paragraph of reassurance. If the cost falls unevenly, say who bears more of it. People generally accept that a change has winners and losers; they resent being told there are none when they can see otherwise.
Acknowledge the downsides of the approach itself
Centralizing a function or system has well-known trade-offs. It can create single points of failure, slow down decisions that used to be made locally, and reduce the ability to tailor a process for a local need. A credible case mentions the ones that are relevant and explains what will be done about them, or admits that they are accepted risks.
It is also fair to say what was considered and not chosen. If a hybrid arrangement or a lighter alternative was weighed, a sentence on why it was rejected shows that the decision was not made on a whim and gives people a way to test the reasoning.
State the uncertainties
Uncertainty is not a weakness in a change case; hiding it is. Typical open questions include timelines that depend on a supplier, roles whose final shape has not been decided, or effects on a team that cannot be known until a pilot is done. For each, it helps to say:
- what is not yet known,
- when it is expected to be known, and
- how people will be told.
“We do not yet know whether your team’s reporting line will change; a decision is expected by the end of next quarter and you will hear it from your manager first” is a more useful message than silence or a vague assurance. Promises that cannot be kept, such as “no one’s job will be affected”, should be avoided unless the decision-makers are genuinely able to guarantee them.
Make room for disagreement
An honest case is an invitation to respond, not a verdict. People may point to a flaw in the reasoning, a cost that was missed or a local need the design overlooked. Sometimes they will be right. Building a way to receive that input, and showing that it can change the plan, is part of the case itself. Otherwise the message reads as a decision dressed up as consultation, which tends to feed change resistance rather than reduce it.
It also helps to be clear about what is open and what is not. If the decision to proceed is made, say so, and invite input on how it is carried out. Pretending that everything is still negotiable when it is not creates its own disappointment.
Match the message to the audience
The same change looks different from different positions. Senior leaders may care about cost and risk, managers about workload and team structure, and frontline staff about how their tasks will change. A single document can hold the common facts, but the emphasis, examples and questions should be adjusted for each group. The groups can be identified in advance through stakeholder mapping, which also helps predict where the questions will come from.
A short checklist
Before releasing a change case, it can help to read it as a sceptical colleague would and ask:
- Does it describe the problem in terms the reader would recognise?
- Are the benefits labelled as known, expected or hoped for?
- Are the costs and the people who bear them named?
- Are the trade-offs of the chosen approach acknowledged?
- Are the open questions listed, with a date or route for answers?
- Is there a clear way to respond, and a clear statement of what can still change?
A case that passes these checks will not convince everyone, and it should not try to. Its job is to give people accurate material to form their own view, which is a firmer basis for cooperation than enthusiasm that does not last.