MECE
Mutually Exclusive, Collectively Exhaustive
What is MECE?
- The principle of dividing with no overlap and no gaps
- A fundamental of logic trees and the Pyramid Principle
- A single, consistent criterion is the key to checking MECE
Once MECE becomes a team’s shared language, the first thing to change is the shape of the questions asked in meetings. Instead of a question like “Why isn’t it selling?”, whose answers scatter in every direction, people ask “Which box is losing numbers?”, and the debate shifts from a clash of opinions won by the loudest voice to a verifiable one: “Is this the right basis for the breakdown?” In reports, the table of contents is the breakdown, so approvers can scan the table of contents alone and spot missing issues before reading the body.
In practice, there are roughly four ways to break a problem down: formula-based (revenue = customers × conversion rate × average order value), process-based (awareness → evaluation → purchase → repurchase), contrast-based (splitting in two, such as internal/external or new/existing), and element-based, which borrows ready-made frameworks like 3C and 4P. The first three rarely produce overlaps by design, but the element-based approach forces your problem into boxes someone else designed, so gaps appear when the framework doesn’t fit. Three to five branches per level and about three levels deep is the most people can handle. A logic tree applies MECE downward to trace causes, while the Pyramid Principle is a writing rule that states the conclusion first and supports it with MECE evidence, so the two work at different levels.
The most common mistake in practice is mistaking MECE for a “perfect breakdown.” Teams spend two weeks drawing a beautiful tree and end up with a report that has no conclusion, or they dump every ambiguous issue into an “Other” box to avoid overlap, and the key point gets buried there. There is another catch: MECE is only a principle for dividing; it doesn’t tell you where to dig. Dig all eight branches to the same depth and the analysis load grows eightfold while no insight is left. It is far more practical to add priority judgment to a breakdown that leaves nothing out than to chase a “complete MECE.”
John KimAuthor of B2B Marketing Design and CEO of Nanum Consulting
Naha JinStartup leadership specialist with a social welfare backgroundThe principle was developed by Barbara Minto, one of McKinsey's first female consultants, while she was formalizing how to write logical documents, and it spread widely through her book The Minto Pyramid Principle. It later became a standard problem-solving technique across the strategy consulting industry.
Let’s look at a hypothetical case: Company A, a mid-sized home appliance maker with 240 employees and annual revenue of about KRW 120 billion (≈ US$89,780,000). The new cordless vacuum it launched last spring reached only 58% of its sales target over six months. Sales said “the price is too high,” marketing said “the ad budget is too small,” and for three weeks the meetings had run in parallel with no resolution.
- At the start of a meeting, Park, a senior manager on the planning team, wrote “Sales = number of exposed customers × purchase conversion rate × average order value” on the whiteboard and set the ground rule: “Today, let’s skip the causes and look only at which box is missing a number.”
- Once the three boxes were filled with real data, impressions were at 112% of plan and average order value at 97%, but only the purchase conversion rate, at 1.8%, was about half the category average. The proposal to increase the ad budget was dropped on the spot.
- While splitting the conversion-rate box into product-page drop-off, cart abandonment, and checkout drop-off, Kim, a manager on the data team, caught that figures from the company’s own online store and from open marketplaces were being counted twice.
- At the review, the head of sales asked, “Where do dealers, which account for 18% of total sales, fit in this diagram?” Park moved the channel axis to the top of the tree and re-split it from the start into online and offline.
- Of the final seven branches, the team spent two weeks on just two: the product detail page and the shopping cart, where the drop-off gap was largest. They closed the other five as 'verified' and decided not to dig further.
- After the team added a spec comparison table and installation guide, the purchase conversion rate rose from 1.8% to 3.1% over eight weeks, and monthly revenue grew from KRW 240 million (≈ US$179,600) to KRW 390 million (≈ US$291,800). Meetings to review report outlines also dropped from two hours to 40 minutes.