Skip to content
← All tools

Why

Your roadmap and your opportunity solution tree disagree because they're maintained separately. Write one tree — outcomes, opportunities, solutions, assumptions — and project it two ways: a Causal Tree for discovery, a Delivery Lens for readiness. Same file, so they can't drift.

Causal Tree — trace every solution to the customer opportunity and assumption it relies on.

Start typing — or load an example.

Export
History
Snapshot before each discovery review — compare renders the “what changed” narrative on the Causal Tree

Why one file?

Teresa Torres's Opportunity Solution Tree keeps solutions tethered to customer needs and a desired outcome. The Causal Tree makes that chain legible as an instrument: outcome, opportunity, solution, assumption. Teams otherwise maintain a separate plan and drift: roadmap items lose their why, tested-nowhere solutions quietly become commitments. Here both are projections of the same text, so drift is structurally impossible.

The Delivery Lens is derived from discovery status, never declared: delivering means an active solution, testing means an active bet, and unaddressed means an acknowledged opportunity without a committed solution. It is not an operating roadmap: use Roadmap for delivery commitments and Paths when outcomes could stop, pivot, or expand the work.

The projections also audit each other: solutions with no opportunity ancestry land in a no why lane; committed solutions whose assumptions are all untested get an untested bet badge; a broken assumption on something you're delivering is the loudest flag on the page. Source: Torres, Continuous Discovery Habits.