Knowledge · Strategy & Planning

So What / Why So

So What? / Why So?

📂Strategy & Planning⏱2-min read📊Beginner🔗5 related

What is So What / Why So?

In one line
Two verification questions that work in opposite directions: 'So what does this mean?' lifts an implication out of the facts, and 'Why can we say that?' traces a claim back to its evidence.
⚡ Summary in 3 lines
  • So What = From fact to implication
  • Why So = From claim to evidence
  • Checking for logical leaps in two directions

The first thing that changes when you adopt So What and Why So is the slide title. Noun-phrase titles like 'Monthly Inquiry Trends' and 'Traffic by Channel' become judgment statements like 'Organic traffic is not holding up since the ads stopped.' The moment a title becomes a judgment, the accountability for the report shifts to the presenter. The habit of putting numbers on screen and leaving the interpretation to the audience disappears, and slides the presenter can't explain drop out entirely.

So What has two layers: a summary type that ties scattered facts into one sentence, and an insight type that pushes on to causes and next actions. Reports are usually dull because they stop at the summary type, and risky because they skip the summary type and jump straight to the insight type. Why So comes from the opposite side and asks what kind of evidence there is. You have to distinguish whether it is data, a case, or logical inference, and a claim backed by only one kind of evidence collapses with a single rebuttal. If MECE is a tool for checking items on the same level horizontally, these two questions are tools for checking vertically between levels.

In practice, it works better to fix the standards as numbers. A slide title should be one sentence with a subject and predicate, within 40 characters; each claim should have around three supporting points; and the path from fact to conclusion should not exceed three steps. A single supporting point is circumstantial, and more than five is an ungrouped list. Beyond three steps, the listener loses the ladder. Especially at steps that involve causal inference, distinguish 'it may be because…' from 'it is because…'; the moment you mix inference and certainty in the same tone, Why So becomes a question no one can answer.

The point where things most often go wrong in practice is overshooting on So What. If you leap three rungs at once from 'Inquiries down 15%' to 'The sales organization needs restructuring,' executives start doubting the presenter's intent rather than the evidence, and the discussion drifts into office politics. Conversely, many team leaders use Why So like an interrogation. When the purpose of asking back becomes establishing dominance rather than strengthening the logic, team members start bringing only safe conclusions that won't be challenged from the next report on. The report then reverts to a list of facts.

Courses That Cover This Term · Finance & Strategy
Recommended courses · Recommended instructors · Quick quote
🧮 Mini quote · Based on instructor fees
About KRW 1.2 million (≈ US$900)2-hour talk · up to 20 people · Korean
Get a quote for these requirements →
💡 In plain English
Like climbing a ladder up and down to check for missing rungs — take one rung at a time so you don’t fall.
Why it matters in practice
You need to ask yourself 'So what are we proposing?' before an executive does.
Origin and sources

Introduced by Barbara Minto as a logic-checking device in the Pyramid Principle, and later popularized as the So What/Why So pair through Japanese consulting handbooks.

Source · Barbara Minto, “The Pyramid Principle” · Hanako Teruya, “Logical Thinking” (2001)
An example

Consider a hypothetical case. Company A distributes small appliances in the greater Seoul area, with 310 employees and annual revenue of about KRW 82 billion (≈ US$61,349,700). A 45-slide performance report goes to the monthly sales division meeting, yet in two-hour sessions not a single agenda item was ever decided. When the first-half repurchase rate dropped to 12%, the division head decided to start by fixing how reports are written.

  1. In the first workshop, when Manager Kim of the Sales Planning team reported 'repurchase rate 12%,' Director Choi replied, "So what are you proposing?" and the meeting stalled within 3 minutes.
  2. When the facilitator asked them to rewrite all 45 slide titles as judgment statements of 40 characters or fewer, 31 slides could not be rewritten at all, because they had numbers but no interpretation.
  3. Manager Kim decided to climb just one rung, adding the fact 'zero follow-up proposals within 3 months of completion' to produce a single sentence: 'The lack of follow-up proposals is blocking repurchase.'
  4. When Director Choi asked, "Why can you say that?", the team backed it up with interview records in which 28 of 40 churned customers said they had 'never received any follow-up.'
  5. To avoid mixing inference with certainty, Team Lead Park kept 'it may be…' in the cause statements and picked just three action proposals to collect on the last slide.
  6. Eight weeks later, the regular meeting report had shrunk from 45 slides to 18, decisions per meeting had risen from 0 to 4, and the next quarter’s repurchase rate climbed from 12% to 19%.
Related terms
Training linked to this term
📚Taking Direction and Reporting Skills ProgramNanum Consulting corporate training · In person or onlineView course →
Need in-house training on this topic?
Get a curriculum and quote tailored to your needs right away.
Ask About Training
Last updated 13 Sep 2026 · Reviewed by John Kim

FAQ

Go as far as the point where it connects to action. Stop when 'So what should we do?' comes up. Go higher than that and it becomes an abstract slogan.
Trace it back with Why So. If the evidence does not come immediately when you step down one level, there is logic missing in between.
Rephrase them as questions such as 'So how should we approach it?' or 'What data did you base that judgment on?' and they work collaboratively.