methodatlas
Method guideProduct Strategy

OKRs

A practical method guide: clarify prerequisites and materials, understand the complete process, and look up outputs, pitfalls, and stop criteria.

ComplexityMedium
Time1-2 h Setup
Participants2-20
FormatWorkshop + async
MaturityCanonical
Plan OKRs
01

Prerequisite

What needs to be finished first

Complete firstClear scope

Agree the subject, boundary and decision before filling the model.

A broad or mixed scope produces a misleading model.
Complete firstAccess to relevant evidence

Bring source material and people who know the work; distinguish facts from assumptions.

Unverified interpretations become false certainty.
02

Preparation

What needs to be ready before start

Materials

Shared visual workspace, source evidence, and an agreed decision question.

People / roles

Team lead, team members, dependency owners, organizational sponsor.

Pre-read

Collect existing data, examples, constraints and relevant stakeholder perspectives.

Time needed

2–4 h to draft a team set; align dependencies and check-ins separately.

Setup

Set a bounded cycle and connect team focus to organizational direction. Write a concise, meaningful Objective that states the desired change. Define measurable outcome Key Results with baselines, targets, units and data sources. Name owners and distinguish initiatives (work) from Key Results (outcomes). Review signals regularly; discuss confidence, blockers and learning, then close the cycle.

03

Core question

The one question this method answers

What measurable outcome will this team achieve in the cycle?

04

Flow

Phases with goal, actions, output and pitfall

Connects a qualitative objective with measurable key results and a recurring review practice.

OKR: objective and outcomes

Fictional worked example

Fictional quarterly OKR: Objective “Make follow-up appointments easy and reliable for patients.” KR1: raise share of follow-ups booked self-serve from 18% to 35%. KR2: reduce bookings requiring staff intervention from 22% to 10%. “Send an SMS link” is an initiative, not a Key Result. Agree metric definition, baseline and data owner before starting.

OKR: objective and outcomes
ScenarioObjectiveKey ResultBaseline → targetInitiative
Objective 1Record an observation or example for this row.Make follow-ups easy and reliableIncrease self-serve bookings18% → 35%Send SMS link

  1. 1. Objective

    Objective 1
    Make follow-ups easy and reliable

  2. 2. Key Result

    Objective 1
    Increase self-serve bookings

  3. 3. Baseline → target

    Objective 1
    18% → 35%

  4. 4. Initiative

    Objective 1
    Send SMS link

Fictional quarterly OKR: Objective “Make follow-up appointments easy and reliable for patients.” KR1: raise share of follow-ups booked self-serve from 18% to 35%. KR2: reduce bookings requiring staff intervention from 22% to 10%. “Send an SMS link” is an initiative, not a Key Result. Agree metric definition, baseline and data owner before starting.

Set goals with OKRs · Google re:Work

  1. 1

    Cycle

    Align cycle and direction

    Goal

    Cycle and alignment

    Inputs for this step

    • Strategy, team mandate and cycle

    Actions

    • Set a bounded cycle and connect team focus to a higher-level priority.

    Output

    Cycle and alignment

    Cycle and alignment

    Quality check

    Can the team explain its contribution?

    Pitfall

    Objectives arrive as an assigned task list. Agree the outcome contribution with the team.

    Timing: Allow time according to scope and evidence; no universal duration.

  2. 2

    Objective

    Write outcome-led Objective

    Goal

    Understandable Objective

    Inputs for this step

    • Desired user or business condition

    Actions

    • Write a focused qualitative statement of the desired state, not a feature or project list.

    Output

    Understandable Objective

    Understandable Objective

    Quality check

    Does it describe an intended impact?

    Pitfall

    Objective is a KPI without meaning or a project name. State the change first, then define its evidence.

    Timing: Allow time according to scope and evidence; no universal duration.

  3. 3

    Key Results

    Measure outcome Key Results

    Goal

    Measurable Key Results

    Inputs for this step

    • Baseline, source, target and period

    Actions

    • Define each KR with an observable metric, baseline, target and source; measure result rather than activity.

    Output

    Measurable Key Results

    Measurable Key Results

    Quality check

    Could another person calculate progress consistently?

    Pitfall

    Launches and delivery dates are used as KRs. List work as initiatives and define the expected outcome as the KR.

    Timing: Allow time according to scope and evidence; no universal duration.

  4. 4

    Review

    Connect initiatives and reviews

    Goal

    Reviewable OKR and initiatives

    Inputs for this step

    • Owners, dependencies and metric cadence

    Actions

    • Separate initiatives from KRs, assign ownership, set review cadence and close the cycle with learning.

    Output

    Reviewable OKR and initiatives

    Reviewable OKR and initiatives

    Quality check

    Can teams influence KRs and see shared dependencies?

    Pitfall

    Targets are pursued despite missing data or changed assumptions. Check instrumentation and revise the hypothesis transparently.

    Timing: Allow time according to scope and evidence; no universal duration.

05

Artifact

What comes out at the end

Sketch: what the artifact looks like

