DESCRIPTION
Turn complexity into one clear insight by using your curiosity as your storytelling engine to ask the question “Why?” five times and to get the “One powerful answer” which points out the real reason.
The “5 Whys, 1 Answer” method is an adaptation of the classic Five Whys root-cause analysis technique, used to uncover the underlying reason behind a problem or situation by repeatedly asking “why?” about the previous answer. The process typically involves asking “why” five times, each answer leading to the next question, until a fundamental cause or insight emerges.
In business storytelling, the method is used to transform a simple situation into a meaningful narrative that explains why something truly happened and what the real lesson or solution is. Its main superpower is clarity: instead of presenting a story full of symptoms, descriptions, buzzwords, it leads audiences step-by-step toward the root insight: the single answer that explains the entire chain of events.
ORIGIN
Although the main method ist based on kids behaviour, Sakichi Toyoda adapted the approach for Toyota Motor Corporation for their Production System in the 1930’s.
The method became a fundamental tool in Lean Manufacturing and quality management, used to identify root causes rather than superficial problems.
The 5 Why-questions would force to think about the real reason and deliver clarity at the end. The phrase “5 Whys, 1 Answer” is a storytelling adaptation: five explorative questions leading to a single core insight or lesson.
USED BY
Commonly used in environments where understanding cause-and-effect matters, such as lean manufacturing and quality management teams, process design and product development teams, strategy workshops and innovation teams, business storytelling and consulting contexts explaining transformation or failure.
Approximately needed time
- Step 1: 1 hours
- Step 2: 1 hours
- Step 3: 1 hours
- Step 4: 1 hours
- Step 5: 1 hours
- TOTAL: 5 hours
METHOD
MATERIAL YOU COULD NEED: Whiteboard or digital collaboration board, sticky notes or cards for each “Why” layer, timeline or description of the problem/situation, data sources supporting answers (metrics, reports).
STAKEHOLDER GOOD TO KNOW: Multiple perspectives reduce bias and prevent stopping too early in the questioning chain. Therefore, team members involved in the original situation to supply/add context, insights and value to the answers, and decision makers and the end to validate, or get a buy-in, for the “final” answer, should be part of the story design.
STEPS
DEFINE THE PROBLEM
The process has to start with a clearly defined problem or situation. Without clarity, the questions will lead to vague conclusions. The team writes down a precise statement describing the situation, challenge, or event that needs explanation. This becomes the starting point of the questioning chain.
Supporting methods: Transformation and mapping methods.
Example: “Customer satisfaction dropped by 20% last quarter.”
FIRST WHY: “Kick ass”-Why to start with
The first “why” is the “instinctive” pain and reason for action and identifies the most visible cause and starts the causal chain. Participants ask: Why did this problem occur? The answer should be factual and evidence-based and stand as a stand-alone “Challenge” for the rest of the activities.
Supporting methods: Root causes, brainstorming, data pools as “base of evidence”
Example:
- Problem: Customer satisfaction dropped.
- Why #1: Because delivery times increased significantly.
GO DEEP: Dig deeper and add 1-3 more Why’s
The deeper questions move the story from symptoms toward underlying processes or structural issues. For each answer, ask “Why (did that happen)?” again and again and again… Usually these 3 additional layers reveal the real patterns or systemic issues and failures.
Supporting methods: Fishbone diagram, (mind) mapping approaches, lean analysis tools.
Example:
- Why #2: Delivery times increased because warehouse processing slowed.
- Why #3: Warehouse processing slowed due to new inventory software.
- Why #4: The software rollout lacked proper employee training.
ALL IN WITH THE LAST ONE: Identify thee root of the initial need
The final “why” should reveal the root cause, fundamentally explaining the chain of answers. Often the root cause is a process, management decision, something which (not) happened/changed over time, or systemic weakness rather than an isolated event.
Supporting methods: Root causes analöysis, system and/or design thinking.
Example:
- Why #5: Training wasn’t planned because the project timeline was compressed to meet quarterly targets.
The root insight: short-term management decisions compromised operational readiness and now need adaptions/changes.
THE ONE: Craft the “One Answer” story
The purpose of storytelling is to convert the analytical chain into a clear narrative insight. Now, the story structure becomes a logic chain of events from problem, over the “Why” chain to the root insight and the lesson or action needed. The final message explains not only what happened but why it truly happened.
Supporting methods: Story pyramid, SCARF model, transformation map.
Example: “Our customer satisfaction didn’t drop because of logistics alone; it dropped because we rushed a system rollout without training. The real story isn’t slower delivery—it’s leadership choosing speed over readiness.”
- The number “five” is symbolic, meaning you ask “why” as many times as needed to reach the root cause. In most cases 5 are sufficient though…
- The technique is simple but powerful because it forces teams to move beyond surface symptoms.
- It works best when combined with other analysis tools such as fishbone diagrams or process mapping.
- In storytelling contexts, the chain of “whys” becomes a narrative device showing how a situation evolved.
PROMINENT BRANDS USING IT:
Many organisations apply the “5 Whys” technique in operations, processes and improvement activities (like Toyota Motor Corporation). Companies applying Lean manufacturing and Six Sigma approaches and technology companies performing incident root-cause analysis too. Even if not explicitly used for storytelling, the logic often appears in case studies explaining failures or innovation breakthroughs.
ANECDOTES:
A famous teaching example from Toyota describes a machine that stopped working.
- Why? The fuse blew.
- Why? The bearing overheated.
- Why? There was insufficient lubrication.
- Why? The lubrication pump wasn’t circulating enough oil.
- Why? The pump intake was clogged with metal shavings.
The story reveals that the real issue wasn’t the fuse, but the the maintenance process, demonstrating how the “5 Whys” method exposes deeper systemic causes.
