Loading content
The 5 Whys method is a simple yet effective technique to determine the root cause of a problem by repeatedly asking why a problem occurs, typically five times. This helps identify deeper causes for sustainable solutions.
Use this profile to understand the building block briefly, place it in the model, and switch to the 360° assessment when needed.
Executable approach: can be applied and produces an outcome.
What organizes, connects, or makes decisions possible.
5 Whys is a simple root-cause analysis method. A group repeatedly asks why an observed problem occurred, moving from a visible symptom toward a cause that can be acted upon.
The method became widely known through Taiichi Ohno's problem-solving practice in the Toyota Production System. It helped teams look beyond the visible symptom after a disruption and find the conditions that make recurrence more likely.
Imagine a ladder from the event to the conditions behind it. Each answer to “Why?” forms the next rung and should be supported by observations, data, or people who understand the work. Five is a rule of thumb; what matters is a defensible causal chain. The endpoint should not be a convenient assignment of blame, but a cause that can be addressed through a useful system change. When several causes are plausible, the analysis branches; one linear chain is then often insufficient.
An observable and bounded event prevents the analysis from starting with vague assumptions.
Each answer describes a condition that plausibly explains the preceding event and can be investigated further.
Data, logs, observations, and domain knowledge test whether an assumed connection actually holds.
The analysis stops where a concrete system change can meaningfully reduce the risk of recurrence.
Complex problems often have several contributing causes and require more than one chain of why questions.
5 Whys works well for bounded incidents and as an entry point for retrospectives or postmortems. It quickly creates a shared picture. Complex, safety-critical, or tightly coupled systems need broader methods and stronger evidence alongside it.
Where this building block is located in the topic model.
No structure path available.
Explore how this building block connects to concepts, methods, technologies, and tools.
These sources establish the term and its professional meaning.
All direct connections of the current building block in a compact text view.
This classification shows where the building block typically matters, how demanding it is, and what kind of impact it has in the model.
The level within the organization (enterprise, domain, team) at which the AssetBlock is applied.