You have several things you could work on, so you start by defining the problem in front of you. It feels responsible - name the problem clearly, then solve it. But the problem in front of you is usually the nearest one, not the right one: it’s whatever is loudest, most urgent, or most broken today.
Defined from the present forward, you solve what’s visible. Defined from the outcome backwards, you solve what actually matters. The gap between those two is the most expensive mistake in execution - solving the wrong problem well, and only realising a month in that it was never on the path to what you actually wanted.
The problem in front of you is rarely the one worth solving.
This tool defines the problem from the finish line. You stand in the achieved outcome, work backwards through what had to be true to get there, and land on the one problem that actually blocks you. Start from where you want to end up, and the real one appears.
Imagine this: three problems compete for the team’s attention - a flaky test suite, a slow onboarding flow, a data pipeline gap. Imagine a year from now with the product thriving and work back: the onboarding flow was never the problem - the real blocker was poor activation data, because without it the product could never have improved. The other two were just loud.
You stand in the achieved future - vividly. Not “imagine success” in the abstract. It’s exactly one year from today; the outcome is real: what’s visibly different, what are customers saying, what is the team no longer struggling with? The shift in viewpoint is the whole mechanism; a vague future just becomes ordinary goal-setting.
You work backwards through the chain. From that future: what had to become true for it? What made that true? What had to change before that? Each step walks you back from the outcome toward the present, one link at a time.
You force out the single problem. The chain lands on one problem - the one that had to be solved first for everything else to follow. Not a wishlist of everything that would help; the single problem on the critical path. That’s the output: “the problem we must solve now is X, because without X the outcome is impossible.”
Team ✓ About 20–30 minutes, depending on how many candidate problems are in play and how quickly the future gets vivid. It’s a quick activity with minimal setup.
The time required is indicative and will depend on the size of the team and the number of candidate problems.
The facilitator should read the short facilitation guide first - about 6–8 minutes. It is a downloadable PDF on this page.
Bring a desired outcome and several problems you could plausibly work on - and uncertainty about which one actually matters.
Use it whenever:
You’ve done it well when: the team can name which problem, solved now, is on the critical path to the outcome - and say why the loudest problem wasn’t it.
If left alone, attention fixes on what’s loud now - the urgent, the broken, the obvious - and you define the problem forward from there. That’s present bias: the pull toward whatever’s in front of you, which quietly picks the nearest problem instead of the right one. Standing in the achieved outcome moves your viewpoint: from the finish line, “what had to be true for this to happen?” becomes unavoidable, and the nearest problem is exposed as a distraction. The backward chain does the rest - it walks the outcome back to the single problem that actually blocks it. You’re not being told to “start with the goal.” You’re standing somewhere that makes the real problem obvious.
The people closest to the work. Bring the people who understand both the desired outcome and the candidate problems. Without them, the backward chain becomes speculation instead of discovery.
A clear desired outcome. Something concrete enough to picture clearly - a real future state, not “do well.” The more specific the outcome, the sharper the problem that falls out of it.
Your candidate problems. The several things you could plausibly work on. You don’t need them fully defined; you need them named, so the chain can show which one was actually on the path.
A facilitator who can make the future vivid. The one hard skill this tool needs: transporting the team into a concrete future state, not a vague “imagine success.” If the future stays abstract, the tool collapses into ordinary goal-setting. The capture sheet carries the backward chain.
Validation: ask “if we solved this problem tomorrow, would the outcome become significantly more likely?” If the answer is “not really,” you haven’t found the right problem yet - work the chain again.
Output
Important rules
Planning to facilitate this activity? Access the resources below to get started.