Complete firstNorth Star Metric
A North Star Metric or comparable top outcome metric exists to align key results.
Without: Without a top-level metric, OKRs are optimized locally and pull the organization in competing directions.
RunsheetProduct Strategy
OKRs
ComplexityMedium
Time1-2 h Setup
Participants2-20
FormatWorkshop + async
MaturityCanonical
01
Prerequisite
What needs to be finished first
Complete firstImpact Map
An Impact Map or comparable translation from business goals to actor-impact-deliverable chains exists, from which team objectives can be derived.
Without: Without a strategy anchor, OKRs become team wants instead of company priorities, causing misalignment.
02
Preparation
What needs to be ready before start
Materials
OKR template (table or document with columns Objective, Key Result, Baseline, Target, Owner, Confidence), shared document, link to strategy or company bets, history of previous quarter OKRs.
People / roles
One OKR owner per set (team lead or Product lead); two to five team members who will hold key results; optional OKR coach or Chief of Staff for cross-team consistency.
Pre-read
Company-level OKRs of the layer above; lessons learned from last quarter with final score; known external constraints (releases, compliance, hiring); open commitments from running projects.
Time needed
1-2 h setup, plus 30 min reviews every 2 weeks
Setup
Create document with sections header, Objectives, Key Results, owner list, and review cadence. Define cadence in advance (for example every two weeks, Wednesday 30 min). Define confidence scale (for example 1-10 or traffic-light).
03
Core question
The one question this method answers
Which three to five measurable outcomes will the team deliver next quarter, and how can success be recognized objectively?
04
Flow
Marker: Sektion
| Step | Duration | Action | Hint |
|---|---|---|---|
1Section 1: Strategic anchor | 15 min | Place company OKRs and the North Star Metric at the top of the document. Mark which company bets this team directly supports. | If the team cannot be linked to any company bet, either the strategy is unclear or the team is outside focus. Neither is usually resolved inside the OKR workshop. |
2Section 2: Objectives | 20-30 min | Formulate a maximum of three objectives. Each should be an outcome sentence that is inspiring and achievable in 3 months. No outputs, no feature lists. | An objective like "launch Feature X" is an output, not an outcome. Reframe to the user or business outcome the launch should produce. |
3Section 3: Key results | 30-40 min | 2-4 key results per objective, each with baseline (current value), target (quarter end), and source. At least one KR per objective must be a lagging metric. | If all KRs are activity metrics ("10 interviews completed"), the set measures effort rather than impact. Enforce at least one outcome KR per objective. |
4Section 4: Owner and confidence | 10-15 min | Assign one named owner per key result. Record initial confidence on the defined scale. If confidence under 5, trim KR or validate assumptions. | Confidence 9-10 at quarter start is a warning sign; KR is likely too conservative. Aim for start value 5-7. |
5Section 5: Review cadence | 10 min | Set timing and format: check-in every two weeks with confidence update, blockers, and adaptation decisions. Fix mid-quarter review and end-of-quarter retro. | Without fixed cadence, the set dies by week 4. Put date in calendar immediately. |
05
Artifact
What comes out at the end
Form
Structured document or OKR tool entry with header (team, quarter, owner), section per objective with all key results, baseline, target, owner, confidence, measurement link, and review cadence section.
Versioning / ownership
One entry per quarter with date. Close previous quarter with final KR score (0.0-1.0) and archive, not overwrite. Record mid-quarter adjustments in an edit log at section end.
Tool alternatives
- Notion or Confluence page with tables
- Google Sheet with columns and confidence trend
- Dedicated OKR tool like Workboard, Mooncamp, or Tability
- Linear cycles with milestones as key results
okr-set-markdown.md
Template for objectives, key results, confidence, and the review rhythm.
OKR Set
Objective 1
Why is this objective important?
Key Results
- KR1:
- KR2:
- KR3:
Confidence: 0.0-1.0 Owner: ...
Review rhythm
- Weekly check-in:
- Mid-cycle review:
- Final review:
Risks and dependencies
- ...
06
Example output
Concrete filled scenario, fictional example
okr-beispiel.md
Concrete filled scenario, fictional example
OKRs — Product Team "Discovery", Q3 2026
Strategic anchor: Company bet 2, "Double activation of new users".
Objective 1: New users experience the aha moment in their first session.
- KR 1.1: Activation rate (Session 1) from 22% to 38%. Owner: @lisa. Baseline 22%, confidence 6/10. Source: Amplitude.
- KR 1.2: Time-to-first-value from 7 min 40 s to under 3 min. Owner: @ben. Confidence 5/10.
- KR 1.3: NPS of new users on Day 7 from 14 to 30. Owner: @anna. Confidence 4/10.
Objective 2: Onboarding bottlenecks are identified and prioritized.
- KR 2.1: Complete 25 structured onboarding interviews. Owner: @anna. Confidence 8/10.
- KR 2.2: Top-5 drop-off points with hypotheses and prioritized backlog documented. Owner: @lisa. Confidence 7/10.
Review cadence
Every two weeks on Wednesday at 14:00, 30 min, with asynchronous confidence update by Tuesday 18:00. Mid-quarter review on 19.08.2026, end-of-quarter retro on 30.09.2026.
07
Pitfalls
Recognize symptoms and steer against them
Trap
Output instead of outcome
Symptom
Key results are feature lists or delivery dates ("launch Feature X by 15.07.").
What to do
Ask a follow-up question: what user or business result does this output create. This result becomes the KR; the launch stays as initiative behind it.
Trap
Too many objectives
Symptom
Team set has 5+ objectives with 4-5 KRs each, over 20 metrics total.
What to do
Cap to max three objectives and 2-4 KRs; trim excess. What does not fit is either BAU or belongs to next quarter.
Trap
Sandbagging via confidence 9
Symptom
All confidence values start at 8-10 and all targets reach 100%.
What to do
Introduce stretch norm: set targets so average starting confidence is 5-7. Anyone reaching 100% on all KRs aimed too low.
Trap
Missing measurement source
Symptom
A KR has a number, but no one can explain where current value comes from or how it is measured.
What to do
No KR without a named data source (dashboard link, SQL query, tool path). If source must be built first, include source build as a KR or initiative.
Trap
Cadence breaks after 2 weeks
Symptom
First check-in happens, the rest are postponed or forgotten. At quarter end the set is rediscovered.
What to do
Set cadence as recurring calendar series. Confidence update is mandatory asynchronous input before each meeting. One owner escalates inertia.
Trap
Top-down dictation
Symptom
Team hears OKRs in a review meeting and had no participation in writing.
What to do
At least 70% of key results must be written by the team. Strategic anchor can be top-down; outcome translation remains with the team.
08
Stop criteria
Done signals checkable in under a minute
No written company or functional strategy available; anchor is missing.
Team lacks authority over required levers; outcomes are not influenceable.
Current baselines for more than half of KRs not measurable, set becomes speculation.
OKR owner not named or not decision-authoritative, cadence will not be maintained.
Quarter is already more than 50% over; creating OKRs afterward creates compliance documentation.
Team is primarily in maintenance or compliance and OKRs force artificial change.
Finished the runsheet?
Go to the profile for purpose, similar methods, and sources or continue to the next method in the catalog.