Issue tree / hypothesis tree builder
Constructs a MECE issue tree or hypothesis tree from a problem statement, creating the analytical skeleton that organises all subsequent data collection and analysis.
In / outProblem statement + client context → MECE issue tree or hypothesis tree (structured JSON + narrative rationale for each branch)
You might say…
“Without a proper issue tree I'm just doing random analysis and hoping it adds up to something — the tree forces me to define what 'solved' actually means.”
What it does
Decomposes the client question into a MECE issue or hypothesis tree, naming the sub-questions that must be answered to resolve it. Used at the start of analysis to choose the logic structure before any data work begins.
Trigger: Use at the start of the analysis phase after the problem has been scoped; provide the problem statement, client context, and any known constraints.
Recognise the problem?
The primitives are the commodity part. The fastest next step is a conversation about composing them into something that works for you.
Start a conversation