Issue Tree Builder
Break a big problem into smaller parts you can investigate one by one.
Turn a messy problem into one clear question you can actually answer. Answer five short steps. Get a sharp problem statement you can share with your team.
Consultants spend a surprising amount of time on the first step of any project: agreeing exactly what problem they're solving. It feels slow. It saves weeks.
Most stuck problems aren't hard. They're vague. Different people are solving slightly different problems, so every discussion goes in circles. A clear frame gets everyone answering the same question.
A simple and widely used way to frame a problem is to split it into three parts:
Steps 2 and 5 of the tool follow this structure. Steps 3 and 4 add what makes a question answerable: a measurable goal, a deadline, an owner and clear limits.
A good key question is specific, measurable, time-bound, owned, scoped and solution-free. The checklist next to your result tests for each one.
Weak: “How do we fix customer satisfaction?”
Strong: “How can we get customer satisfaction back above 80% by the end of June, given no extra headcount?”
Framing is the first stage of Futureback problem solving: frame, structure, hypothesise, prioritise, analyse, recommend. Once your question is clear, break it into parts with an issue tree, form a best guess at the answer, then focus your analysis on what matters most.
See the full problem-solving process · Read about the Think Better skill
Messy problems feel hard because they're vague, not because they're complicated. Here's how to turn one into a single clear question.
An issue tree breaks one big question into smaller ones until each branch is something you can actually check.