MECE examples: how to fix overlaps and gaps in a list

I remember the first time I heard the term MECE. I asked a friend who worked at Bain for feedback on my resume, and she suggested specific changes to make sure it was MECE.

I thought, “What the heck is MECE? And does it even matter outside of consulting?”

I’d soon use that resume to get a job at McKinsey. Learning about MECE probably helped me land an interview, not to mention succeed on the job. But it took me many reps on the job before MECE finally clicked. So this page is mostly examples: a list that looks fine, what’s wrong with it, and the fix. There’s a short quiz at the end to test yourself.

A MECE list has no overlaps, no gaps, and one sorting rule

MECE stands for mutually exclusive, collectively exhaustive. Mutually exclusive means no item fits in two categories. Collectively exhaustive means every item fits somewhere.

A useful test is to ask what single rule sorts the list. Customers by age. Revenue by channel. Tasks by deadline. When a list breaks, it’s almost always because it mixes two rules, and that creates overlaps and gaps at the same time.

Customer segments break when they mix motivations with behavior

A clothing retailer wants to tailor its marketing, and the brand manager proposes these segments:

1. Bargain hunters
2. Fashion-forward shoppers
3. Quality seekers
4. Occasional buyers

They sound reasonable, but a fashion-forward shopper can also be a bargain hunter, and “occasional buyers” is about how often someone shops, not why. That’s two sorting rules in one list. Loyal customers who don’t fit any of the motivations are left out.

Sorting by a single rule, each customer’s main reason for buying, fixes it:

1. Price-driven: mainly motivated by low prices
2. Trend-driven: mainly motivated by the latest fashion
3. Quality-driven: mainly motivated by durability
4. Convenience-driven: mainly motivated by ease of shopping

Each customer now lands in one segment, and the retailer can write one email campaign per segment without arguing over who belongs where. How often people buy becomes a second, separate cut the team can layer on later.

Revenue streams break when one channel is also a customer type

An analyst at a multi-channel business sorts revenue into digital sales, retail sales, and B2B sales. Online sales to businesses land in both digital and B2B, so they get double-counted, and licensing income isn’t anywhere.

The fix is to sort by where the money comes from:

• Online sales: everything sold through the company’s e-commerce site
• In-store sales: everything sold in physical stores
• Wholesale: everything sold to other businesses for resale
• Licensing: fees from other companies using the brand or technology

Now the four numbers add up to total revenue, which is the quickest check that a revenue breakdown is MECE. If they don’t add up, something is missing or counted twice.

Profit and sales trees are MECE by construction

The cleanest MECE structures are built from math. Profit is revenue minus costs, so every change in profit comes from one or the other.

Sales work the same way. If sales fell, the cause has to be fewer customers, customers buying less often, or smaller purchases, because sales equal customers times purchase frequency times average purchase size. Nothing can fall outside those three, and none of them overlaps another. That makes them a natural starting point for an issue tree.

Priority lists break when the levels are fuzzy

Product managers juggle more feature requests than they can build. Sorting them into high, medium, and low priority sounds MECE, but two people will put the same feature in different buckets, and the team spends the meeting debating the labels.

The MoSCoW method gives each bucket a definition:

• Must have: the release fails without it
• Should have: important, but the release works without it
• Could have: nice to include if there’s time
• Won’t have: out of scope for this release

It isn’t called MECE, but it follows the same idea. Every request gets one label, and the “won’t have” bucket makes the list exhaustive by forcing a decision on everything else.

The fix is often to define the group more tightly

Sometimes a list can’t be exhaustive because the group is too broad. “Social media platforms” has hundreds of members, so no short list covers it. “Social media apps with more than a billion users” is a group you can actually list in full. Narrowing the group is often what turns a vague list into a MECE one.

Everyday plans work the same way. Planning a vacation around “relaxing, adventurous, and cultural” activities doesn’t work, because an art museum is both relaxing and cultural. Sorting by where the activity happens is cleaner:

• Outdoor activities: hiking, the beach
• Indoor activities: museums, shows
• Food and drink: restaurants, cooking classes
• Rest: the spa, the pool

Fair warning: you might annoy your friends and family if you say “MECE” out loud on vacation.

Standard business lists usually leak at one category

Many of the lists teams use every day are close to MECE but have one weak spot. Knowing where it is saves an argument later.

MECE is a tool, not a law

Perfect MECE often isn’t possible or necessary. WhatsApp is a messaging app and a social network. A loyal, price-driven customer belongs to two cuts at once. The goal is a list with no overlaps or gaps that matter for the question you’re answering.

What matters is going through the process. Asking “what’s the one rule that sorts this list?” pushes you to sharpen your thinking and find a clearer way to present it.

Test yourself: is this list MECE?

Each list below is one of four things: MECE, overlapping, leaving gaps, or both. Pick an answer to see the explanation.