Continuous Improvement

Continuous improvement starts with reality

By Lesego Modiakgotla · 8 October 2026 · 6 min read

Many improvement initiatives begin with enthusiasm and end quietly. A new system is introduced, a workshop generates ideas, a project team is formed—and twelve months later the original problem is still there, sometimes in a different form.

One of the most common reasons is that the improvement started with a solution rather than with reality. The team knew what it wanted to implement before it understood what was actually happening.

As an Industrial Engineer and Lean Six Sigma Black Belt, I learned early that improvement begins with an honest picture of the present. No engineer would redesign a production line using imaginary data. Yet organisations regularly try to improve processes they have only imagined: the process as written in the procedure, as remembered by management, or as described in last year's presentation.

Why continuous improvement initiatives fail: solutions before diagnosis

Solutions feel productive. They can be announced, budgeted and tracked. Diagnosis, by contrast, can feel like delay. It requires observation, data collection and patience with uncomfortable findings. Under pressure, organisations tend to skip it.

But a solution applied to a poorly understood problem is a gamble. It may work. It may also move the problem elsewhere, add complexity, or treat a symptom while the cause carries on.

A common pattern looks like this. Customer complaints rise, and someone proposes a new system, a new form or a new approval step. The change goes in quickly, everyone feels that action has been taken, and for a few weeks the complaints dip. Then they return, because the real cause—an unclear handover between two teams, perhaps, or a planning rule that no longer fits demand—was never touched. The organisation now has the original problem plus an extra layer of process to maintain.

Solutions are attractive because they let us skip the uncomfortable part. Diagnosis often reveals that the problem is closer to home than we hoped: in our own decisions, our own design, our own habits as leaders.

Acceptance is not surrender: understand the current condition

Lean thinking puts strong emphasis on understanding the current condition before designing the future one. Lean Six Sigma does the same through its first phases: define the problem clearly, then measure it before analysing causes. These disciplines exist because experience shows that people consistently overestimate how well they understand their own processes.

Understanding the current condition means knowing how the work is really done—not how the procedure says it should be done. It means knowing where time is lost, where errors are introduced, where people work around the system, and what the customer actually experiences.

This takes a particular kind of courage. Many leaders resist an honest baseline because it feels like admitting failure. It is not. Acceptance is not agreeing that the current situation is desirable. It is agreeing that it is real. A navigator blown off course does not reach port by insisting the ship is somewhere else. Every meaningful improvement starts with the same plain sentence: this is where we are. Not where the plan says we should be, and not where we intend to be next year. Where we are.

Go and see: observation reveals what reports hide

There is no substitute for observing the work where it happens. Reports summarise; observation reveals. When leaders and improvement teams spend time at the process, they notice the workarounds, the waiting, the informal fixes and the frustrations that never appear in a dashboard.

This is not about inspecting people. It is about respecting the work enough to understand it before trying to change it. The people closest to the process usually know where it hurts. What they often lack is someone senior enough to listen without becoming defensive.

When you go and see, resist the urge to explain what you observe. Watch first. Ask what makes the job hard today. Notice where people pause, search, wait, re-enter information or check someone else's work. Those moments are the process telling you the truth about itself. Every system leaves clues; the discipline is to collect them before forming conclusions.

A disciplined starting point for root cause analysis

The steps below are not new. What makes them powerful is doing them in order, and refusing to skip ahead when a favoured solution is already on the table.

1. Write a clear problem statement. Describe what is happening, where, when and to what extent—without implying a cause or a solution. "We need a new scheduling system" is a solution. "Orders for one product family are shipping late, and the delays are getting longer" is a problem.
2. Establish a baseline. Measure current performance so that improvement can be demonstrated rather than assumed. Look at the trend and the variation, not just the average.
3. Map the actual process. Walk it with the people who do the work, and draw what really happens, including the rework loops and workarounds.
4. Separate symptoms from causes. Ask why repeatedly until the answer points to something that can be changed. Test each proposed cause against the data before accepting it.
5. Only then design solutions. Test them on a small scale and check the results against the baseline.
6. Hold the gain. Update the standard, train the people affected and keep measuring, so the process does not quietly drift back.

No engineer would redesign a production line using imaginary data. Yet we often attempt to redesign our lives using imagined realities.

From Reality Always Wins, Chapter 5: Acceptance Is Not Surrender

The same applies to organisations. Effort that is cut off from reality is just motion. A team can work extremely hard and still be moving steadily in the wrong direction. A disciplined starting point anchors that effort in the truth.

Avoiding improvement theatre

Improvement theatre is activity that looks like progress without changing results: impressive boards, frequent meetings and long action lists that are never closed. It persists when organisations value the appearance of improvement more than evidence of it.

The warning signs are usually visible to anyone willing to look:

• Projects are reported by activity completed rather than by change in performance against a baseline.
• The same problems reappear on the agenda under new names.
• Improvement boards are updated before senior visits and ignored in between.
• Root causes are agreed in the meeting room without anyone having gone to see the process.
• Nobody can say which past improvements are still holding.

Theatre is not a sign of bad intentions. It is usually what happens when people are asked to show progress faster than reality allows. The cure is to ask for evidence rather than activity, and to treat an honest "this did not work" as useful information rather than a failure.

Continuous improvement means continuously returning to reality

Even good improvements fade. Processes drift. Customer expectations change. Equipment ages. People move on and new constraints appear. Continuous improvement exists because reality keeps moving. Facing it once is not enough; we have to keep coming back to it.

That is why the most effective improvement cultures are less dramatic than people expect. They are built on ordinary routines repeated consistently: short reviews at the process, regular checks against the baseline, leaders who ask what is getting in the way and then act on the answer. Reality rewards consistency more than intensity.

It also means leaders accept that drift is normal rather than shameful. Finding that a process has slipped is not evidence that the earlier work was wasted. It is evidence that someone is paying attention. The goal is not a perfect process that never needs correcting. It is a team that notices the drift early and responds before drift becomes distance.

Reality is the starting point

Real continuous improvement is quieter than improvement theatre. It starts with an honest view of the present, makes small changes, checks what happened and learns. It welcomes uncomfortable findings because they show where effort will actually make a difference.

Reality is not an obstacle to improvement. It is the starting point—and the organisations that keep returning to it are the ones that keep getting better.