← ClaudeAtlas

mece-frameworklisted

Categorize the factors of a problem so they don't overlap (Mutually Exclusive) and nothing is missed (Collectively Exhaustive). Outputs nested Markdown bullets. Use for problem structuring, "make sure I've thought of everything", or step 1 of a strategic analysis.
ConrayGambit/Strategy-Consultant-5-Consulting-Frameworks · ★ 4 · AI & Automation · score 75
Install: claude install-skill ConrayGambit/Strategy-Consultant-5-Consulting-Frameworks
# MECE Framework ## Concept MECE — **M**utually **E**xclusive, **C**ollectively **E**xhaustive — is the foundation of structured problem solving: - **Mutually Exclusive:** No factor belongs in two categories. - **Collectively Exhaustive:** Every relevant factor is captured. Non-MECE breakdowns look rigorous but aren't — overlapping categories double-count, and missing categories blind you to root causes. ## Required output format Nested Markdown bullets. Top-level bullets are categories in **bold**; nested bullets are the specific factors under each category. ```markdown - **Category 1** - Sub-factor A - Sub-factor B - **Category 2** - Sub-factor C - Sub-factor D ``` ## Defaults & flex points | Default | When to flex | |---|---| | 3–6 top-level categories | If the problem has only 2 real categories, use 2 — don't pad. If it has 7, use 7. | | 2–5 sub-factors per category | Use as many as the problem actually contains. | | Categories specific to the problem | Generic "People/Process/Technology" buckets are a smell — only use them if they genuinely fit. | **Rule that doesn't flex:** the categories must be MECE. Test each one — could a factor reasonably belong to two? Then merge or split. Could relevant factors not fit anywhere? Then add a category. ## Example — logistics **Problem:** A regional courier company's on-time delivery rate fell from 94% to 81% in six months. ```markdown - **Network capacity** - Vehicle fleet utilization (peak hour saturation)