Article
Startup Guide

How to Ask ‘Why’ Five Times — A Self-Diagnosis Workbook for Your Business Plan

2026.05.01·8 min·OPENSEED

A wrong diagnosis produces a wrong prescription. Toyota's 5 Whys technique is the simplest, and yet one of the most powerful, tools for separating “surface symptom” from “root cause.” This article provides a concrete worksheet for applying the 5 Whys to your business plan, the traps people commonly fall into, and worked examples applying it to the P (Problem), S (Solution), and T (Team) axes. With just paper and a pen, you can uncover a weakness in your own business plan in 30 minutes.

Intro.

#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.

TIP
The 5 Whys isn't a tool for blaming a person. It asks “why did that environment or structure exist,” not “who screwed up.” If your answer ends with a person, you've applied it wrong.
02

#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.

StepQuestionAnswer
Symptom70% drop-off rate at checkout
Why 1Why does 70% drop off?The checkout form has 12 fields — too many
Why 2Why 12 fields?Card details, shipping address, and terms agreement all have to be entered fresh every time
Why 3Why every time?The “save” feature isn't trusted
Why 4Why isn't it trusted?Signup and checkout flows are kept separate
Why 5Why 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%.

03

#Three Common Traps

  1. 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.
  2. 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.
  3. 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.
주의
If you get stuck at Why 3, don't stop there — go back and reinforce it with interviews, logs, or customer data. Filling in five levels with data-free guessing gets you to a fake essence.
04

#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.”

StepQuestion templateEvidence (data / interviews / logs)
SymptomThe problem I'm trying to solve, in one sentenceQuantified metric (% / count / frequency)
Why 1Why does this symptom occur?1st-level cause + evidence
Why 2Why does that 1st-level cause occur?2nd-level cause + evidence
Why 3Why does that 2nd-level cause occur?3rd-level cause + evidence
Why 4Why does that 3rd-level cause occur?4th-level cause + evidence
Why 5Why 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.

05

#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.

AxisStarting symptomThe root the 5 Whys should reach
PCustomers don't know about us→ It's not weak marketing — the customer definition itself is vague
SWe built an MVP, but nobody uses it→ The solution isn't wrong — the problem it solves isn't real
TExecution isn't happening→ It's not a lack of motivation — decision-making authority and roles (R&R) are unclear
TIP
Run the 5 Whys against each axis, and it becomes clear which of P, S, or T the real weakness lives in. Weaknesses usually cluster on one axis, and strengthening that axis tends to lift the scores on the other two as well.
Summary.

#Automating the 5 Whys in Discovery

It's hard to push the 5 Whys all the way through on your own, for one simple reason: it's easy to be satisfied with your own answer. An outside perspective is essential. OpenSeed AI review's 15 agents essentially run the 5 Whys automatically — repeatedly asking “why is that true?” against every claim in your business plan to verify the consistency and depth of your evidence.

CTA
After filling out your own 5 Whys worksheet, get an outside check from OpenSeed's AI review. It flags the assumptions, missing evidence, and logical leaps the AI catches — item by item.
광고

Verify Your Essence with an Outside Perspective

15 AI reviewers automatically run the 5 Whys against every claim in your business plan.

🔒 Free during beta · your submission isn't saved

Start Free AI Feedback →

관련 AI 피드백 서비스.

AI 피드백
사업계획서 AI 추천
AI 피드백
예비창업패키지 점검
RELATED · Same categoryStartup Guide
Business Plans With No Unit Economics at All — Why Reviewers Dock Points Immediately2026.07.12 · 8 minBusiness Plan 'Competitive Advantage' — Why an Unsupported Comparison Table Costs You Points in Review2026.07.11 · 8 minBusiness Plan Mistake Log: When You Have a 'Problem Definition' But No Customer Validation2026.07.09 · 7 minThe Business Plan Mistake Log Series — 4 Point-Losing Patterns AI Review Keeps Finding2026.07.09 · 8 min3 Patterns Where the 'Problem → Solution' Logic Breaks Down in Korean Startup Grant Business Plans2026.07.09 · 8 min
← Back to Discovery