5 So's Technique: Trace What Follows
The 5 So's Technique helps you trace consequences from one event by asking So what? in a chain, labeling what must follow versus what might follow, and stopping when the next step is too speculative. It is a forward mirror of 5 Whys, not a forecast license.
Framework Card
- Name:
- 5 So's Technique
- Goal:
- Trace consequences from one event by asking So what? in a chain, labeling must versus might, and stopping when speculation takes over.
- Flow:
- Name the event → Chain So what → Separate must from might → Stop rule → Decision implication
- Best For:
- A small decision that could ripple; A short-term fix that may create a later problem; Risk talk that stays on first-order effects
Why it matters
A team can find a cause, patch it, and still be surprised next month. The patch was a first-order move. The second-order load showed up in another queue. The third-order story was never asked.
5 Whys is built to walk backward. The 5 So's Technique is built to walk forward. Neither one replaces the other. The leak is treating a single “then we are done” as the whole future.
What it is
Start with one event or decision. Ask So what? for a realistic next consequence. Repeat. Later links usually depend on more conditions, so their probability drops. Teaching materials often distinguish must-happen links from might-happen links. Stop when the next event is too unlikely to change the decision, or when you have left the domain you actually know.
Five is a name. Three good links can be enough. Seven weak links are not better.
This is not 5 Whys. It is not Saito’s Purpose, Perspective, Position, Period. It is not a quantitative model.
How it works
A useful pass is one event, a labeled chain, a stop, and an implication.
1. Name the event
One decision or occurrence from the case. Mixing three events blurs the chain.
2. Chain So what?
Each link should be a consequence of the previous one, not a new wish. Stay inside domain knowledge.
3. Separate must from might
Mark links that follow if the event holds versus links that need extra conditions. Might-links need stated assumptions.
4. Stop
End when likelihood collapses, when you leave what you know, or when the next link no longer changes the decision. Do not fill five boxes for the name.
5. Decision implication
State what you will watch, buffer, or refuse to treat as a cheap patch. Without that, you have a story, not a 5 So's.
How it compares
When another lens fits better, or when you need a complementary view, these frameworks do different jobs. They are not interchangeable labels for the same question.
| Framework | What it helps you see | How it differs from 5 So's |
|---|---|---|
| 5 Whys | Backward cause chain | Mirror direction |
| 4Ps Problem-Solving Framework | Purpose, Perspective, Position, Period | Reframe, not a so-what chain |
| Fishbone Diagram | Cause categories | Structure of causes, not forward effects |
| FMEA | Failure modes and effects as a formal system | Heavier method |
| First Principles | Rebuild from facts | Different job than consequence tracing |
The 5 So's Technique is the lens for a forward consequence chain. Other methods help when the question is cause, framing, or formal FMEA.
When to Use This Framework
- A small decision that could ripple. A policy, a price, a hire, a “temporary” workaround.
- A short-term fix that may create a later problem. The patch looks cheap this week.
- Risk talk that stays first-order. The room has named the event and stopped.
Example
A concrete example makes the structure easier to reuse when you are under uncertainty.
Example: “Ship Friday anyway”
A team wants to skip a data-migration check to hit Friday.
Chain (illustrative, not a probability table): Ship Friday. So, known bad rows go live. So, support volume rises Monday. So, the on-call engineer delays the next feature. So, a promised demo slips. Must versus might: bad rows going live may be must if the check is the only filter. Demo slip is might (depends on calendar).
Implication: The cheap patch is not cheap if Monday support is a must-link. The 5 So's did not predict the year. It made a later load visible before Friday.
The textbook free-trade-zone chain (trade zone, then traders, then logistics, then land, then finance) is the same shape: a teaching illustration of ripple, not a measured forecast you should copy as fact.
Takeaway
What 5 So's can help with
- Making second- and third-order effects visible
- Separating must-happen from might-happen
- Stopping a chain before it becomes science fiction
- Complementing a 5 Whys diagnosis with a forward view
What 5 So's cannot replace
- Root cause. 5 Whys walks backward.
- Problem finding. 4Ps Problem-Solving reframes Purpose, Perspective, Position, Period.
- Cause categories. Fishbone groups causes.
- Formal failure modes. FMEA is a structured risk method.
- A forecast model. The chain does not compute probabilities.
Honest scope: 5 So's structures a consequence chain. It does not replace 5 Whys or FMEA, and it should not be sold as prediction.
Frequently asked questions
Until the next link stops changing the decision or becomes guesswork. Five is a name.
Yes. Whys for how it happened. So's for what might follow. Different jobs.
Must: follows if the event holds. Might: needs extra conditions. Label the extras.
You need enough knowledge to stay realistic. If you do not have it, mark the link as assumed and consider stopping.
No. It asks a structured next-effect question. It does not compute a forecast.