# OKR Writing > OKRs (Objectives and Key Results) are a goal-setting framework. The form is deceptively simple — one inspirational Objective, three to five measurable Key Results — but most OKRs in the wild are broke Parent: [Writing and Documentation](https://llms-explorer.com/tree/writing-and-documentation/) · 14 facets · 57 facts · page: https://llms-explorer.com/tree/okr-writing/ ## Overview - OKRs (Objectives and Key Results) are a goal-setting framework. The form is deceptively simple - one inspirational Objective, three to five measurable Key Results - but most OKRs in the wild are broken. They are project plans wearing OKR clothing. — [source](https://llms-explorer.com/sources/mdb-context-hub/okr-writing/#overview) - The Objective is qualitative, inspirational, time-bound. — [source](https://llms-explorer.com/sources/mdb-context-hub/okr-writing/#overview) - Each Key Result is measurable - a numerator over a denominator, by a date. — [source](https://llms-explorer.com/sources/mdb-context-hub/okr-writing/#overview) - The KR measures an outcome (value delivered), not an output (work done) and never an input (effort spent). — [source](https://llms-explorer.com/sources/mdb-context-hub/okr-writing/#overview) ## 2. The measurable-KR test: numerator, denominator, deadline - Every KR must answer: — [source](https://llms-explorer.com/sources/mdb-context-hub/okr-writing/#2-the-measurable-kr-test-numerator-denominator-deadline) - Numerator - what is being counted? — [source](https://llms-explorer.com/sources/mdb-context-hub/okr-writing/#2-the-measurable-kr-test-numerator-denominator-deadline) - Denominator - relative to what? — [source](https://llms-explorer.com/sources/mdb-context-hub/okr-writing/#2-the-measurable-kr-test-numerator-denominator-deadline) - Deadline - by when? — [source](https://llms-explorer.com/sources/mdb-context-hub/okr-writing/#2-the-measurable-kr-test-numerator-denominator-deadline) - Fails: "Improve onboarding." (no numerator, no denominator, no deadline) — [source](https://llms-explorer.com/sources/mdb-context-hub/okr-writing/#2-the-measurable-kr-test-numerator-denominator-deadline) - Fails: "Reach 1000 users." (no denominator, no deadline) — [source](https://llms-explorer.com/sources/mdb-context-hub/okr-writing/#2-the-measurable-kr-test-numerator-denominator-deadline) - Passes: "Grow week-1 activation rate from 28% to 45% by 2026-09-30." — [source](https://llms-explorer.com/sources/mdb-context-hub/okr-writing/#2-the-measurable-kr-test-numerator-denominator-deadline) ## 3. OKR vs KPI — different jobs - KPI (Key Performance Indicator) - a steady-state health metric you watch all the time. KPIs run forever. — [source](https://llms-explorer.com/sources/mdb-context-hub/okr-writing/#3-okr-vs-kpi-different-jobs) - OKR - a change goal for a bounded period. Says "we are choosing to push this number from X to Y this quarter." — [source](https://llms-explorer.com/sources/mdb-context-hub/okr-writing/#3-okr-vs-kpi-different-jobs) - A KPI can become a KR if you decide to push it - but the KR must specify the from-to delta and the deadline. — [source](https://llms-explorer.com/sources/mdb-context-hub/okr-writing/#3-okr-vs-kpi-different-jobs) ## 4. Input → Output → Outcome hierarchy - Input - effort, headcount, money spent. ("hired 5 engineers") - never a KR. — [source](https://llms-explorer.com/sources/mdb-context-hub/okr-writing/#4-input-output-outcome-hierarchy) - Output - work produced, artifacts shipped. ("shipped the new dashboard") - almost never a KR. — [source](https://llms-explorer.com/sources/mdb-context-hub/okr-writing/#4-input-output-outcome-hierarchy) - Outcome - change in the world, value delivered. ("dashboard adoption reached 60% of paying teams") - this is what KRs measure. — [source](https://llms-explorer.com/sources/mdb-context-hub/okr-writing/#4-input-output-outcome-hierarchy) - Felipe Castro's "so what?" test: read the KR and ask "so what?" If the answer is another metric (the outcome), the original was an output. — [source](https://llms-explorer.com/sources/mdb-context-hub/okr-writing/#4-input-output-outcome-hierarchy) ## 5. Ambitious-but-not-impossible: the 70% rule - For aspirational / stretch OKRs: — [source](https://llms-explorer.com/sources/mdb-context-hub/okr-writing/#5-ambitious-but-not-impossible-the-70-rule) - Pick a target where your confidence of hitting 100% is about 5 out of 10 (50/50 at draft time). — [source](https://llms-explorer.com/sources/mdb-context-hub/okr-writing/#5-ambitious-but-not-impossible-the-70-rule) - Score around 0.7 on average at the end of the quarter is healthy. — [source](https://llms-explorer.com/sources/mdb-context-hub/okr-writing/#5-ambitious-but-not-impossible-the-70-rule) - Consistently scoring 1.0 means you sandbagged. Scoring < 0.4 means you set fantasy targets. — [source](https://llms-explorer.com/sources/mdb-context-hub/okr-writing/#5-ambitious-but-not-impossible-the-70-rule) - For committed OKRs (operational must-haves - SLAs, compliance deadlines), the target is 1.0 and anything less is a problem. — [source](https://llms-explorer.com/sources/mdb-context-hub/okr-writing/#5-ambitious-but-not-impossible-the-70-rule) ## 6. The rollup pattern across org levels - Company sets 3–5 Objectives for the quarter. — [source](https://llms-explorer.com/sources/mdb-context-hub/okr-writing/#6-the-rollup-pattern-across-org-levels) - Each team picks ~3 Objectives that contribute to the company set. — [source](https://llms-explorer.com/sources/mdb-context-hub/okr-writing/#6-the-rollup-pattern-across-org-levels) - An individual contributor may have 1–2 personal Objectives that map to a team Objective. — [source](https://llms-explorer.com/sources/mdb-context-hub/okr-writing/#6-the-rollup-pattern-across-org-levels) - Key insight: roughly half of OKRs should be set bottom-up. Pure top-down OKRs kill engagement. — [source](https://llms-explorer.com/sources/mdb-context-hub/okr-writing/#6-the-rollup-pattern-across-org-levels) ## 7. Mid-quarter check-in: traffic-light language - Green - on track, no help needed. — [source](https://llms-explorer.com/sources/mdb-context-hub/okr-writing/#7-mid-quarter-check-in-traffic-light-language) - Yellow - at risk, here is what would unblock me. — [source](https://llms-explorer.com/sources/mdb-context-hub/okr-writing/#7-mid-quarter-check-in-traffic-light-language) - Red - will not hit current target. Either re-plan or formally revise the KR. — [source](https://llms-explorer.com/sources/mdb-context-hub/okr-writing/#7-mid-quarter-check-in-traffic-light-language) ## 8. End-of-cycle scoring (0.0 to 1.0) - For each KR, compute the actual / target on its native scale: — [source](https://llms-explorer.com/sources/mdb-context-hub/okr-writing/#8-end-of-cycle-scoring-00-to-10) - Started at 28%, target 45%, ended at 38%. Progress = (38 − 28) / (45 − 28) = 10/17 ≈ 0.59. — [source](https://llms-explorer.com/sources/mdb-context-hub/okr-writing/#8-end-of-cycle-scoring-00-to-10) ## 9. Common bad-OKR patterns - "Ship feature X by date Y" - that is a task, not a KR. The KR is the outcome the feature is supposed to produce. — [source](https://llms-explorer.com/sources/mdb-context-hub/okr-writing/#9-common-bad-okr-patterns) - "Do our normal job well" - operational baselines are KPIs, not OKRs. — [source](https://llms-explorer.com/sources/mdb-context-hub/okr-writing/#9-common-bad-okr-patterns) - Activity counts - "publish 12 blog posts" measures effort, not outcome. — [source](https://llms-explorer.com/sources/mdb-context-hub/okr-writing/#9-common-bad-okr-patterns) - Sandbagged targets - KRs you are 95% confident in. — [source](https://llms-explorer.com/sources/mdb-context-hub/okr-writing/#9-common-bad-okr-patterns) - Too many KRs - more than 5 per Objective is a wishlist. — [source](https://llms-explorer.com/sources/mdb-context-hub/okr-writing/#9-common-bad-okr-patterns) - Set-and-forget - OKRs scored only at quarter end. — [source](https://llms-explorer.com/sources/mdb-context-hub/okr-writing/#9-common-bad-okr-patterns) ## References - John Doerr, whatmatters.com — [source](https://llms-explorer.com/sources/mdb-context-hub/okr-writing/#references) - Christina Wodtke, The Art of the OKR — [source](https://llms-explorer.com/sources/mdb-context-hub/okr-writing/#references) - Felipe Castro, "An OKR should measure the outcome, not the work" — [source](https://llms-explorer.com/sources/mdb-context-hub/okr-writing/#references) ## Where this helps - A team's quarterly planning doc is full of task lists dressed up as OKRs ("Ship feature X by date Y") and needs a test to separate real outcome-based Key Results from disguised project plans. — [source](https://llms-explorer.com/tree/okr-writing/) *(AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.)* - Deciding whether a metric belongs on a KPI dashboard or as this quarter's Key Result — the OKR vs KPI distinction between a steady-state health metric and a deliberate push from X to Y by a deadline. — [source](https://llms-explorer.com/tree/okr-writing/) *(AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.)* - A mid-quarter check-in where a team needs a shared, low-drama vocabulary to signal risk before it becomes a quarter-end surprise. — [source](https://llms-explorer.com/tree/okr-writing/) *(AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.)* - Reviewing an org's full OKR rollup to check it isn't purely top-down, since roughly half should be set bottom-up from teams and individuals. — [source](https://llms-explorer.com/tree/okr-writing/) *(AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.)* ## How to apply this - Run every draft KR through the numerator/denominator/deadline test before it ships to the team, rejecting anything that reads like "Improve onboarding" with no measurable target. — [source](https://llms-explorer.com/tree/okr-writing/) *(AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.)* - Apply Felipe Castro's "so what?" test to a KR candidate — if the answer names another metric, the original was an output, not an outcome, and needs one more turn of the crank. — [source](https://llms-explorer.com/tree/okr-writing/) *(AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.)* - Calibrate stretch-OKR targets to roughly 50/50 confidence at draft time, then track end-of-quarter scores across the team — a pattern of consistent 1.0s signals sandbagging, not success. — [source](https://llms-explorer.com/tree/okr-writing/) *(AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.)* - Score each Key Result at quarter end using actual-minus-start over target-minus-start on its native scale, rather than a gut-feel percentage, so scoring is comparable across KRs with different units. — [source](https://llms-explorer.com/tree/okr-writing/) *(AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.)* ## Antipatterns - Writing a task ("Ship feature X by date Y") and calling it a Key Result instead of naming the outcome the feature is supposed to produce. — [source](https://llms-explorer.com/tree/okr-writing/) *(AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.)* - Setting an operational baseline as an Objective when it's actually a KPI that should be watched continuously, not pushed this quarter. — [source](https://llms-explorer.com/tree/okr-writing/) *(AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.)* - Measuring activity instead of outcome — publishing a fixed number of blog posts counts effort, not the change in the world that effort was supposed to cause. — [source](https://llms-explorer.com/tree/okr-writing/) *(AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.)* - Loading more than five Key Results onto one Objective, turning it into a wishlist instead of a focused bet. — [source](https://llms-explorer.com/tree/okr-writing/) *(AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.)* ## Limitations - The 70%-average-score-is-healthy heuristic only applies to aspirational/stretch OKRs — applying it to committed OKRs (SLAs, compliance deadlines) misreads a real miss as acceptable. — [source](https://llms-explorer.com/tree/okr-writing/) *(AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.)* - The numerator/denominator/deadline test catches vague KRs but doesn't by itself catch a KR that's precisely measurable yet still measures an output instead of an outcome — the "so what?" test is a separate, necessary check. — [source](https://llms-explorer.com/tree/okr-writing/) *(AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.)* - Traffic-light check-ins only work as an early-warning system if teams actually update them mid-quarter — set-and-forget scoring only at quarter end is a common failure mode. — [source](https://llms-explorer.com/tree/okr-writing/) *(AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.)* - The rollup pattern assumes teams have the latitude to set roughly half their OKRs bottom-up — in a highly centralized org, forcing this ratio without real autonomy can produce cosmetic bottom-up OKRs that still originate from a top-down mandate. — [source](https://llms-explorer.com/tree/okr-writing/) *(AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.)* ## Context files - [OKR Writing](https://llms-explorer.com/downloads/sources/mdb-context-hub/okr-writing.md)