Credit first. The five whys is a Toyota technique. Olivier Serrat's guide for the Asian Development Bank credits Sakichi Toyoda with developing it, and Taiichi Ohno, who shaped the Toyota Production System, described asking why five times whenever a problem turns up as the basis of Toyota's scientific approach in his book on that system. Toyota still says it uses the technique to get to the root cause of every problem. This worksheet is our own independent take on the method; Toyota has not reviewed, endorsed or partnered with it.

Why a chain of whys works

Most recurring problems get fixed at the surface. You are late again, so you promise to leave earlier. You skipped the run again, so you set a second alarm. The promise holds for a few days and then the problem is back, because nothing underneath it changed.

The five whys makes you look underneath. You write the problem the way it actually happens, ask why, and then ask why about your own answer, so each answer becomes the next question. A typical chain for a skipped morning run goes like this: you hit snooze three times; you were too tired when the alarm went off; you went to bed after midnight; you scrolled in bed until late; the phone charges on the nightstand. Notice how the last answer differs from the first. Get up on time is a wish. Charge the phone in the kitchen is a change you can make tonight.

That is the stopping rule. Keep going until you reach something you can act on, something that would keep the problem from coming back if it changed. Serrat calls five a good rule of thumb, and some chains get there in three while others need more.

How this page works

The page is a garden bed in cross-section. Your problem sits on the surface, each why you answer opens the next layer of soil, and a root is drawn down through the layers as you dig. The bed holds five layers. If you reach the fifth and still have nothing you could change, the problem at the top is probably too broad, so narrow it and start again.

When an answer feels like something within your reach, mark it as the root. The page then asks for one change at the root and a day to look again: a week, two weeks or a month out. Plant the fix and it moves to the planted list, where it waits for its day. When the day comes, mark it held or grew back. The list keeps a running count, so over a few months you can see which kinds of fixes tend to hold for you.

Two more things happen as the list fills. When you mark a new root, the page shows the roots you found before and flags any that share a word with the new one, so you can say this is the same root. Problems linked that way are grouped together, and a root sitting under three different problems deserves more of your attention than any one problem above it. And when a fix grows back, you can dig the same problem again, with the old root shown so that you look for a different answer.

What the evidence does and does not say

Be clear about what this tool is. The five whys is a thinking habit, not a tested treatment or an assessment, and being popular is not proof that it works. In a critique titled The problem with ‘5 whys’, Alan Card points out that a single chain lands on one root cause at the end of one causal path, and that two teams studying the same incident are unlikely to arrive at the same answer. He argues it should be dropped from serious safety investigations in healthcare, while granting that it teaches the value of digging deeper. Serrat lists similar caveats: people stop at symptoms, and answers rarely reach past what the person already knows.

For personal problems, those limits turn into three habits. Check each answer against what actually happened, not what sounds plausible. When more than one answer fits a layer, note the other and dig it next time. And treat a fix that grows back as information: the problem probably has a second root.

Using it with a team

At work the method usually runs as a group exercise. Serrat's version starts by agreeing on the problem statement, records every sensible answer to each why, and follows each plausible branch before settling on the most likely systemic cause. Keep the questions about the process rather than about who slipped. For incidents where someone got hurt, use a fuller root cause analysis that allows several contributing causes instead of one chain.

When to use it

Use this page for small problems that repeat: late mornings, skipped workouts, the same argument about dishes, money that drains away on takeout. For a single moment you want to understand rather than a pattern, the Reflective Journal suits it better. If your root turns out to be a habit, the Habit Loop Worksheet helps you redesign its cue and reward. And if the root is something you keep putting off, The Cost of Avoidance adds up what the delay is costing you.