consulting-issue-tree-mece
MECE Issue Tree
Use $ARGUMENTS as initial context.
When to use this skill
- Diagnosing root causes in performance decline or execution failures.
- Structuring strategic questions into mutually exclusive branches.
- Creating a prioritized analysis plan before data deep-dives.
- Aligning teams on problem scope and ownership.
Required inputs
- Problem statement, metric, and baseline.
- Scope boundaries (segment, geography, time horizon).
- Available data and decision deadline.
Workflow
- Convert the request into one decision-oriented problem statement.
- Select tree type: driver, process, option, or hypothesis tree.
- Build 2-3 levels of MECE branches with parallel labels.
More from santos-sanz/lifeskills
pyramid-principle-structured-communication
Structure high-stakes communication with the Pyramid Principle. Use when preparing executive summaries, recommendations, decision memos, or storyline-driven updates that need a clear answer-first flow and defensible support.
52persuasion-cialdini-influence-design
Design ethical persuasion using Cialdini principles with evidence-backed claims. Use when crafting high-impact messages, proposals, or campaigns that require principle-to-proof traceability and channel-specific execution.
52negotiation-voss-tactical-empathy
Prepare and run negotiations using tactical empathy and structured trade design. Use when handling high-stakes salary, vendor, contract, or scope discussions that require strategy-script separation, BATNA/ZOPA framing, and concession guardrails.
31high-agency
Apply George Mack's High Agency approach to founder and leadership execution. Use when ambiguity, blockers, stalled execution, impossible constraints, or cross-functional deadlock require ownership and rapid action.
20consulting-market-competition-analysis
Analyze market size and competitive dynamics with consulting-grade rigor. Use when decisions require TAM/SAM/SOM triangulation, competitor mapping, positioning implications, and uncertainty-aware recommendations.
20consulting-hypothesis-driven-80-20
Build hypothesis-driven workplans with explicit 80/20 prioritization. Use when rapid decision-making requires testing assumptions, ranking opportunities, and focusing on highest-leverage analyses.
19