Start with a question.
Build your thinking top-down, one MECE split at a time. Guided step by step or with AI.
Open a pre-filled MECE interview in one click, answer 3 short questions, then paste the reply back here.
Build your thinking top-down, one MECE split at a time. Guided step by step or with AI.
Open a pre-filled MECE interview in one click, answer 3 short questions, then paste the reply back here.
Start broad (e.g. Grow revenue vs Decrease costs), one card type per split. Click a card for notes or + to branch.
A driver card is a proposed lever; a Driver tree breaks down a number. Different branches can use different trees. Use a method badge, or Details → Tree type on an inherited branch.
Tell your agent your question, what you want to change and any constraints. It can choose a tree and build it with you.
Select the card where the question changes, then set its approach. That subtree uses it; deeper subtrees with their own approach keep theirs.
Why is profit falling? · Issue tree
├─ What changed in revenue?
│ └─ Revenue = orders × order value · Driver tree
│ ├─ Orders
│ └─ Average order value
└─ What changed in costs?
└─ Overtime may explain the rise · Hypothesis tree
└─ What do payroll records show?Fictional example. The driver branch explains a calculation; the hypothesis branch investigates a possible cause. Check each connection on its own terms. Selecting a method does not convert or validate the reasoning.
To use the wider tree’s approach again, select the subtree’s first card and choose Use parent type.
This type changed elsewhere. Review the latest setting first.
Changed elsewhere. Your draft is kept; review the latest saved version.
Answer in plain English. When ready, AI updates your tree directly on the canvas (Undo stays available).
Pick your goal and stuck lever. We map the high-level MECE branches, attach your notes, and suggest 4 practical moves.
Opens your AI with a pre-filled MECE prompt carrying this tree, then paste its JSON reply back.