Based on patterns observed across real organisations
Late on a Thursday afternoon, the detective stands on the floor of a food production site, watching the line move steadily.
A batch of product is inspected at the line. It moves forward, only to be checked again before packaging. Then, before dispatch, it is reviewed once more. Each check is carried out carefully. Each one feels justified. But when asked why all three are needed, the answers are unclear.
The checks have been added over time. One to improve quality. Another to reduce risk. A third “just to be safe.”
Nothing is technically wrong. But everything is taking longer than it should.
At first glance, the process looks careful and thorough.
But the detective knows better. This is Overprocessing, one of the 8 wastes in Lean, where more work is done than the output actually requires.
If you’re new to the 8 wastes, this case links back to the bigger picture explored in our original blog post here.
The Scene: When Simple Becomes Complicated
In many organisations, overprocessing creeps in quietly.
A task is checked twice because trust was never built into the system. A process gains another approval step because nobody wanted to remove the old one. A report becomes more detailed over time because no one wants to miss anything. Over time, one small extra step becomes two, then three, and suddenly the process is far more complicated than it needs to be.
The problem is not that people are being careless. It is that the process has grown layers of effort that no longer add value. What once may have made sense now exists only because nobody has stopped to question it.
And every extra step consumes time, attention, and energy that could be spent on the work that actually matters.
Clues: Where to Look for Overprocessing
Overprocessing waste shows up wherever work is being done beyond what the customer, user, or process actually needs. It often hides in routines that feel normal because they have been around for a long time.
You are likely to see it in places like these:
- Re-entering or duplicating data across systems that don’t connect
- Extra approvals or sign-offs for routine, low-risk work
- Reports or documents more detailed than anyone uses
- Full checks or reviews applied even when risk is minimal
- Steps continued simply because “that’s how it’s always been done”
Anywhere a step exists because “that’s how we’ve always done it,” overprocessing may be nearby.
Interrogation Questions: How to Spot It in Your Process
To uncover overprocessing, ask questions that challenge every step in the chain.
- What value does each step add, and for whom?
- Where is work being duplicated due to poor systems or unclear ownership?
- Are approvals and checks proportionate to the actual level of risk?
- If we removed this step, what would actually go wrong — and do we have evidence of that risk?
These questions help separate necessary work from inherited complexity.
The Verdict: What’s Really Going On
Overprocessing is bureaucracy that has outlived its purpose.
It builds up because changing a process takes effort, because nobody owns the review, and because “this is how we do it” can be a very persuasive phrase. But when a process contains steps that no longer add value, those steps become waste, even if they are carried out carefully.
The overcomplicated step is not a sign of diligence. It is a sign that the process has not kept pace with the world around it.
And once you start spotting overprocessing, the trail does not stop here. If a process has too many steps, it often has too many chances to go wrong, too many handoffs, and too much rework.