Standard : Outcome Objectives Met (OKRs)

Description

Outcome Objectives Met (OKRs) tracks the percentage of committed objectives that are successfully achieved within a defined timeframe, typically a quarter. It helps teams focus on results over activity and ensures delivery is tied to measurable value.

This measure strengthens the alignment between team delivery and strategic goals, and encourages clarity on how work translates to user and business outcomes.

How to Use

What to Measure

  • Count of committed OKRs (Objectives and Key Results) per cycle.
  • Track how many key results were met or exceeded during the review period.
  • Optionally, assign a confidence or impact score to OKR completion.

Formula

OKRs Met (%) = (Number of Key Results Achieved / Total Key Results Committed) x 100

You may also break this down:

  • By team or product stream
  • By business theme (e.g. growth, retention, efficiency)
  • By objective type (customer vs. internal outcomes)

Instrumentation Tips

  • Ensure OKRs are specific, measurable, and have clear owners.
  • Track OKRs in a shared, visible space (e.g. Confluence, spreadsheets, or OKR software).
  • Standardise scoring: full (1.0), partial (0.5), or unmet (0.0).
  • Supplement with retrospectives to explore outcome achievement quality.

Benchmarks

Ideal benchmark ranges will vary based on ambition, team maturity and cycle length:

Target Range Interpretation
70–100% High performance, with solid planning
40–69% Stretch goals or partial delivery
<40% Misalignment, overreach or blockers

OKRs are not intended to be easy wins—moderate stretch with 60–70% success is often healthy.

Why It Matters

  • Focuses teams on outcomes
    Reinforces delivery as a means to achieve impact, not just finish tasks.

  • Improves strategic alignment
    Ensures teams contribute visibly to organisational goals.

  • Supports planning and prioritisation
    Provides a clear yardstick to evaluate if teams are working on the right things.

  • Builds accountability and learning
    Retrospectives around OKR delivery can surface valuable insights.

Best Practices

  • Align OKRs at multiple levels (organisation, programme, team).
  • Cascade goals but allow team-level autonomy in how to deliver them.
  • Review OKRs regularly and adjust confidence levels mid-cycle.
  • Focus on outcome-based key results (not activity or task completion).
  • Celebrate progress and share learnings from shortfalls.

Common Pitfalls

  • Using vague or immeasurable key results.
  • Focusing on output-based metrics (e.g. “launch feature”) instead of impact (e.g. “increase usage by X%”).
  • Setting too many OKRs, leading to diffusion of focus.
  • Not reviewing OKRs until the end of the quarter.

Signals of Success

  • Teams consistently hit a meaningful percentage of key results.
  • Objectives are tied to real outcomes like adoption, satisfaction or efficiency.
  • Delivery work is clearly traceable to specific OKRs.
  • Stakeholders can see progress toward shared goals throughout the cycle.
  • [[Value Delivered via Working Software]]
  • [[CoE/Agile/Measures/Value Realisation/Feature Adoption Rate]]
  • [[Customer Feedback to Deployment Cycle Time]]
  • [[Team Goal Confidence Scores]]

Aligned Industry Research

  • Measure What Matters (John Doerr)
    Popularised OKRs as a method to align teams and drive outcome thinking at scale.

  • Evidence-Based Management (Scrum.org)
    Encourages setting and evaluating goals that deliver current and future value.

  • Objectives and Key Results (Atlassian, Google)
    Case studies show that clear OKRs improve focus, alignment, and transparency across agile organisations.