Outcome Thinking

Use this skill when the core problem is that a team is managing work by features, tasks, or delivery dates instead of by behavioral change.

Boundaries

• Use outcomes-based-planning when the task is to rewrite a roadmap, use a journey map, or turn roadmap items into hypotheses.
• Use organizing-for-outcomes when the problem is team structure, backlog trust, cross-functional workflow, or defining "done" for outcome work.
• Use outcomes-driven-transformation when the target of change is internal stakeholder behavior or organizational adoption.

Default procedure

1. Separate the discussion into:
   • impact: business result
   • outcome: human behavior change
   • output: thing the team builds or does
2. Rewrite vague goals into observable user, customer, or employee behaviors.
3. Choose leading indicators that predict the business result instead of only lagging indicators that report it after the fact.
4. Express uncertain beliefs as hypotheses.