• Home
  • BVSSH
  • C4E
  • Playbooks
  • Frameworks
  • Good Reads
Search

What are you looking for?

Practice : OKRs Linked to Outcomes

Purpose and Strategic Importance

Objectives and Key Results (OKRs) provide a framework for aligning teams around measurable outcomes rather than outputs. Linking OKRs directly to customer and business outcomes ensures strategy translates into real impact.

Without outcome-linked OKRs, goals risk being activity-based, leading to busyness without value creation.


Description of the Practice

  • Objectives define ambitious, qualitative outcomes.
  • Key Results are measurable indicators of progress.
  • Both are linked explicitly to strategy and value metrics.

How to Practise It (Playbook)

1. Getting Started

  • Train teams in outcome vs output thinking.
  • Create OKRs collaboratively to ensure ownership.
  • Review OKRs quarterly and link them to portfolio goals.

2. Scaling and Maturing

  • Cascade OKRs through portfolio, product, and team levels.
  • Align OKRs to customer feedback loops and value validation.
  • Use OKR retrospectives to improve the process itself.

3. Team Behaviours to Encourage

  • Focusing on value delivered, not volume of work.
  • Transparency in progress towards key results.
  • Courage to set ambitious but realistic objectives.

4. Watch Out For…

  • OKRs framed as tasks or feature lists.
  • Too many OKRs diluting focus.
  • Treating OKRs as rigid contracts.

5. Signals of Success

  • Qualitative: Teams reference OKRs in backlog and roadmap discussions.
  • Quantitative: Increase in measurable outcomes achieved across portfolio.
Associated Standards
  • Outcomes are the basis of success
  • Value is validated continuously
  • Portfolio investments are purposeful

Technical debt is like junk food - easy now, painful later.

Awesome Blogs
  • LinkedIn Engineering
  • Github Engineering
  • Uber Engineering
  • Code as Craft
  • Medium.engineering