What's the fastest way to check if a framework is MECE?

Ask two questions of every pair of branches and the set as a whole: can anything belong to more than one branch (not mutually exclusive), and is there anything real that fits in none of them (not collectively exhaustive)?

Should I always build my own MECE framework instead of using a standard one?

Standard frameworks (profitability, market entry) are useful starting shapes, but the skill worth building is adapting or rebuilding the split when the standard one doesn't quite fit your specific problem.

MECE Framework: How to Build One From Scratch

A MECE framework is just a breakdown of a problem into parts that don't overlap and don't leave anything out (see What Does MECE Mean? if you need the definition first). Building one is a repeatable process, not a flash of insight.

Step 1: Write the question at the top

Every framework starts from one clear question. Vague questions produce vague splits — "how do we grow?" is harder to split cleanly than "how do we grow revenue in our existing markets this year?" Spend a minute sharpening the question before you split anything.

Step 2: Pick a splitting logic

There's usually more than one valid way to split a problem. Common splitting logics:

A formula. Profit = Revenue − Cost. Revenue = Price × Volume. Formulas give you a mutually exclusive split almost for free, since each term is a distinct variable.
A process or timeline. Before, during, after. Acquisition, activation, retention.
A stakeholder or segment. By customer type, by region, by product line.
A binary. Internal vs. external. Controllable vs. uncontrollable.

Pick whichever logic maps most naturally onto your actual question — don't force a formula split onto a problem that's really about stakeholders.

Step 3: Write out the branches, then test them

Write two to four first-level branches. Then run the MECE test on them: could anything fall into two branches? Is anything missing? It's normal to redraw the split two or three times before it holds up.

Step 4: Go one level deeper on the branch that matters

You rarely need every branch at the same depth. Once the top level is MECE, push deeper on whichever branch is most likely to hold the answer — that's what turns a flat framework into a proper issue tree.

Common mistakes

Splitting by example, not by category. "Marketing, sales, and TikTok" isn't MECE — TikTok is a channel within marketing, not a peer category.
Stopping at the first split that sounds right. The first split is rarely MECE on inspection. Test it before you build on top of it.
Going deep before the top level is clean. If your first-level branches overlap, every branch underneath inherits that problem.

Practice building one yourself

Reading examples only gets you so far — the skill is in constructing the split under time pressure, which is exactly what case interviews test. Meceify gives you a blank canvas to build and test MECE frameworks directly: build your first tree →

Related reading: MECE Examples, Why MECE Matters.