Practice : Outcome-Based Planning and Review

Purpose and Strategic Importance

Outcome-Based Planning and Review is the practice of focusing delivery efforts on the measurable impact they create, not just the features released. By framing plans and reviews around outcomes, teams align more closely with business goals, user needs, and learning.

This practice supports agility at every level by ensuring decisions are grounded in value, and by enabling regular adaptation based on what’s working—not just what’s delivered.

Description of the Practice

  • Teams define desired outcomes upfront using success criteria, metrics, or OKRs.
  • Sprint goals, initiatives, and roadmap items are framed around problems to solve or value to realise.
  • Progress is assessed based on whether outcomes are being achieved, not just activity completed.
  • Reviews explore not only what was built, but how it moved the needle on user, team, or business outcomes.
  • Outcomes are revisited and refined based on feedback, learning, and changing priorities.

How to Practise It (Playbook)

1. Getting Started

  • Frame backlog items and sprint goals as outcome statements (e.g. “Increase customer activation”).
  • Define what success looks like and how it will be measured before work starts.
  • Use a lightweight format like OKRs or hypotheses to guide discovery and planning.
  • Invite stakeholders into the process of shaping and reviewing intended outcomes.

2. Scaling and Maturing

  • Align programme or portfolio planning with outcome themes or value streams.
  • Use metrics dashboards to review progress at sprint, initiative, and quarterly levels.
  • Include both leading and lagging indicators to assess near- and long-term impact.
  • Retire or pivot work that is not achieving its intended value.

3. Team Behaviours to Encourage

  • Ask “What outcome are we aiming for?” before committing to delivery.
  • Celebrate learning and impact, not just output.
  • Use outcome reviews as a space for reflection, not just demo.
  • Link team metrics and feedback to business or user goals.

4. Watch Out For…

  • Vague or unmeasurable outcomes that can’t guide decisions.
  • Measuring outputs (e.g. tickets closed) and mistaking them for impact.
  • Treating outcomes as static commitments rather than learning goals.
  • Teams being held accountable for outcomes they can’t influence.

5. Signals of Success

  • Planning is focused on value, not volume.
  • Delivery conversations shift from “What did we ship?” to “What did we change?”
  • Stakeholders feel more engaged and aligned through shared goals.
  • Teams regularly reflect on impact and adjust their approach.
  • Backlogs and roadmaps evolve based on what is learned—not just what is left.