Consulting

MECE

MECE stands for "mutually exclusive, collectively exhaustive," the principle that a problem breakdown should have no overlaps and no gaps. Each category covers distinct territory, and together the categories cover every possibility. Popularized at McKinsey and often credited to Barbara Minto, it is the foundation of clean case structuring and consulting communication.

What Is MECE?

MECE stands for mutually exclusive, collectively exhaustive, a test applied to any breakdown of a problem into parts. Mutually exclusive means no item belongs in more than one category, so there is no double counting. Collectively exhaustive means the categories together cover every possibility, so nothing falls through the cracks. A breakdown that passes both tests lets an analyst examine each piece independently and trust that the sum equals the whole.

The principle was popularized at McKinsey and is most often credited to Barbara Minto, the former McKinsey consultant who wrote The Pyramid Principle. It has since become the default standard for structured thinking in consulting, and it shows up anywhere problems get decomposed: issue trees, market segmentations, slide storylines, and case interview frameworks.

How to Build a MECE Structure

The most reliable MECE breakdowns come from arithmetic, because math cannot overlap or leave gaps. Profit splits cleanly into revenue minus costs, revenue splits into price times volume, and costs split into fixed and variable. Segmentations work the same way when the dimension is well defined: customers by age band, sales by region, or products by line each produce buckets that are distinct and complete.

Breakdowns fail the test when categories are generated by brainstorming rather than by a single organizing dimension. Splitting customers into students, young professionals, and parents is not MECE: a 26-year-old parent lands in two buckets, and a 70-year-old retiree lands in none. The fix is usually to pick one dimension per layer, such as age first and occupation second, rather than mixing them at the same level.

A Worked Example

Suppose a case asks why an airline's annual profit fell by $50 million. A MECE structure splits the problem into revenue and costs, then splits revenue into price per ticket and passenger volume, and costs into fixed and variable. If the data shows revenue down $30 million and costs up $20 million, the tree accounts for the full $50 million with no double counting, and each branch can be sized and tested on its own.

Drilling further, if passenger volume was flat but average fares fell about 3% on $1 billion of revenue, pricing explains the entire $30 million revenue decline by itself. Contrast that with an unstructured answer that lists fuel prices, competition, and marketing: competition affects both price and volume, fuel sits inside variable costs, and whole categories like fixed costs never get examined.

Why MECE Matters for Interviews and Careers

MECE is arguably the single most tested skill in consulting case interviews at MBB and beyond. When an interviewer asks how a candidate would approach a problem, they are grading whether the framework's buckets overlap or leave obvious gaps, and a non-MECE structure is one of the most common reasons strong candidates get dinged. Practicing issue trees until MECE breakdowns become reflexive is a core part of case prep.

On the job, the same discipline organizes workstreams so that two teams never analyze the same question and nothing important goes unowned, and it shapes communication through the Pyramid Principle, where the supporting arguments under each point should themselves be MECE. The habit travels well beyond consulting: bankers, product managers, and MBA students use it to structure analyses, memos, and interview answers.

Join the free newsletter

A free weekly email on breaking into banking and building your career in finance. Read by 30,000+ people.