MECE Problem Decomposition
Break any problem into buckets that are mutually exclusive and collectively exhaustive so you never miss a possible cause or solution.
- Difficulty
- Easy
- Time to result
- ~days to results
- Steps
- 3
- Confidence
- 80%
When attacking a problem or brainstorming solutions, decompose it into categories that don't overlap (mutually exclusive) and together cover every possibility (collectively exhaustive). Applying MECE at each layer of a problem tree ensures you surface more candidate solutions and gives you and others confidence the analysis is comprehensive.
Origin
MECE is a classic management-consulting framework; Batchu credits it to consultants ('crucified here but it's most Consultants now') and offers it as advice for people earlier in their careers.
Core principles
- 01Split every problem into non-overlapping, all-covering buckets
- 02Apply the split recursively at each layer of the problem
- 03Comprehensiveness prevents missing an important cause
- 04It also builds shared confidence that the analysis is complete
How to run it
- 1
State the problem
Name the specific problem you're solving, e.g. 'revenue growth has slowed.'
- 2
Decompose into MECE buckets
Break it into non-overlapping, exhaustive components: revenue = revenue per customer x number of customers; then decompose each further (which products? new acquisition vs activation vs retention?).
Pro tip Think of it as writing the formula of all the variables that feed the question, then examining each.
- 3
Recurse until causes are isolated
At each layer, exhaust all the possible ways the problem could arise, drilling down until you've located where the change actually happened.
Watch out If your buckets overlap or leave gaps, you'll either double-count or miss the real cause; check both properties at every layer.
In the wild
Batchu walks through it: revenue slowdown decomposes into revenue-per-customer down vs customer count down; customer count decomposes into which products, then into new acquisition vs activation vs retention. Each layer collectively exhausts the possible causes.
→ A structured diagnosis that surfaces every candidate cause and gives confidence nothing important was missed.
Common mistakes
Brainstorming solutions without a comprehensive frame
Without MECE you tend to miss whole categories of cause or solution, and you lack confidence that your analysis is complete.
Building overlapping buckets
If categories aren't mutually exclusive you double-count and confuse the diagnosis; the discipline requires both non-overlap and full coverage at each layer.
Is it for you?
Best for
Analysts, operators, and people early in their careers structuring an ambiguous business problem
Not ideal for
Fast, low-stakes decisions where formal decomposition is heavier than the problem warrants
From the transcript
“so whenever you're trying to like attack a problem and trying to brainstorm Solutions or what have you uh I I really like to remind…”
“at each layer you've collectively exhausted all of the possible ways that this problem could have arrived uh and just having that framework whenever you…”
From the episode
Lessons from scaling Ramp
Sri Batchu (Ramp, Instacart, Opendoor)