Independent and unaffiliated. The skills, prompts, and frameworks referenced on this page are not created by, endorsed by, or affiliated with any consulting or financial-services firm whose methods may be referenced here. They are built on publicly available frameworks and ways of working, and are inspired by how such approaches are used to tackle complex business problems.
MECE issue tree analysis in Claude
MECE stands for Mutually Exclusive, Collectively Exhaustive. It is the structural discipline leading consulting teams use to decompose a business problem before analysis. Each branch must cover a distinct part of the problem space, with no overlap, while all branches together cover the complete space, with no gaps.
In practice, that discipline is hard to maintain under time pressure. Teams list symptoms instead of causes, collapse levels that belong at different depths, or merge branches that should stay separate. A strong issue tree forces those tensions to be resolved before the first hypothesis is tested.
The workflow in this guide encodes that discipline into a repeatable Claude interaction. It complements the broader 21 strategy skills for Claude collection, which covers diagnosis, execution, and stakeholder alignment.
What the workflow does
Use the method as a structured instruction for Claude Opus 4.6. It introduces four specific behaviors that ad-hoc prompting does not reliably produce.
Two-level minimum
Forces a decomposition from problem to drivers to sub-drivers before stopping.
MECE test at each branch
Explicitly checks for overlap between sibling branches and tests whether together they cover the full solution space.
Diagnostic questions per branch
Each branch comes with the key question it answers and the data required to close it.
Assumption flagging
Surfaces untested beliefs embedded in the tree before the analysis begins.
The result is a structured issue tree that can anchor an analytical workplan, executive brief, or written recommendation.
How to use the MECE issue tree method
Describe the problem clearly and provide the business context, scope, and known constraints. Then tell Claude to decompose it to at least two levels, test every branch for overlap and gaps, and flag the evidence needed to close each branch.
Example prompt
"Build a MECE issue tree for the following problem. Decompose it to at least two levels. Apply the MECE test at every branch and flag data gaps or untested assumptions before closing the tree. For each branch, state the diagnostic question and evidence required. Problem: [describe your business problem here]."
Tip
After Claude returns the tree, expand one branch at a time or mark a branch as resolved and ask it to focus on the remaining hypotheses. This supports partial updates without rebuilding the whole tree.
The method pairs well with the consulting-grade problem solving skill, which handles upstream framing before decomposition begins.
When to run it
Run this method at the start of a diagnostic workstream, before writing a hypothesis or assigning analysis. It is most useful when:
When the tree is complete, assign one owner and one evidence request to each unresolved leaf. That turns the structure into a practical workplan rather than a diagram that stops at classification.