OKR Framework
An Objective is simply WHAT is to be achieved, no more and no less. Key Results benchmark and monitor HOW we get to the objective. Effective KRs are specific and time-bound, aggressive yet realistic. Most of all, they are measurable and verifiable.
John Doerr's OKR (Objectives and Key Results) framework is the goal-setting system behind Google, Intel, and the Gates Foundation. It separates the inspirational 'what' (Objectives) from the measurable 'how you'll know' (Key Results), creates bidirectional alignment from CEO to individual contributor, and operates on a 0.0–1.0 scoring rubric that makes success undeniable. This skill applies Doerr's specific rules — not generic goal advice — to draft, audit, classify, and cascade OKRs across any level of an organization.
“It's for my engineering team, quarterly. Our big focus is improving API reliability, but honestly when I write it out it always sounds vague.”
Set inspiring objectives, define quantified key results, and finally measure what actually matters
Doerr's OKR framework organizes goal-setting around two tightly defined components: Objectives (qualitative, inspirational, time-bound statements of what you want to achieve) and Key Results (3–5 quantified, outcome-based measures per objective that prove whether the objective was reached). The framework runs on dual cadences — annual OKRs for strategic direction and quarterly OKRs for operational execution — and requires all OKRs to be public and visible organization-wide to enable cascading alignment from company to team to individual. A critical distinction separates Committed OKRs (must be fully achieved, scored 1.0) from Aspirational/Stretch OKRs (moonshots where 0.7 is considered success). Doerr names four organizational benefits he calls the 'Four Superpowers': Focus and Commit to Priorities, Align and Connect for Teamwork, Track for Accountability, and Stretch for Amazing. The companion CFR system (Conversations, Feedback, Recognition) replaces annual performance reviews with continuous OKR-linked dialogue, and OKRs are explicitly separated from compensation to eliminate sandbagging.
Most goal-setting fails because objectives are vague ("improve customer experience") and key results are actually tasks ("run 3 customer surveys"). Without Doerr's strict separation of inspirational objectives from quantified outcome metrics, teams measure effort instead of impact — and never really know if they succeeded. Annual goal cycles get forgotten by Q2 because there's no scoring rubric, no transparency, and no alignment between what leadership wants and what individuals are working on.
Apply Doerr's precise OKR rules — not watered-down goal advice — to produce a quarterly OKR document where every key result is a measurable outcome with a defined target, every objective is genuinely inspiring, and the 0.0–1.0 scoring rubric makes success or failure unambiguous.
- A goal, initiative, or area of focus you're trying to drive results in
- Your role and organizational level (individual, team, company)
- Existing OKRs you want audited or improved (optional)
- The time horizon — quarterly or annual
- A complete, scored OKR set with 3–5 objectives and 3–5 key results each, ready to publish
- Classification of each OKR as Committed (score target: 1.0) or Aspirational (score target: 0.7)
- An audit report identifying anti-patterns: activity-based KRs, vanity metrics, goal bloat, or compensation linkage
- A cascade map showing how your team or individual OKRs connect to higher-level company objectives
Watch the methodology work.
Three specimens from a single real session: the same situation, unaided and calibrated, the full transcript, and the skill answering live in the channel where the work happens.
“You're heading into Q2 planning with a slide that says 'Goals: improve reliability, ship new features faster, reduce churn.' Your team nods in the meeting but nobody's sure what success actually looks like, and by week six everyone is measuring different things — one engineer tracks deployments, another tracks uptime, the PM tracks NPS. At the quarter-end retro, you can't agree whether Q1 was good or not.”
“You open Q2 with a public OKR document: three Objectives, each with four quantified Key Results, each classified as Committed or Aspirational with explicit score targets. At the six-week check-in your team scores each KR on the 0.0–1.0 scale — KR2 is at 0.4, which is a red flag under Doerr's rubric, and you reallocate two engineers before it's too late. At the quarter-end retro, there's no debate: you hit 0.9 on the aspirational KRs and 1.0 on the committed ones.”
The same skill, where the work happens.
No new app to learn. The methodology runs over the WhatsApp Business API, so the answer lands as a reply in the thread you’re already in — same rigour, zero context-switch.
What it does, specifically.
Each capability is a distinct move drawn straight from the source methodology — not a generic assistant guessing.
Objective Drafting
Transforms a vague goal statement into a proper Objective: qualitative, inspirational, action-oriented, and anchored to a time horizon. The skill tests each Objective against Doerr's criteria — it must be significant enough to matter, concrete enough to focus effort, and motivating enough that a team would want to pursue it.
Key Result Conversion
Converts activities, tasks, and vague intentions into proper Key Results: specific, quantified, outcome-based, and falsifiable. Crucially rejects any KR that describes an action rather than an outcome ("launch the feature" becomes "feature adopted by 40% of active users within 90 days").
Committed vs. Stretch Classification
Determines whether each OKR should be classified as Committed (achievable with current resources, must score 1.0) or Aspirational/Stretch (a moonshot requiring breakthrough, where 0.7 is considered success). Misclassification is one of the most common OKR errors — treating stretch goals as committed leads to burnout; treating committed goals as aspirational enables sandbagging.
OKR Audit
Evaluates an existing set of OKRs against Doerr's full criteria and returns a scored assessment with specific remediation. Detects the most common failure modes: output-based KRs masquerading as outcomes, objectives that are actually strategies, too many OKRs diluting focus, and key results that can't be measured until after the quarter ends.
Cascade Alignment
Maps a team's or individual's OKRs to the higher-level Objectives they support, ensuring the 60/40 bidirectional balance Doerr prescribes — where roughly 60% of OKRs originate bottom-up from employees while 40% cascade from leadership priorities. Surfaces misalignment where team work doesn't connect to any company objective.
Graded before it shipped.
Every skill is scored against independent scenarios for methodology fidelity before it goes live — not vibes, a rubric.
Quarterly OKR Document
A complete, publishable OKR set for a role, team, or company — 3–5 Objectives each with 3–5 Key Results, classified as Committed or Aspirational, with scoring targets and a cadence note. Formatted for direct use in a team meeting, board deck, or OKR tracking tool.
OKR Audit Scorecard
A line-by-line evaluation of existing OKRs against Doerr's criteria, with each Objective and Key Result rated on validity, measurability, and classification accuracy. Includes a prioritized list of anti-patterns found and specific rewrites for each failing element.
Cascade Alignment Map
A visual mapping showing how each team or individual OKR traces upward to a department or company Objective. Highlights orphaned OKRs (effort with no strategic connection) and over-concentrated alignment (all eggs in one company bucket).
CFR Check-in Template
A structured quarterly conversation guide built on Doerr's CFR (Conversations, Feedback, Recognition) companion system. Gives managers a concrete agenda for OKR-linked check-ins that replace annual reviews with continuous, forward-looking dialogue.
Grounded in the original work.
Every answer traces back to a real source and the practitioner who wrote it — not a secondhand summary. Here is the source of record.
John Doerr
John Doerr is a venture capitalist at Kleiner Perkins who learned OKRs directly from Andy Grove at Intel in the 1970s and personally introduced the framework to Google in 1999 — when the company was 40 people working out of a garage. His 2018 book 'Measure What Matters' became a New York Times bestseller and documents OKR adoption at Google, Intel, the Gates Foundation, Bono's ONE Campaign, and Adobe. His TED Talk on OKRs has been viewed over 6 million times.
Measure What Matters
Partner at Kleiner Perkins; early Google board member; introduced OKRs to Google in 1999; NYT bestselling author of 'Measure What Matters'; TED Talk with 6M+ views.
Be first to run it.
OKR Framework is being built right now. Leave your email and we’ll tell you the moment it goes live.