What's a simple everyday MECE example?

Splitting a day into morning, afternoon, and evening is MECE: every minute of the day falls into exactly one bucket, and the three buckets together cover the full 24 hours.

What's a MECE example that's often done wrong?

Splitting customers into 'new,' 'loyal,' and 'high-value' looks reasonable but isn't MECE. A new customer can also be high-value, so the buckets overlap.

MECE Examples: 7 Breakdowns That Actually Hold Up

Definitions only go so far — MECE is easier to recognize with examples. Here are seven, from simple to case-interview-level, with a note on why each one actually holds up.

1. Profit = Revenue − Cost

The classic. Revenue and cost are mutually exclusive (a dollar is either money coming in or money going out, never both) and collectively exhaustive (there's no third bucket profit depends on).

2. Revenue = Price × Volume

Any change in revenue traces back to a change in price, a change in volume, or both — nothing else moves revenue. Clean split, one level deeper than the first.

3. A day split into morning, afternoon, evening

Every minute of the day falls into exactly one segment, and the three segments cover the full 24 hours. No overlap, nothing left over.

4. Customers: new vs. existing

Splits cleanly if "new" and "existing" are defined by one clear cutoff (e.g., first purchase in the last 90 days). It breaks the moment you add a third, fuzzier category like "loyal" that can overlap with either.

5. Costs: fixed vs. variable

A cost either changes with output or it doesn't — no cost is both, and every cost is one or the other. A clean binary split, useful as the second-level branch under "cost" in a profitability framework.

6. Market entry: organic vs. acquisition

Two ways to enter a market — build it yourself, or buy your way in. Mutually exclusive by definition; collectively exhaustive because there's no third practical route into a market.

7. A hiring decision: internal candidates vs. external candidates

Every candidate is either already inside the company or not — a clean split that's often the first branch in a hiring issue tree before splitting further by role fit, cost, and ramp time.

What breaks a MECE split (with an example)

"Customers: new, loyal, high-value" fails the test — a new customer can also be high-value, so the buckets overlap. The fix is to pick one dimension at a time: split by tenure (new vs. existing) as one framework, and separately by value (high vs. low) as another, rather than mixing dimensions into one flat list.

Build your own

Reading examples is a good start; building your own from scratch under a real question is the skill worth practicing. See MECE Framework: How to Build One for the process, then try it yourself — build your first tree →