Practical Solutions
How can a transformation director choose an early win without committing to the wrong change?
Choose an early win for what it can reveal, not only for what it can display. The best first action is small enough to reverse, important enough to matter and designed to test an assumption that would otherwise remain hidden inside the transformation plan.
Illustrative business scenario—not a reported client result.
A transformation director has been given 30 days to show progress. The programme is intended to reduce service friction, but the diagnosis is still broad: teams say decisions are slow, customers report inconsistency and the executive team wants a visible sign that the change is underway. A large new process is ready to announce.
The director can see why it is tempting. It creates a story of momentum. But it also risks turning an untested explanation into a public promise. If the real constraint is decision rights, customer data or capacity, the new process may add work without addressing the bottleneck.
Urgency can turn a pilot into a promise
An early action always sends a signal. The moment a transformation director chooses a prominent initiative, people infer what will be rewarded, which diagnosis is believed and what the future operating model will look like. That is why an early win is not simply a communications device.
Karl Weick’s original discussion of “small wins” describes a small win as a concrete, complete and implemented outcome of moderate importance. He argues that such actions can make resources, barriers and opportunities more visible, while cautioning that the next useful step will not necessarily follow a neat, pre-plotted sequence. 1 The paper is a conceptual account, not proof that a particular pilot will improve business results. Its useful implication here is more limited: early action can be designed to generate information as well as visibility.
Why the familiar quick win can fail
The common fix is to pick the thing that can be announced fastest: a new dashboard, a simplified process map or a short-term target. These can be useful. The problem appears when “visible” becomes the selection rule.
A visible intervention can quietly commit the organisation to a diagnosis it has not tested. A new dashboard assumes the real issue is lack of information. A streamlined approval route assumes the issue is bureaucracy. A capability programme assumes the issue is skill. Each may be true. Each may also be a confident answer to the wrong question.
The existing Insight on the speed trap addresses the broader pressure to move fast in a new senior role. The question here is more specific: what kind of early movement protects the director’s ability to learn before the larger change takes shape?
Define the learning question first
Before selecting the win, write one question the action must answer. If the proposed action cannot produce a credible answer, it may be a communications activity rather than an early win.
For this scenario, the question might be: “Can a named cross-functional owner resolve the service exception without adding a new approval layer?” The question is precise enough to test and consequential enough to inform the programme.
Then design the action around three conditions:
- A limited boundary. Test it in one service journey, region or decision type rather than across the organisation.
- A clear owner and reversal point. State who will make the call, how long the test lasts and what would cause it to stop or change.
- An observation method. Capture the delay, the point at which decisions stall, the people who need to be involved and the work created elsewhere.
The result is not a miniature version of the whole transformation. It is a controlled way to expose an assumption.
Choose a win that preserves options
The stronger candidate is often less dramatic than the first idea. It deals with a real pain point, requires limited coordination and produces a result that can be read in more than one way.
The director in this scenario chooses a two-week exception-resolution pilot for one customer journey. A small cross-functional group is given authority to resolve defined cases within a stated boundary. They log the handoffs, information gaps and escalations. The director tells the organisation that the purpose is to understand the bottleneck and improve the next decision, not to declare the final service model.
Measure learning before scale
The potential payoff is momentum that preserves options. It may reduce avoidable waiting in the tested area, but it should not be presented as a guaranteed transformation outcome.
Track measures that reveal the mechanism: the number and type of handoffs; time from exception to decision; cases resolved within the agreed boundary; work transferred to another team; participation from the people closest to the issue; and the time from contrary evidence to a documented revision of the plan.
These measures are not a full business case. They are a test of whether the next commitment should be larger, different or delayed. Any released hours are capacity released in that local process; they are not cash savings unless costs actually fall.
Know when not to use a pilot
A pilot is not a substitute for an immediate safety, legal, security or customer-protection action. Nor should it become a way to avoid a decision where evidence is already sufficient and the cost of delay is real.
It also needs honest sponsorship. A pilot advertised as a consultation but treated as a predetermined rollout will damage trust. The director has to be prepared to revise the programme when the evidence contradicts the original story.
Start with a clearer baseline
For leaders stepping into a complex transition, the programme’s current Free Assessment is the verified no-cost starting point. The site presents it as a 15-minute baseline assessment with no commitment. The right early win still depends on the particular operating constraints, relationships and evidence in front of the transformation director.