# MECE, Explained

> What MECE means, where it came from, and when it backfires. With a worked example and a version you can play.

Source: https://www.wavetable.net/frameworks/mece

[Frameworks](https://www.wavetable.net/frameworks)

Structuring thinkingAlso called Mutually exclusive, collectively exhaustive

# MECE

A test for any list: no item overlaps another, and nothing important is missing.

## In one look

1.  1No overlaps.
2.  2No gaps.
3.  3Every item has exactly one home.

It comes from the same desk as the Pyramid Principle: Barbara Minto's, at McKinsey in the 1960s. The pyramid puts the answer first. MECE checks how the reasons underneath it are grouped.

The problem it solves

## Half the sticky notes say the same thing.

"Communication issues," "alignment," "unclear ownership." Several are one problem under different names, and the real cause isn't on the wall at all. A tidy-looking list can overlap and leave gaps at the same time. MECE is the check that finds both.

## Try it yourself

No sign-up, a few minutes. You size a market for the board, and the parts have to add up to exactly 100%.

## The same churn list, fixed

A churn analysis. The first version counts some customers twice and misses others.

-   First versionPricing issuesbecomes Left over price
-   First versionProduct gaps, poor onboardingbecomes Left for a missing feature, or after a failed first 90 days
-   First versionUnhappy customersbecomes Left for reasons outside our control

## Good times to run it

-   Breaking down a problem at the start of a project
-   Options slides where the choices have to be distinct
-   Survey and research categories
-   Splitting work across a team without doubling up

## When to skip it

-   Early, messy exploration, before ideas have settled.
-   Creative work, where the interesting material sits in the overlaps.
-   Fuzzy categories like emotions or motives, which don't separate cleanly.

Teams we've run sessions with:

-   ![Publicis Groupe](https://www.wavetable.net/logos/publicis-groupe.svg)
-   ![SoundCloud](https://www.wavetable.net/logos/soundcloud.svg)
-   ![WeTransfer](https://www.wavetable.net/logos/wetransfer.svg)
-   ![The New York Times](https://www.wavetable.net/logos/nyt.svg)
-   ![Columbia Business School](https://www.wavetable.net/logos/columbia.svg)
-   ![EY](https://www.wavetable.net/logos/ey.svg)
-   ![Havas](https://www.wavetable.net/logos/havas.svg)
-   ![NYC](https://www.wavetable.net/logos/nyc.svg)
-   ![MCI Group](https://www.wavetable.net/logos/mci-group.svg)
-   
-   
-   
-   
-   
-   
-   
-   
-   

## Run it with your team

That was someone else's market. On your own team's list, where every bucket has an owner who likes it, it's harder. We run it as a live session on problems like yours, in small groups with a host.

[Consulting firms](https://www.wavetable.net/for/consulting-firms)[Professional services](https://www.wavetable.net/for/professional-services)

## More frameworks

-   [Communication**Pyramid Principle**Put your answer first, then group the reasons that support it underneath.](https://www.wavetable.net/frameworks/pyramid-principle)
-   [Structuring thinking**First Principles Thinking**Break a problem down to the facts you can check, then reason up from those instead of from what's usually done.](https://www.wavetable.net/frameworks/first-principles)
-   [Communication**SCQA**A four-part opening for any memo, deck or email: what they already accept, what changed, the question that raises, and your answer.](https://www.wavetable.net/frameworks/scqa)
