Why the Fastest Improvement Is Rarely the One That Lasts

There is a moment in almost every improvement programme when someone sensible suggests starting with the low-hanging fruit. It sounds like pragmatism. It usually is not. It is a decision to buy momentum with credibility, and the invoice arrives later.

We have sat through enough of these conversations to recognise the shape. The programme has a mandate, a timeline and a nervous sponsor. Someone proposes a visible win within six weeks to prove the approach works. The win is delivered. The slide is circulated. Eighteen months on, the underlying problem is still there, and the win has become a documented workaround that nobody now has the appetite to unpick.

What a quick win actually delivers

Quick wins are rarely worthless in themselves. Removing a duplicated approval, simplifying a form, cutting a weekly meeting: these are real improvements and people notice them.

The difficulty is what they are asked to carry. They are loaded with a representational job they cannot do. A fast, shallow win demonstrates that change is possible. It does not demonstrate that the system is capable of changing, which is the question that matters once the novelty fades and the harder work begins.

Three costs tend to follow, and they compound.

Workarounds get formalised. A local fix that bypasses a broken decision route becomes the new standard, complete with a process map and a trained owner. The route stays broken, now with an accepted exception sitting next to it.

Systemic issues get masked. The improvement looks like it addressed the symptom. Diagnostics stop. The root cause, often a decision right sitting in the wrong place, continues to generate the same queue in a slightly different location.

Change appetite is spent. Every improvement consumes political capital, manager attention and a share of the organisation's tolerance for disruption. Spend it on the trivially fixable and you will find the account thin when the substantive work needs funding.

There is also a quieter cost. Teams learn what gets celebrated. If the visible reward goes to the fast, cosmetic fix, that is what the organisation will produce more of.

The win-worth-having test

Before committing to an early improvement, put it through four questions. It should clear all four.

• Does it remove work or move it? Genuine improvement reduces total effort somewhere in the system. Relocation of effort upstream or downstream is not a win, it is a transfer.
• Does it survive its owner leaving? If the improvement depends on one person's diligence rather than on a changed rule, it is a personal intervention, not an operational one.
• Would you be comfortable if it became permanent? Many quick wins are tolerable only because they are temporary. If it hardens into standard practice, does the system get better or stranger?
• Does it tell you something you did not know? The most valuable early work is diagnostic as well as useful. If the win teaches you nothing about why the problem persists, it is decoration.

Failing one of these is not fatal. Failing three means you are about to spend credibility on something you will have to undo.

Three alternatives that hold

If quick wins are the wrong opening move, what should come first? In our experience, three categories of work deliver slower visible returns but a far better trajectory.

1. Fix decision rights

A striking proportion of operational friction is not process friction at all. It is the consequence of decisions sitting with people who lack the information, time or authority to make them. Clarifying who decides what, within which boundaries, and by when, costs almost nothing and usually shortens queues more than any process redesign.

Start by mapping the three or four decisions that generate the most chasing. For each, name a single accountable role and a service standard for the response. Publish it. The improvement is unglamorous and invisible on a slide, which is precisely why it endures.

2. Build capability rather than dependency

Improvement that relies on a central team of specialists creates a queue at the door of that team. Capability built into the line, through short practical coaching in problem definition and small-scale experimentation, distributes the work and reduces the bottleneck.

The measure of success is not how many improvements the central team delivered. It is how many the line delivered without them.

3. Remove recurring friction

Keep a simple, honest log of the same irritations that appear in every team meeting: the report nobody uses, the approval that takes nine days, the handover that loses information twice a month. Recurring friction is a stronger signal than any single dramatic failure, because repetition tells you the system is producing it reliably.

Work the log in order of frequency rather than ease. The item that happens weekly and takes ten minutes costs more across a year than the crisis that happened once.

Holding the line

None of this argues for slowness. It argues for spending early credibility on things that change the operating rules rather than on things that change the mood.

When someone proposes the low-hanging fruit, the useful response is not a refusal. It is a question: what will this fix, and what will still be broken afterwards? If the answer is vague, the win is not ready. Choose the improvement you would be content to live with in three years, and start there.