METHODS / GOALS, CADENCE, AND OPERATING SYSTEMS / OKRS

FRAMEWORK

OKRs

OKRs, short for Objectives and Key Results, connect a desired change with measurable evidence of progress or completion. The objective states the direction. Key results define the evidence for a set period. Initiatives remain separate as the work expected to influence those results.

REFERENCE What Matters, by John Doerr

WHAT IT HELPS WITH

A leadership or cross-functional team that needs to concentrate on a small number of changes, expose dependencies, and review progress during a defined cycle.

TYPICAL SCOPE Team
SETUP EFFORT Significant
ONE MATERIAL LIMITATION

OKRs cannot supply strategy, reliable data, capacity, or decision authority. A weak measure can redirect effort away from the result it is meant to represent.

WHAT IT IS

How an objective and key results work together.

An objective states the meaningful change a team wants to produce. Key results define measurable evidence of progress or completion by the end of the cycle. Outcome measures are often the most informative, although a team may use a measurable input or output when it is the clearest responsible signal. Initiatives are the projects or actions the team expects to influence those results.

The distinction matters. Completing an initiative proves that work was done. Movement in a key result provides evidence about whether the intended change is happening. A review connects that evidence to decisions about work, capacity, dependencies, targets, or assumptions.

One objective says what should change. A few key results are the numbers that prove it did.

FIT

When OKRs may help.

Consider them when

  • A few changes matter more than the rest of the work during the next planning period.
  • Several teams need one shared definition of the result.
  • The responsible people can influence the result or escalate its dependencies.
  • Leadership will make tradeoffs when the goals expose a conflict in priorities or capacity.

Use a focused method when

  • Leadership has not decided which outcomes matter.
  • The work is a stable recurring obligation better managed through an SOP or KPI.
  • The team lacks the data or authority needed to influence the result.
  • Another goal system is already working and the reason for adding OKRs is unclear.

THE OKR

What each record needs to explain.

HOW TO RUN IT

Use the review to decide what changes next.

01
Set the horizon.
Agree on the cycle and the choices the OKR should support.
02
Choose one material change.
Write an objective that is specific enough for the team to understand and important enough to deserve tradeoffs.
03
Define the evidence.
Create a small set of key results with baselines, targets, dates, definitions, sources, and owners.
04
Separate initiatives from results.
Track the work without treating completion as proof of impact.
05
Challenge the measures.
Check data quality, distortion risk, quality tradeoffs, and external dependencies.
06
Review and decide.
Examine current results, confidence, blockers, and the decisions needed from the team or sponsor.
07
Close the cycle.
Record the final results, material changes, lessons, and what should continue.

EXAMPLE

Making enterprise onboarding more predictable.

A SaaS company wants enterprise onboarding to become more predictable. It measures the share of kickoffs held within five business days, median time to a configured workspace, and the share of customers reaching a live workflow within 30 days. A revised handoff form and onboarding playbook remain initiatives.

A separate quality guardrail tracks severe onboarding escalations. The company sets baselines and targets from its own data rather than copying another team's figures.

KEEP IT USEFUL

Common implementation and leadership considerations.

Common implementation issues

  • Writing a broad slogan instead of a meaningful change.
  • Using completed tasks as the only key results.
  • Approving a target before establishing the baseline and source.
  • Creating more objectives than the organization can support.
  • Changing a target or definition without preserving the reason and approver.
  • Treating the cycle result as a complete performance verdict.

Leadership and behavior considerations

  • Surface cross-team dependencies before assigning accountability for the result.
  • Pair speed or volume results with a relevant quality guardrail.
  • Check whether incentives encourage gaming, concealment, or local optimization.
  • Give outcome owners enough authority to act or a clear path for escalation.
  • Use the review to make tradeoffs. A result update without a decision can become reporting work with no operational effect.

AI AND JUDGMENT

Use AI to prepare the review. People choose the goal, measures, and tradeoffs.

AI can help

  • Check a draft for missing baselines, targets, dates, owners, or sources.
  • Flag key results that read like tasks or initiatives.
  • Collect approved updates and draft a source-linked review summary.
  • Identify stalled results, conflicting definitions, and unresolved dependencies.

People remain responsible for

  • Choosing the objective and deciding why it deserves attention.
  • Approving targets, measures, quality guardrails, and data definitions.
  • Resolving capacity conflicts and cross-functional dependencies.
  • Interpreting the result and deciding what changes at review or close-out.

AI can make a measure sound precise without proving that it represents the intended outcome. Validate the measure, data, and incentives before approving it.

SOURCES

What the sources cover.

Documented professional practice

Practitioner guidance defines the basic relationship among objectives, measurable key results, and initiatives, although OKRs have no single standards body and implementation varies. Recent academic mapping documents practices, benefits, and challenges, while broader goal and progress research provides context for related mechanisms rather than the complete framework.

View sources (4)OpenClose
Microsoft Learn, writing Objectives, Key Results, and Initiatives. Source, accessed August 31, 2026.
Silva and Santos, systematic mapping of academic OKR literature, 2024. Source, checked August 31, 2026.
Harkin and colleagues, progress-monitoring meta-analysis, 2016. Source, checked August 31, 2026.
Kleingeld, van Mierlo, and Arends, group-goal meta-analysis, 2011. Source, checked August 31, 2026.

WHERE IT FITS

What this pairs with.

LAST REVIEWED: AUGUST 31, 2026 Every claim is checked against the source it names, and where the evidence does not support a claim we say so. Spotted a problem? Tell us and we correct it in the open.