Dichotomy
Dichotomy is a thinking approach that splits complex problems in two: find the key dividing line, cut into two sub-problems, and narrow the scope fast.
What It Is
Dichotomy is a thinking approach that splits a complex problem "in two": faced with a large, fuzzy problem, find one key dividing line, cut it into two smaller and clearer sub-problems, then handle each separately.
The underlying logic is simple — the human brain can only process limited information at once. Cutting the problem smaller makes each half understandable and actionable. Like cutting a cake: the whole is daunting, but halved you know where to start.
Example: company revenue is declining with dozens of possible causes. Dichotomy asks first: "Is it a market problem or an internal problem?" One cut, and the investigation scope halves instantly.

Origins and Key Figures
- The idea of dichotomy traces back to ancient Greek dialectics; Plato used the method of division in the Sophist to define concepts by repeatedly halving a large class.
- Ancient Chinese wisdom holds similar thinking — the "one gives birth to two" division mindset in the Tao Te Ching.
- In modern management, McKinsey-style problem breakdown and the binary search algorithm in computer science are engineered applications of dichotomy.
- Key figures: Plato (conceptual division), Descartes (analytical thinking), generations of McKinsey consultants (problem decomposition).
How to Use
- Write down the original problem: turn a vague worry into one clear problem statement.
- Find the first dividing line: ask "what is the most critical binary dimension here?" (e.g., internal/external, grow/cut, now/future).
- Make the cut: split into sub-problems A and B, making sure they are mutually exclusive with no overlap.
- Judge which half matters more: use data or intuition to quickly decide where the problem likely hides.
- Repeat dichotomy on the important half: keep cutting until sub-problems are small enough to act on directly.
- Record the discarded half: don't work on it for now, but don't delete it — retrospectives may reveal a wrong cut.
Case Study
- Background: a SaaS company's renewal rate slid for two quarters, from 92% to 84%.
- Constraint: the customer success team had only 5 people — interviewing all 300 customers was impossible.
- Diagnosis: first cut with dichotomy — "product problem or service problem?" Ticket data showed 70% of churned customers had filed support tickets within 30 days before expiry.
- Action: locked onto the "service" half, second cut — "slow response or unresolved issues?" Data showed average first response of 26 hours vs. a promised 4.
- Phase: phase one fixed response speed (hiring + ticket triage); phase two improved resolution quality.
- Result: renewal rate recovered to 90% two quarters later.
- Metric: average first response time dropped from 26 hours to 3.2 hours.
- Retrospective: spreading 5 people evenly across product and service would have achieved nothing; dichotomy focused limited resources on the sharpest pain.
- Transfer: this "cut broad, then cut narrow" approach transfers to any scenario with limited resources and complex problems — personal time allocation, feature prioritization.
Strengths and Limitations
Strengths:
- Strength: turns chaos into order; a complex problem reveals its structure within minutes.
- Fast decisions: each step only judges between two options, keeping cognitive load minimal.
Limitations and risks:
- Limitation: the world is rarely black and white; forced cuts can lose the middle ground.
- Risk: a wrong first cut sends everything off track (e.g., splitting internal/external when the real difference is new vs. old customers).
- Boundary: fits "find causes, make trade-offs" problems; not suitable for scenarios needing creative divergence.
- Not suitable for: ethical dilemmas needing nuanced trade-offs, highly coupled systemic problems.
- Mitigation: after each cut, ask "is there a third possibility?" — leave an exit for the middle ground.
- Trade-off: dichotomy trades precision for speed — locate fast, refine slowly.
Common Questions
Q: Isn't dichotomy too crude? Reality is never black and white.
A: Dichotomy is a starting point, not the destination. Its value is narrowing scope quickly, not delivering the final answer. After cutting, keep analyzing the chosen half with finer methods.
Q: How do I know the first cut is right?
A: Check whether the two halves are "mutually exclusive and easy to judge." If you still can't tell which half holds the problem, the dimension is wrong — pick another dividing line. Re-cutting is cheap.
Q: How does dichotomy relate to the MECE principle?
A: MECE is the test, dichotomy is the method. After each cut, run the MECE check: do the two halves cover everything? Do they overlap? Only a cut that passes is valid.
Recommended Resources
- Book: The Pyramid Principle — Barbara Minto, the classic on problem decomposition
- Book: Asking the Right Questions — Neil Browne, questioning techniques for critical thinking
- Articles: McKinsey's "problem definition" series, decomposition in consulting practice
Related Methods
Core Quote
Dichotomy: first cut through the chaos, then refine toward precision.