# Objectives and Key Results

Objectives and Key Results connect a meaningful qualitative goal with measurable outcomes that show whether progress actually occurred.

- Type: framework
- Domain: Data, experimentation & growth
- Level: Foundational
- Last reviewed: 2026-09-21
- Original: [Soroush’s Product Wiki](<https://wiki.soroush.uk/topic/objectives-and-key-results/>)

## What it means

Objectives and Key Results, usually shortened to OKRs, are a goal-setting framework. An objective describes a valuable direction in clear qualitative language; a small set of key results defines observable outcomes that indicate achievement. Initiatives are the work attempted to move those results, not the results themselves.

## Why it matters

OKRs can align product, design, engineering, and commercial teams around outcomes rather than a list of promised features. They make assumptions discussable, expose conflicting priorities, and create a review rhythm in which teams can learn whether their work changed customer or business conditions.

## When to use it

Use OKRs for a bounded planning period when a team needs focus across several possible initiatives. They are especially useful when the desired outcome is known but the best solution remains uncertain. Keep routine operations and fixed compliance obligations outside aspirational OKRs.

## How it works

1. Write an objective that names the valuable change, audience, and strategic intent without prescribing a feature.
2. Choose two to five key results with baselines, targets, time boundaries, owners, and unambiguous calculation rules.
3. List initiatives separately so teams may change tactics without quietly changing the intended outcome.
4. Review progress and evidence regularly, including counter-signals and confidence in the underlying data.
5. At the end of the cycle, score results, record learning, and decide what to continue, revise, or stop.

## A practical example

A collaboration product sets the objective “Help new teams reach a useful shared workflow quickly.” Its key results target the percentage creating a project with two collaborators, median time to that milestone, and four-week team retention. The team may test templates or invitations without treating either feature as the goal.

## Where it breaks

OKRs do not supply strategy, prove causality, or make every important contribution measurable. Poorly chosen targets invite gaming and local optimization. Excessive cascading can turn them into task assignment, while grading ambitious and committed goals by one rule can distort incentives.

## Common mistakes

- Writing feature delivery or activity counts as key results.
- Selecting targets without baselines or stable definitions.
- Tying compensation mechanically to scores and encouraging sandbagging.

## Visualization

[View the visualization on the website](<https://wiki.soroush.uk/topic/objectives-and-key-results/#visualization-objectives-and-key-results>)

## Sources

1. [Google's OKR Playbook](<https://www.whatmatters.com/resources/google-okr-playbook>) — What Matters · Creator-associated implementation guide
2. [Understand Team Effectiveness](<https://rework.withgoogle.com/en/guides/understanding-team-effectiveness>) — Google re:Work · Organizational research and guidance

## Related topics

- [Key Performance Indicator](<https://wiki.soroush.uk/topic/key-performance-indicator/>)
- [Metric Tree](<https://wiki.soroush.uk/topic/metric-tree/>)
- [Data-Informed Decision Making](<https://wiki.soroush.uk/topic/data-informed-decision-making/>)
