The symptom is rarely the problem I spent two hours last month with someone who was convinced their problem was hiring. They could not keep good people. Three operations managers in eighteen months. Each one started strong, then faded, then left. They wanted to talk about recruitment strategies, interview questions, salary benchmarks. I asked them to try something different first. We did the 5 Whys. Took about fifteen minutes. By the end, we had found the actual problem: there was no documented process for anything. Each new manager walked into chaos, built their own systems from scratch, burned out trying to hold it together, and quit. The hiring was not broken. The job was impossible. This happens constantly. People running their own thing come to me with what they think is the problem. Usually it is a symptom. The 5 Whys is how you tell the difference. What the 5 Whys actually is Toyota developed this in the 1950s. Taiichi Ohno, who built their production system, used it to trace manufacturing defects back to their origin. The method is simple: you state a problem, then ask why it happened. You take that answer and ask why again. Repeat until you hit something structural. Five is not a magic number. Sometimes you get there in three. Sometimes it takes seven. The point is to keep pushing past the obvious until you reach a cause you can actually change. Here is the structure: Problem: Revenue dropped 20% this quarter. Why? We lost three major clients. Why? They said our response times were too slow. Why? Support tickets were sitting in the queue for days. Why? Our support person was also handling onboarding for new clients. Why? We never hired a second support role when we grew past 50 clients. The surface problem was revenue. The root cause was a staffing decision made eight months ago. Fixing response times without addressing capacity would have been a plaster on a fracture. Why people get this wrong I see three common failures with the 5 Whys. The first is stopping too early. Someone asks why twice, gets an answer that sounds reasonable, and stops there. "We lost clients because response times were slow" feels like a complete explanation. It is not. It is a description of what happened, not why it happened. The second is blaming people instead of systems. "Why did the project fail? Because Sarah did not finish her part." That is not a root cause. That is a name. Why did Sarah not finish? Was she overloaded? Was the brief unclear? Did she have the resources? If you fire Sarah and the next person fails the same way, you have learned nothing. The third is doing this alone. Your own blind spots will steer the answers. I have seen business owners do the 5 Whys and somehow arrive at "the market is difficult" as their root cause. That is not actionable. That is an excuse dressed as analysis. You need someone who will challenge your answers. When to use it The 5 Whys works best on specific, contained problems. A project that went over budget. A client who churned. A process that keeps breaking. A hire that did not work out. It is less useful for vague strategic questions like "why is growth slow" or "why are we not more profitable". Those need breaking down into smaller problems first. I use it with clients at ALIRA. when something has gone wrong and they want to react quickly. The instinct is always to patch the immediate issue. The 5 Whys forces a pause. Often the fix that feels urgent is not the fix that matters. With everything happening in the economy right now, borrowing costs climbing, uncertainty about what comes next, people are looking for places to cut or change. That pressure makes the 5 Whys more valuable, not less. Cutting the wrong thing because you misdiagnosed the problem is expensive. I worked with someone last year who nearly eliminated a role that turned out to be the only thing holding their delivery process together. The 5 Whys caught it before they made the decision. How to run a proper session Write the problem down. Be specific. "Sales are down" is too vague. "We closed 40% fewer deals in Q1 compared to Q4" is better. Ask why. Write the answer. Then treat that answer as a new problem statement and ask why again. At each stage, check: is this something we can change? Is this within our control? If not, you have probably landed on a circumstance, not a cause. Keep going. When you reach something structural, something about how the business operates, how decisions get made, how resources are allocated, you are likely at the root. Document the chain. The path matters as much as the destination. It shows you where the system broke down. A real example from last quarter Someone came to me because their cash flow was unpredictable. They thought the problem was clients paying late. Why are clients paying late? Because invoices go out at random times. Why? Because we invoice when we remember, not on a schedule. Why? Because there is no invoicing process. It is whoever has time. Why? Because we never assigned ownership of finance admin. Why? Because we assumed it would sort itself out as we grew. The root cause was not late-paying clients. It was an assumption made two years earlier that admin would just happen. We fixed it by assigning one person to send invoices every Friday. Cash flow stabilised within six weeks. Average payment time dropped from 34 days to 19. What to do this week Pick one problem that keeps recurring. Not your biggest strategic challenge. Something specific that has gone wrong more than once. Run the 5 Whys on paper or using the 5 Whys tool at alira.london. Write each answer before moving to the next question. Do not skip ahead. Share your chain with someone who will push back. A business partner, a mentor, someone from your team. Ask them where you stopped too early or blamed a person instead of a system. If the root cause is something you can change this week, change it. If it needs more work, put it in your calendar as a project, not a someday task.