00 / MECE Framework
Mutually Exclusive, Collectively Exhaustive.
MECE is a two-part test for whether a split is any good: no two branches overlap, and together they cover the whole problem. It's the standard behind every well-structured issue tree, and how MBB consultants judge how you think.
Free to start. No sign-up required.
01 / The Two-Question Test
Check any split against these two questions.
Mutually exclusive?
Could anything reasonably belong to more than one branch? If yes, the split overlaps and isn't MECE yet.
Collectively exhaustive?
Is there something real that doesn't fit any branch? If yes, the split has a gap and isn't MECE yet.
Full definition, examples, and the process for building a MECE split from scratch: What Does MECE Mean? · MECE Framework: How to Build One · MECE Examples
02 / Where It's Used
MECE is the standard behind issue trees.
Every level of a well-built issue tree is a MECE split, and it's the standard case interview answers are judged against at McKinsey, BCG, and Bain. Reading the definition gets you the concept; building your own splits on the issue tree builder is what makes it automatic.
03 / FAQ
FAQ
What does MECE stand for?
Mutually Exclusive, Collectively Exhaustive: a split where no two parts overlap, and together the parts cover the whole problem. See What Does MECE Mean? for the full definition and examples.
How do I check if a framework is MECE?
Ask two questions of the split: could anything reasonably belong to more than one branch (not mutually exclusive), and is there anything real missing from all of them (not collectively exhaustive)? If both answers are no, it's MECE.
Is MECE only used in consulting?
No -- consulting is where the term is most explicit, but the discipline (splitting a problem cleanly, without overlap or gaps) applies anywhere you're structuring a messy problem: planning, research, product decisions, writing.