#How the 5 Whys Works — Surface vs. Root
The 5 Whys is a root-cause analysis technique developed by Sakichi Toyoda of Toyota in the 1950s. When a symptom occurs, you ask “why?” five times in a row, descending from the surface to the root. It looks simple, but surprisingly few people actually go all the way down — most stop, satisfied, after one or two rounds. The real essence usually only shows up at steps three through five.
#Applying It to a Business Plan — A Checkout Drop-Off Case
A concrete example beats an abstract explanation. Let's dig into the symptom “a 70% drop-off rate at B2C checkout” using the 5 Whys.
| Step | Question | Answer |
|---|---|---|
| Symptom | 70% drop-off rate at checkout | — |
| Why 1 | Why does 70% drop off? | The checkout form has 12 fields — too many |
| Why 2 | Why 12 fields? | Card details, shipping address, and terms agreement all have to be entered fresh every time |
| Why 3 | Why every time? | The “save” feature isn't trusted |
| Why 4 | Why isn't it trusted? | Signup and checkout flows are kept separate |
| Why 5 | Why separate? | We followed the payment gateway's guide and never validated our own user flow ← root cause |
Surface-level answer: “shorten the checkout form.” Root-cause answer: “merge the signup and checkout flows, and redesign the flow using our own user-validation data instead of the payment gateway's guide.” The cost, impact, and timeline of the two solutions are completely different. Trimming the form based on the surface answer only cuts drop-off by 10%; redesigning the flow based on the root cause cuts drop-off by 40–50%.
#Three Common Traps
- You can't get to five whys — you stop, satisfied with “ah, that's why,” after 1–2 rounds. That's actually still the surface.
- Answers get progressively weaker — the deeper you go, the vaguer the answers get, or they trail off into “I think...”. That's a sign of insufficient data or interviews.
- The causal chain breaks — the answer to Why 3 isn't actually the direct cause of Why 2, but an unrelated event. You need to verify the causal chain holds.
#Worksheet — The 5-Step Why Template
Copy the table below directly and apply it to one core problem in your own business plan. It takes about 30 minutes, and by the end you'll usually see “ah, this is the part that was weak.”
| Step | Question template | Evidence (data / interviews / logs) |
|---|---|---|
| Symptom | The problem I'm trying to solve, in one sentence | Quantified metric (% / count / frequency) |
| Why 1 | Why does this symptom occur? | 1st-level cause + evidence |
| Why 2 | Why does that 1st-level cause occur? | 2nd-level cause + evidence |
| Why 3 | Why does that 2nd-level cause occur? | 3rd-level cause + evidence |
| Why 4 | Why does that 3rd-level cause occur? | 4th-level cause + evidence |
| Why 5 | Why does that 4th-level cause occur? | Root cause + verifiable evidence |
Once you've finished all five steps, answer these: (1) does the root cause end in a structure, environment, or process rather than a person? (2) is every evidence cell filled with actual data? (3) does the solution address the root cause rather than the surface? If the answer to all three is “yes,” your business plan's P section has passing-level depth.
#Self-Diagnosis Across the P/S/T Axes — Applying the 5 Whys
The 5 Whys can be applied not just to P (Problem) but also to S (Solution) and T (Team). Here's a three-axis approach for quickly diagnosing weaknesses in a business plan.
| Axis | Starting symptom | The root the 5 Whys should reach |
|---|---|---|
| P | Customers don't know about us | → It's not weak marketing — the customer definition itself is vague |
| S | We built an MVP, but nobody uses it | → The solution isn't wrong — the problem it solves isn't real |
| T | Execution isn't happening | → It's not a lack of motivation — decision-making authority and roles (R&R) are unclear |
#Automating the 5 Whys in OpenSeed
It's hard to push the 5 Whys all the way through on your own because it's easy to accept your own answer. An outside perspective helps. OpenSeed's AI review can examine the claims in your business plan by asking why each one is true and checking the logic and evidence behind it.
Verify Your Essence with an Outside Perspective
Use OpenSeed's AI review to examine the reasoning and evidence behind your business plan's claims.
Pre-submission business-plan review with clear service limitations
Start OpenSeed Review →