What interviewers mean by MECE
They mean they can see the whole problem, and they can see that you will not count the same thing twice. A MECE structure is a set of branches. Mutually exclusive: a fact belongs in one branch. Collectively exhaustive: a fact that would change the answer is not left outside.
This is the standard McKinsey interviewers name out loud, and every other firm scores the same habit even when they use different words. The structure guide is the order of the answer. MECE is the test you apply to the framework step.
A fast check before you speak
Write the branches, then run two questions:
- Overlap. Could the interviewer file one fact under two headings? If yes, merge or redefine.
- Gap. Is there a way to be wrong that none of the branches would catch? If yes, add that branch or widen one.
A profitability case that splits into price and volume, and forgets cost, is not exhaustive. A digital case that splits into "technology" and "systems" is not exclusive — those are the same bucket.
Examples that hold
- Profit: price, volume, cost. Cost then splits into fixed and variable only after the first cut is clean.
- Market entry: demand, ability to win, economics of entering. Regulation sits inside ability to win unless it is large enough to be its own branch.
- Cloud move: retire or keep, migrate, and the operating model that has to change. Listing six vendors is not a structure.
What gets marked down
A laundry list of topics with no claim. Branches that are really the same idea in different words ("digital", "technology", "innovation"). And a structure so broad that any answer fits inside it. MECE is not a longer list. It is a shorter list that still covers the decision.
Practice it on a live case. The McKinsey library is the strictest place to hear the pushback when a branch overlaps.