talgacapri Why this exists, and what I'd change
Why it exists. Most breakdowns silently double-count or miss a bucket. PMs list "options" or "user segments" without checking that the buckets don't overlap and together cover everything. MECE forces both checks explicitly, every time.
Design tradeoffs.
- Five-step check instead of a gut test. Name the parent, ME test, CE test, math test, exclusion test. Cost: feels procedural for trivial lists. Skip it when there are only two buckets.
- Pre-built MECE structures (user lifecycle, revenue drivers, etc.) are presented as defaults. Cost: biases toward known patterns. A novel domain may need a fresh structure, and the defaults can blind you to it.
- Linked as a "check" into other skills, not enforced. I made the integration a hint inside
/decision-doc,/impact-sizing, and/prd-draft, rather than a gate. Cost: it gets skipped when people are in a rush, which is exactly when they need it most.
What I'd change. Auto-invoke the MECE check silently inside /decision-doc, /impact-sizing, and /prd-draft. Output the MECE result alongside the main artifact, so the structuring discipline happens whether or not the PM remembered.
MECE Problem-Solving Framework
MECE is McKinsey's method for structuring any problem so your analysis has no gaps and no double-counting.
Two rules:
- Mutually Exclusive (ME): Each item fits in exactly one bucket. No overlap.
- Collectively Exhaustive (CE): All buckets together cover everything. No gaps.
When to Apply MECE
| Situation | MECE Question to Ask |
|---|---|
| Defining decision options | Do any two options point to the same outcome? Is there an obvious option missing? |
| Building a driver tree | Does this breakdown account for 100% of the metric with no overlapping causes? |
| Identifying root causes | Can two causes on this list be true simultaneously for the same user? |
| Segmenting users | Can a user fall into two segments? Is there a user type not covered? |
| Prioritizing work | Does this task fit more than one category? Is there work that doesn't fit any? |
| Writing problem statements | Are the listed problems distinct? Together, do they fully describe the problem space? |
The 5-Step MECE Check
Run this on any breakdown or list:
Step 1 — Name the parent. What whole thing are you dividing? (e.g., "all users," "all causes of churn," "all strategic options")
Step 2 — Check ME: Overlap test. Pick any two items. Ask: "Can the same thing belong to both?" If yes, merge or redefine.
Step 3 — Check CE: Gap test. Ask: "Is there anything that doesn't fit into any of these?" If yes, add a bucket or expand scope.
Step 4 — Verify the math adds up. If your buckets are quantified, they should sum to 100% or the whole. If they don't, you have overlap or a gap.
Step 5 — Name any deliberate exclusions. If you're intentionally leaving something out of scope, say so explicitly. ("Out of scope: enterprise customers — separate analysis.")
Common MECE Structures
These proven breakdowns pass the MECE test in PM work:
User lifecycle: New (0-7 days) / Early (8-30 days) / Retained (30+ days) / Churned
Revenue drivers: Volume x Price x Frequency (for transactional products) Users x Activation Rate x Conversion Rate x ARPU (for SaaS)
Churn root causes: Product (feature gaps, usability) / Commercial (pricing, value perception) / External (market, competition, life event)
Decision options: Build / Buy / Partner / Defer
Strategic horizon: Now (0-3 months) / Next (3-12 months) / Later (12+ months)
Problem sources: People / Process / Technology (classic ops breakdown)
Quick MECE Test
After writing any list of categories, run:
"Can I draw a Venn diagram where the circles don't overlap AND together they cover the entire space?"
If yes, you're MECE. If not, find the overlap or gap and fix it.
MECE Failure Modes to Catch
Overlap (violates ME):
- "New users" + "users who signed up this month" (one is a subset of the other)
- "Technical issues" + "bugs" (bugs are a type of technical issue)
- "Mobile users" + "iOS users" (iOS is a subset of mobile)
Gaps (violates CE):
- "Mobile" + "Desktop" (misses tablet, TV, API)
- "Paid users" + "Free users" (misses trial/freemium tier if it exists)
- "Good churn reasons" + "bad churn reasons" (subjective, not a real partition)
Vague buckets (violates both):
- "Other" as a bucket is a smell — usually signals the framework is incomplete
- "Misc" or "Etc." means you haven't finished the breakdown
Output Format
When applying MECE to any breakdown, present it as:
Problem / Metric / Decision: [What you're decomposing]
MECE Breakdown:
├── Bucket A: [Definition] — [What belongs here]
├── Bucket B: [Definition] — [What belongs here]
└── Bucket C: [Definition] — [What belongs here]
ME Check: [Pass / Flag] — [Note any potential overlaps]
CE Check: [Pass / Flag] — [Note any gaps or deliberate exclusions]
If quantified:
Bucket A: X% | Bucket B: Y% | Bucket C: Z% | Total: 100%
Integration Points
MECE applies naturally inside other skills:
/decision-doc— Options must be ME (can't both be chosen) and CE (no better option overlooked)/impact-sizing— Driver tree nodes must be MECE at each level/prd-draft— Root causes and user segments should be MECE/prioritize— Task categories (L/N/O) are already MECE by design; applies when defining sub-buckets/metrics-framework— Leading/lagging indicators should cover the full funnel with no gaps/user-research-synthesis— Themes should be MECE to avoid reporting the same insight twice/write-prod-strategy— Strategic pillars must be MECE so every initiative maps to exactly one
Quick Reference Card
| Check | Question | Fix |
|---|---|---|
| ME: Overlap | "Can the same thing be in two buckets?" | Merge, redefine, or make one a subset explicitly |
| CE: Gap | "Is there anything that fits nowhere?" | Add a bucket, or explicitly exclude and say why |
| CE: Math | "Do the parts sum to the whole?" | Find missing segment or remove overlap |
| ME: Vagueness | "Is 'Other' doing too much work?" | Expand the framework until Other is < 5% |