ARTICLE
The 5 Why's
PRESSURE & DECISIONS - MARCH 2026
Most problems in creative businesses get solved at the level of their symptoms. The client is unhappy: improve communication. The project ran over budget: tighten the estimate next time. A key person left: adjust the salary band. Each of these responses addresses what happened, not why it happened, which means the same problem will return in a slightly different form and be treated as a new problem requiring a new response. Taiichi Ohno, the industrial engineer who built the Toyota Production System, designed a method specifically for the organisations that were solving their problems at the wrong level. It asks one question five times.
What It Is
The 5 Whys is a root cause analysis technique developed by Taiichi Ohno and formalised as a core component of the Toyota Production System in the 1950s. The method is simple: when a problem occurs, ask why it occurred. Take the answer and ask why that occurred. Continue for five iterations. The fifth why, or sometimes the third or fourth, typically arrives at a cause that is structural rather than symptomatic: a process flaw, a system gap, or a cultural condition rather than an individual error or a surface-level failure.
Ohno's original example has become canonical: a welding robot stops. Why? The fuse blew. Why? The bearings were overloaded. Why? Insufficient lubrication. Why? The lubrication pump was not drawing enough. Why? The pump intake was clogged with metal filings. The fix is to add a strainer. Not to replace the fuse.
Why It Matters Now
Creative businesses operate under time pressure that systematically rewards fast, surface-level responses. A project is late: the team works harder. A client is dissatisfied: the creative director calls them. The brief was misunderstood: the account manager takes more notes next time. These responses are fast, visible, and address the immediate problem. They also preserve the conditions that produced it.
The 5 Whys requires slowing down at the moment when an organisation most wants to speed up. It asks the organisation to treat a problem as information rather than as an emergency to be resolved and forgotten. In a sector where the pressure to move to the next project is constant and the retrospective is a luxury, that discipline is genuinely difficult. It is also the only mechanism that produces learning that permanently reduces the frequency of recurrent problems.
Case Evidence
Toyota's application of the 5 Whys across its production system produced an organisational culture of structural problem-solving that competitors could not replicate by copying individual solutions, because the solutions were specific to root causes identified through a process competitors were not using.
Virginia Mason Medical Center in Seattle applied Toyota Production System principles to hospital operations in the early 2000s and used root cause analysis to reduce medication errors and surgical complications in ways that symptomatic fixes had failed to achieve over years of conventional management.
In creative business, the 5 Whys most commonly surfaces structural problems in briefing processes, client communication architecture, and project scoping methodology. A scope creep problem, asked through five iterations, almost always arrives at a root cause in the initial brief quality or the contract structure, not in the individual project where the creep occurred.
How It Works
STEP 01
Define the problem precisely before beginning: a vague problem will generate vague answers at each iteration.
STEP 02
Ask the first why and insist on a specific, factual answer, not an interpretation or a judgment about who is responsible.
STEP 03
Take that answer as the new problem statement and repeat, maintaining the discipline to focus on process and system causes rather than individual performance.
STEP 04
Stop when the answer points to something actionable and structural: a process that can be changed, a system that can be improved, a framework that is missing.
STEP 05
Build the fix at the level of the root cause, not at the level where the problem first became visible, and test whether the fix prevents the original problem from recurring.
Industry Application
The 5 Whys applied to the most common problems in creative businesses consistently produces the same pattern: the visible problem is interpersonal or executional, and the root cause is structural. Client dissatisfaction with work quality traces to a brief that was not adequately challenged at intake. Project overruns trace to scoping processes that price optimistically. Staff turnover traces to a development framework that promoted technical skill without building leadership capacity.
The value is not in the individual answers but in the discipline of asking. Organisations that use the 5 Whys as a standard response to significant problems develop a different relationship to failure over time. Problems become data rather than embarrassments.
Financial Dimension
Research published in the Journal of Manufacturing Technology Management found that organisations applying systematic root cause analysis reduced recurrent problem frequency by 40 to 70 percent over a two-year period compared to organisations applying symptomatic fixes. In a creative consultancy where recurrent problems consume 15 to 25 percent of project margin, reducing recurrence frequency by that magnitude represents a material improvement in annual profitability without any increase in revenue.
Where the Market Fails
The creative industry has developed a sophisticated vocabulary for failure after the fact: the post-mortem, the retrospective, the lessons learned session. Most of these processes document what happened and generate a list of things to do differently next time. Very few trace what happened to its structural root cause, because doing so requires more time, more honesty, and more willingness to implicate the process rather than the individual.
Diagnostic Questions
QUESTION 01:
When a significant problem occurred in the last six months, was the response designed to fix the immediate situation or to understand and change the conditions that produced it?
QUESTION 02:
Is there a standard process for asking why a problem occurred more than once before generating a response?
QUESTION 03:
In the last year, did any process, system, or framework change as a result of investigating the root cause of a recurring problem?
Practitioner Reference
"By repeating why five times, the nature of the problem as well as its solution becomes clear. The root cause of Toyota's success is not any particular technology but its ability to learn." Taiichi Ohno, Toyota Production System: Beyond Large-Scale Production, 1988
Key Takeaways
01
Most problems get solved at the level of their symptoms; the 5 Whys is a method for identifying and addressing the structural root cause instead.
02
The fifth why almost always arrives at a process gap, a system flaw, or a cultural condition rather than an individual error.
03
The discipline required to use the 5 Whys correctly is the discipline to slow down at the moment the organisation most wants to speed up.
04
Organisations that investigate failure structurally develop a different relationship to it over time, treating problems as data rather than emergencies.
05
Reducing recurrent problem frequency through root cause analysis produces margin improvement without revenue increase.
What This Means for DON'T WASTE I Partnerships
Under Pressure and Decisions, the 5 Whys provides the investigative framework DWI applies when a client organisation is experiencing recurrent problems that surface-level fixes have failed to resolve. An organisation that can ask the right questions of its own problems is structurally more resilient than one that depends on external diagnosis.
Closing
The problem that keeps coming back was never solved. It was managed. There is a difference.
Sources
Taiichi Ohno, Toyota Production System: Beyond Large-Scale Production, Productivity Press (1988) Toyota Global, The Toyota Way: toyota-global.com/company/toyota_traditions/quality Virginia Mason Institute, Application of Toyota Production System: virginiamasoninstitute.org Journal of Manufacturing Technology Management, root cause analysis research: emerald.com