Why Improving Process Can Make Things Worse

The order that matters: direction, people, process — and what happens when you get it wrong

There is a kind of organisational meeting I have sat in too many times.

Someone has produced a flowchart. The flowchart is genuinely good — clean lines, sensible swim lanes, decision points marked with diamonds. The conversation is energetic. People are pointing at the bottlenecks. Someone has noticed a redundant approval step. Someone else is suggesting an automation. The room is alive with the satisfying sense that something is being improved.

What is rarely examined, in those rooms, is whether the process being improved should exist at all. Or whether the people inside it have been properly equipped. Or whether the direction the whole exercise is moving in is one anyone has recently checked.

This is the trap of process improvement. It is seductive precisely because it produces the feeling of progress without requiring the harder work that progress depends on. There is comfort in diagrams. There is satisfaction in optimisation. There is a subtle belief that if we could only refine the steps, the outcomes would follow.

Sometimes they do.

But a perfect process moving in the wrong direction is simply efficient misalignment. And in most organisations, that is what process improvement actually produces — not value, but a faster way for confusion and cost to accumulate.

The order matters more than most leaders realise

There is a sequence underneath all sustainable improvement work, and it is consistently inverted by the organisations that need it most.

Direction first. Where are we trying to go? What does success actually look like? Have we agreed, honestly, on what we are building toward — and have we tested that agreement against the people closest to the work? What value are we trying to create?

People second. Are the right people in the right roles? Are they equipped — with skill, with authority, with information, with the time to do the work properly? Do they understand what they are trying to achieve, and do they have the conditions under which they can do their best work?

Process third. Once direction is clear and people are equipped, the question of how the work flows becomes useful. Not before.

Most organisations get this exactly backwards. They reach for process improvement when direction is foggy and people are exhausted, because process is the only one of the three that feels concrete enough to fix on a whiteboard. Direction conversations are political. People conversations are personal. Process feels safe — analytical, mappable, neutral.

And so the diagrams come out. The cycle times get measured. The bottlenecks get identified. The optimisation work begins.

Underneath all of it, the foundations are still missing — and the better the process gets, the faster the misalignment travels through the organisation. This is the part that catches leaders by surprise: improving a broken system does not stabilise it. It accelerates the breakdown.

A process without purpose becomes ritual. A process without discipline becomes chaos. A process without people becomes theory. None of these are improved by adding cycle-time tracking.

This is why effectiveness must come before efficiency — and why the order is non-negotiable, not preferred. Doing the right things slowly produces value. Doing the wrong things quickly produces compounding cost.

What changes when the foundations are in place

When direction is clear and people are properly equipped, process improvement becomes powerful in a way it never can be otherwise. Measured. Meaningful. Grounded in reality rather than in the diagram on the wall.

The work itself becomes recognisable. You begin by studying the actual flow — not the documented flow, but what is actually happening when you follow a single piece of work from beginning to end. You watch where it moves cleanly, where it pauses, where it loops back, where it stalls entirely. You note who touches it, what they do with it, and how it changes hands. And how long it takes.

Then you ask the question most process work avoids: why does this process exist?

Some processes exist for regulation. Some for safety. Some for genuine learning that has been built into how the work moves. Some exist because they once solved a problem that no longer exists, and nobody has questioned them since. The willingness to ask the existence question — honestly, without ego — is what separates real process improvement from rearranging the deckchairs.

You measure cycle time. You attach cost — not just financial, but in time, energy, and attention spent. You visualise the invisible. Not to punish, but to understand. The goal is to make the system legible enough that decisions about it can actually be made.

And once a process has been improved, you protect it with discipline. Because a well-designed process, followed consistently, is genuinely liberating. It reduces cognitive load. It frees up the attention that was previously being spent on remembering what to do. It means we can keep learning. That freed attention can then go where it should always have been going — to creativity, to collaboration, to judgement, to the work that no flowchart has ever been able to capture.

A well-designed process ignored, however, creates disorder. Worse disorder than no process at all, because the absence of a working process at least signals to people that they need to bring their own judgement. A process that exists but is not followed teaches people to ignore the system, and that lesson is hard to unlearn.

The dual nature of work

There is a final piece of the picture that most process improvement work systematically forgets.

Some work is complicated. It can be analysed, decomposed, designed, optimised. Cycle times can be measured. Bottlenecks can be removed. The relationship between input and output is reasonably stable.

But much of the work in any organisation is complex. It involves people — with emotions, egos, ambitions, fatigue, disagreements, miscommunications, and the full range of human inconsistency. No diagram predicts those. No flowchart guarantees behaviour. No AI can model that reality.

The human element does not yield to optimisation in the way the technical element does, and pretending otherwise produces some of the most expensive failures in modern organisational life — beautifully designed systems that do not work because nobody asked whether the people inside them could plausibly behave the way the diagram required.

Process improvement that ignores this distinction tends to optimise the complicated parts of work and ignore the complex ones. The complicated parts get faster. The complex ones become more strained. Eventually, the strain dominates the gains, and the whole thing falls apart in a way that surprises everyone except the people doing the work.

The discipline is to know which kind of problem you are actually facing. Complicated problems benefit from analysis and design. Complex problems benefit from feedback, learning, conversation, the right climate and the willingness to adjust. Most real organisational work is a mix of both — and the leaders who succeed are the ones who can tell which lever to pull when.

The principle, plainly stated

This piece is not a rejection of process. Process matters. Well-designed processes save organisations enormous amounts of cognitive effort, and the absence of process produces its own kind of expensive chaos.

The point is more specific. Process is the third move, not the first. It serves the journey from idea to value — it does not create the journey, and it does not substitute for the work of choosing the right journey in the first place.

So improve the process, yes. But only after you are certain you are improving the right journey, with the right people, toward the right future.

Because a smoother road is meaningless if it leads nowhere worth arriving at.