👀You're previewing this lesson for free. It joins your tracked path once you pass Foundations's capstone.
Intuition
Imagine sorting your laundry. If a sock can land in two piles, or some clothes never get a pile at all, you lose things. MECE, Mutually Exclusive, Collectively Exhaustive, is just the laundry rule for ideas: every issue belongs to exactly one bucket, and the buckets together cover the whole pile.
Interviewers do not reward you for knowing the acronym. They reward you for thinking so cleanly that they never spot an overlap or a gap while you talk.
Framework
Mutually exclusive, no issue appears in two branches. If "lower prices" sits under both Revenue and Marketing, your tree leaks.
Collectively exhaustive, the branches add up to the whole problem. A profit tree that forgets costs is not exhaustive.
One cut at a time, slice by a single logic per level (by customer, or by geography, or by cost type), never mixing axes.
Sort it, no overlaps
Clean cut or leaky bucket?
Tap each card to cycle it into a bucket, then grade the board.
1 · Clean MECE cut2 · Leaky or overlapping
Worked Example
Take Netflix deciding whether to raise prices. A MECE split: Revenue = subscribers × ARPU. Subscribers break into new vs. churned; ARPU into plan mix vs. price. No box overlaps, and together they explain every dollar. That is a structure an interviewer can follow without flinching.
A messy tree is a tell. The moment two branches overlap, the interviewer stops trusting your logic.
Contrast with an airline cost case. Weak split: "fuel, staff, operations, and maintenance", "operations" quietly swallows the other three, so every dollar can land in two boxes. Strong split: "I'll cut costs by behavior: fuel (varies with flying), crew and airport fees (vary with the schedule), and aircraft ownership (fixed)." Same airline, same costs, but the second version gives each dollar exactly one home, which is the whole game.
Pause & think
Mid-case you notice your own leak: "pricing" is sitting inside both your Revenue branch and your Competition branch. The interviewer hasn't flagged it. Do you say anything?
In the room
MECE is mostly audible. Announce the cut before the buckets: "I'll slice this one way at a time, revenue versus costs first, then within revenue, price versus volume." After presenting, close the loop explicitly: "Together these cover the whole decision, and nothing sits in two buckets." That single sentence tells the interviewer you checked, most candidates never do. When you choose a cut, say why: "I'm cutting by customer type rather than geography, because this decision hinges on who churns, not where." In the twenty seconds after your buckets land, the interviewer is silently hunting for one overlap or one gap. Every sentence above is you running that hunt first, out loud, before they can.
Pitfalls
Mixing cuts in one level (customer type and region together).
