3 Minutes Inside Operations: Root Cause Isn’t Just a Tool, It’s a Habit

In earlier episodes of the Back to Basics series, we explored how management systems, KPIs and behaviours shape execution. In this episode, Robert Vrugtman turns to something every operations leader knows too well: the same problems keep coming back. Scrap, delays, missed deliveries, rework, they seem to disappear after a quick fix, only to resurface a few weeks later under a different name. The question is not what went wrong. It’s why it keeps going wrong. That is where disciplined root cause analysis comes in.

Why Problems Keep Coming Back

Most organisations are good at fighting fires. A breakdown? Call maintenance. A quality issue? Sort, rework, ship. A late order? Overtime. On the surface, the problem is solved. But underneath, nothing has really changed. The process that created the issue is still the same. The conditions that allowed the error are still in place. So, the symptoms return. Without a structured way to understand causes, teams end up treating every incident as an isolated event instead of a predictable outcome of their system.

From Symptoms to Causes

Root cause analysis is about moving from “What happened?” to “Why did this happen in the first place – and why did we not see it coming?”. It forces teams to look beyond the immediate trigger and dig into the underlying mechanisms. Instead of stopping at “The operator made a mistake”, you ask: Was the standard clear? Was the training sufficient? Was the layout confusing? Were we running under abnormal pressure? One TBM client discovered that 80% of their recurring quality issues traced back to unclear work instructions at changeovers. By attacking that cause, not just correcting each defect, they cut defects dramatically and stabilised the process.

The Discipline Behind Root Cause Analysis

Effective root cause analysis is not a brainstorming session where people share opinions. It is a disciplined process. Problems are defined clearly and supported with data. Teams go to the gemba to see the problem where it happens, not in a meeting room. Tools like the 5 Whys, fishbone diagrams and simple data checks structure the thinking. The point is not to use fancy tools, but to force rigorous logic: each “why” must be backed by observable facts, not assumptions or blame. When done well, this discipline converts frustration into insight – and insight into concrete countermeasures.

Leaders Who Ask Better Questions

The quality of root cause analysis is directly tied to leadership behaviour. If leaders reward quick fixes and heroic firefighting, teams will stop digging for causes. If leaders react emotionally or search for culprits, people will hide information. But when leaders consistently ask “What in our process allowed this to happen?” instead of “Who messed up?”, the tone changes.

Connecting Root Cause Analysis to the Management System

Root cause analysis is not a one-off workshop after a crisis. It needs a home in the daily management system. Tier meetings should not only review yesterday’s performance but also track which problems were analysed, what causes were confirmed, and whether countermeasures are working. Visual boards make this visible: problem → cause → action → result. When this loop becomes routine, the organisation learns continuously. Leaders stop tolerating recurring issues as “the cost of doing business” and start treating them as signals that something in the system must change.

From Fixing Problems to Preventing Them

The real power of root cause analysis is prevention. When teams internalise this way of thinking, they start seeing weak signals earlier. Near misses, minor deviations and small frustrations become valuable data, not background noise. Instead of waiting for a major breakdown, they act on early warning signs. Over time, this shifts the culture: people feel responsible not only for hitting today’s numbers, but for improving tomorrow’s performance.

Back to Basics Means Fixing Causes, Not Symptoms

The message is straightforward. If your organisation is firefighting the same issues month after month, you do not have a capacity problem – you have a root cause problem. Leaders who insist on clear problem definition, fact-based analysis and process-focused thinking create the conditions for real improvement. Root cause analysis is not extra work on top of the day job. It is the work that reduces chaos, stabilises performance and frees up capacity for growth. Back to Basics means this: stop polishing symptoms, start eliminating causes.
See you in the next episode.