OKRs · Objective and Key ResultsConnect a qualitative objective with measurable results, owners, and review cadence
OKRsThe visual shows a qualitative Objective, three measurable Key Results, plus owner and review cadence.Connect direction and measurabilityThe Objective describes the desired impact, while Key Results make progress inspectable.make measurableownreviewObjectiveCustomers can reach their first outcome without helpOwnerTeam GrowthReviewlearn weeklyKR 1Confidence 0.7Activation from 42% to 55%KR 2Confidence 0.5Time-to-value below 8 minKR 3Confidence 0.4Support questions down 25%
Form

Connects a qualitative objective with measurable key results and a recurring review practice. Record scope, evidence, assumptions, owner and next review in the versioned artifact.

Versioning / ownership

Record scope, date, participants, source version and owner. Note changed assumptions and the reason for each revision.

Tool alternatives
  • Shared whiteboard or paper template
  • Source links, records or measurement data

okr-set-markdown.md

Plan objective setting, ongoing check-ins and review.

OKRs: Worksheet

Question

To be confirmed

Desired outcome

To be confirmed

Scope

Objective cycle Time: Set cycle length to the team cadence, usually several weeks; schedule the workshop and check-ins separately.

Complete this worksheet on paper or in your own document during the work.

Preparation for this scope

Method setup

  • Materials: Shared visual workspace, source evidence, and an agreed decision question.
  • Roles: Team lead, team members, dependency owners, organizational sponsor.
  • Advance information: Collect existing data, examples, constraints and relevant stakeholder perspectives.
  • Overall time needed: 2–4 h to draft a team set; align dependencies and check-ins separately.
  • Setup: Set a bounded cycle and connect team focus to organizational direction. Write a concise, meaningful Objective that states the desired change. Define measurable outcome Key Results with baselines, targets, units and data sources. Name owners and distinguish initiatives (work) from Key Results (outcomes). Review signals regularly; discuss confidence, blockers and learning, then close the cycle.

Prepare for the work steps

Cycle: Align cycle and direction

  • Strategy, team mandate and cycle

Objective: Write outcome-led Objective

  • Desired user or business condition

Key Results: Measure outcome Key Results

  • Baseline, source, target and period

Review: Connect initiatives and reviews

  • Owners, dependencies and metric cadence

OKR: objective and outcomes

ScenarioObjectiveKey ResultBaseline → targetInitiative
Objective 1
  • Objective 1: Record an observation or example for this row.

Key Results describe outcomes; initiatives describe work.

Set goals with OKRs · Google re:Work

Cycle: Align cycle and direction

Expected artifact: Cycle and alignment

Cycle and alignment

Entry:

...

  • Can the team explain its contribution?

Objective: Write outcome-led Objective

Expected artifact: Understandable Objective

Understandable Objective

Entry:

...

  • Does it describe an intended impact?

Key Results: Measure outcome Key Results

Expected artifact: Measurable Key Results

Measurable Key Results

Entry:

...

  • Could another person calculate progress consistently?

Review: Connect initiatives and reviews

Expected artifact: Reviewable OKR and initiatives

Reviewable OKR and initiatives

Entry:

...

  • Can teams influence KRs and see shared dependencies?

Open questions and next steps

...

Method guide: https://methodatlas.meierhoff-systems.de/en/methods/okr/run-sheet

06

Example output

Concrete filled scenario, fictional example

Fictional example for orientation. Counts and timings describe this case and are not universal requirements.

okr-beispiel.md

Concrete filled scenario, fictional example

Fictional quarterly OKR: Objective “Make follow-up appointments easy and reliable for patients.” KR1: raise share of follow-ups booked self-serve from 18% to 35%. KR2: reduce bookings requiring staff intervention from 22% to 10%. “Send an SMS link” is an initiative, not a Key Result. Agree metric definition, baseline and data owner before starting.

07

Pitfalls

Recognize symptoms and steer against them

Quick overview, the full text is in the matching phase in the flow

  1. Align cycle and directionObjectives arrive as an assigned task list.View in phase
  2. Write outcome-led ObjectiveObjective is a KPI without meaning or a project name.View in phase
  3. Measure outcome Key ResultsLaunches and delivery dates are used as KRs.View in phase
  4. Connect initiatives and reviewsTargets are pursued despite missing data or changed assumptions.View in phase
08

Stop criteria

When to pause, resolve prerequisites, or choose another approach

Stop if the decision question or scope is disputed; align it first.
Stop if key inputs are unavailable; list what evidence is needed.
Stop if the group treats assumptions as observed facts.

Method after Andy Grove and Intel. OKRs were coined at Intel by Andy Grove and later widely adapted. Curated with 1 sources.

Sources: Set goals with OKRs · Google re:Work

Flow, timeboxes, and pitfalls are editorially curated practice recommendations based on the listed sources.

Where to go next?

Paper illustration of a branching impact map with a Why goal at the root, actor circles, How behavior changes and What options.
Product Strategy
Impact Mapping

Connects an objective to actors and possible behavior changes.

A paper-based illustration representing North Star Metric with its core stages and visible working result.
Growth
North Star Metric

Derives a leading, continuously observable metric from the objective.

View in playbookClarify Strategic AlignmentMove from scattered goals to a traceable strategy, metrics, and priorities.

Finished the method guide?

Go to the profile for purpose, similar methods, and sources or continue to the next method in the catalog.

Go to profileMore methods