OKR (Objectives and Key Results)
A goal-setting framework pairing a qualitative Objective with measurable Key Results, often used alongside Scrum to connect Sprint work to strategy.
What it means
OKRs are not part of Scrum; they originate from Intel and were popularized by Google as a way to align organizational, team, and individual goals around measurable outcomes rather than output.
Many organizations set quarterly OKRs and then use the Product Goal and successive Sprint Goals to translate those OKRs into concrete Scrum Team work, connecting strategy to delivery.
Common mistakes
A common pitfall is treating OKRs as a rigid checklist rather than an aspirational, outcome-oriented target; unlike a Sprint commitment, hitting 70 percent of an ambitious OKR is often considered a success.
Example
An OKR to 'increase activation rate by 15 percent' shapes the Product Goal for the next two months of Sprints.
Illustrative example of an OKR
The following is a made-up example to show the structure. It is not a recommended target.
- Objective: Make it easy for new customers to get value in their first week.
- Key Result 1: Raise the share of new accounts that complete setup within 7 days from 40% to 60%.
- Key Result 2: Cut the median time from sign-up to first completed task from 3 days to 1 day.
- Key Result 3: Reduce onboarding support tickets per 100 new accounts from 12 to 6.
OKRs and the Product Goal
The Product Goal is part of Scrum. It describes a future state of the product and is the commitment for the Product Backlog. The team works toward one Product Goal at a time and it can span many Sprints.
An OKR is an organisational goal-setting format. It usually runs for a fixed period, often a quarter, and may involve several teams or departments. An organisation might use an OKR to express strategy, and the Product Owner might then shape a Product Goal that contributes to it. The two can support each other, but neither replaces the other.
OKRs are optional in Scrum
Scrum does not require OKRs. Many teams use Scrum well with no OKRs at all. If your organisation uses them, keep the link to Scrum light. Let OKRs inform the Product Goal and Product Backlog ordering, and avoid turning Key Results into Sprint tasks or using them to judge individual Developers.
