Dig From Symptom to Root Cause
In the last chapter you turned a vague gripe into a clear, bounded problem. That is a real step forward, but a well-defined problem still is not a solved one. Before you can fix anything, you have to know what is actually causing it, and that is rarely the first thing you notice. In this chapter you will learn to tell apart what you see on the surface from what keeps producing it underneath, and you will practice a simple, reliable method for digging down to the real cause.
How Do You Tell a Symptom from a Root Cause?
When a problem shows up, what grabs your attention is usually a symptom: the visible sign that something is wrong. A symptom is what you notice. Spoiled food in a shared fridge, a meeting that starts late, a machine that keeps jamming: those are all symptoms.
The root cause is different. It is the thing underneath that keeps producing the symptom. Remove it and the symptom stops coming back; leave it in place and the symptom returns no matter how many times you clean it up.
The reason this distinction matters is simple. If you treat only the symptom, you get relief that does not last. You throw out the spoiled food, and next week there is more. You remind everyone to be on time, and the following meeting still starts late. The trouble keeps returning because whatever was causing it is still there, quietly doing its job.
So the goal of this chapter is to get past the symptom and reach the cause that, once addressed, actually makes the problem go away.
Run the 5 Whys, Step by Step
You do not need a complicated technique to find a root cause. One of the simplest and most reliable is a method called the 5 Whys, first used in car manufacturing at Toyota and now applied almost everywhere. The idea is exactly what it sounds like: you start from the symptom and ask “why?” over and over, each answer becoming the thing you question next, until you reach a cause deep enough to act on.
Here is the procedure:
Write down the symptom as plainly as you can.
Ask “why does this happen?” and write the answer.
Take that answer and ask “why?” again.
Keep going, roughly five times, until the answer points to something you could actually change.
Stop when one more “why” would only take you somewhere too broad to act on, like “because people are busy.”
The “five” is a rough guide, not a rule. Sometimes three whys are enough; sometimes you need six. What matters is reaching a cause you can do something about.
There is one move beginners almost always miss.
When a “why” has two or three real answers, follow each one down its own path. You will often find that some branches lead to causes you can act on and others lead somewhere outside your control, which is exactly what the next section is about.
Which Causes Can You Actually Influence?
Once your 5 Whys has surfaced one or more root causes, sort them into two piles: the ones you can act on, and the ones you cannot.
A cause is in reach if you, or the people you are working with, could realistically change it. A cause is out of reach if it sits with someone else, or depends on forces no one nearby controls, like the weather, a national policy, or how a building was constructed decades ago. Both kinds are worth writing down, but only the in-reach causes are candidates for a solution.
This is not just tidiness. Naming which causes are out of reach stops you from pouring effort into something you were never going to move, and it points you straight at the causes where your work will actually pay off. Later, in Chapter 4, you will use this same in-reach and out-of-reach thinking to help decide where to draw the edge of the system you are looking at.
Trace One Symptom to Its Root
Let us run the method on a real everyday case.
The symptom. In a building’s shared community fridge, food keeps spoiling before anyone eats it.
Run the 5 Whys, following the branches.
Why is the food spoiling? Because items sit far past the point when they should have been used.
Why do they sit so long? Here the path branches into two real answers:
Branch A: because no one can tell which items are oldest.
Branch B: because the fridge is often too warm to keep food safely.
Branch A, why can no one tell? Because nothing is dated or ordered when it goes in. Why is nothing dated? Because no one was ever made responsible for organizing the fridge. That is a root cause: no one owns the upkeep.
Branch B, why is the fridge too warm? Because it is regularly overfilled, so air cannot circulate. Why is it overfilled? Because donations arrive in large batches with nowhere else to put them. That is a second root cause: intake outpaces the storage there is space for.
Sort the causes. “No one owns the upkeep” is in reach: residents could agree on who dates and rotates items. “Intake outpaces storage” is partly out of reach, since it depends on how and when donations arrive, though the storage side might be improvable.
Notice what happened. The obvious fix, “throw out the spoiled food,” touches neither root cause, which is why the food kept spoiling. Following two branches instead of one gave a fuller picture: one cause to act on now, and one to keep in view.
Your Turn!
Now trace a symptom of your own, using the fridge case as your model.
Scenario. A local hobby club has a recurring gripe: the weekly meetings always start at least twenty minutes late, so there is never enough time to get through everything planned.
Your task. 1. Write the symptom in one plain sentence. 2. Run the 5 Whys on it. When a “why” has more than one honest answer, follow each branch, and do not stop at the first cause that seems plausible. Aim to surface at least two root causes. 3. Mark each root cause as in reach or out of reach for the club members.
Do this in your own working document, and think it through yourself. Tracing a cause is the exact skill this course is building, so resist the urge to hand it to an AI tool to answer for you.
Then check your answer against the model solution found at the end of this chapter.
Let’s Recap!
A symptom is what you notice; a root cause is what keeps producing it, and treating only the symptom brings the problem back.
The 5 Whys traces a symptom to its cause by asking “why?” until you reach something you can act on.
Five is a rough guide: stop when one more “why” would only lead somewhere too broad to change.
A “why” can branch into several causes, so follow each branch rather than settling for the first answer.
Sorting causes into in reach and out of reach tells you where your effort will actually pay off.
You can now trace a problem down to the causes that keep it alive. In the next chapter, you will step back and see how those causes connect, by looking at the problem as part of a whole system.
Model Solution
Here is one strong way to trace the late-meetings symptom. Yours does not need to match it exactly; it needs to reach real causes and follow more than one branch.
Symptom. The club’s weekly meeting regularly starts about twenty minutes after its scheduled time.
5 Whys, with branches.
Why does it start late? Because most members arrive after the start time.
Why do members arrive late? Two honest branches:
Branch A: because the meeting has no clear first activity, so nothing is lost by arriving late.
Branch B: because it is scheduled right after the workday, when many are still commuting.
Branch A, why is there no clear first activity? Because no agenda is sent ahead, so no one knows what opens the meeting. Why is no agenda sent? Because no one has taken on preparing one. Root cause: no one owns setting the agenda.
Branch B, why does the schedule clash with commuting? Because the start time was fixed years ago and never revisited against members’ actual travel times. Root cause: the start time no longer fits members’ commutes.
In reach vs out of reach. Both root causes are things the club can act on: assign someone to send an agenda, and move the start time later. The commuting traffic itself is out of reach, but the club’s response to it is not.
Compare this with stopping at the first answer, “members arrive late.” That is still a symptom. Pushing through several whys, on more than one branch, is what turns it into causes you can actually do something about.
