What is a Key Result in the OKR framework?
A Key Result is a quantitative metric that measures the success of an Objective. It captures the outcome to reach, not the work to ship.
Definition
Key Results are quantitative metrics that define the success of an Objective. They're specific, measurable, achievable, relevant, and time-bound (SMART). Each Objective typically carries 2 to 5 Key Results, used as benchmarks to track progress and surface areas that need attention. They turn an inspiring Objective into outcome-driven signals, not activity-driven ones.
The golden rule: a Key Result measures a change in the real world, not work completed internally. "Ship a new onboarding flow" is a task. "Move activation rate from 32% to 55%" is a Key Result.
The five hallmarks of a strong Key Result
- Measurable, expressed as a number, ratio, or percentage.
- Outcome, not output, capturing a business or user result, not a deliverable.
- Ambitious, pushing the team to rethink the approach, not just execute the existing plan.
- Achievable within the cycle, realistic on the timeframe (usually a quarter).
- At least partially under the team's control, otherwise it's wishful thinking.
Objective vs Key Result vs Initiative: the OKR value chain
The Key Result is the middle link in OKRs. It connects ambition (Objective) to execution (Initiatives). Without a Key Result, an Objective is just a statement; without an Objective, a Key Result is an orphan metric.
| Pillar | Question it answers | Nature | Example |
|---|---|---|---|
| Objective | Where do we want to go? | Qualitative, inspiring | "Become the European benchmark for team cohesion" |
| Key Result | How will we know we've made it? | Quantitative, measurable | "Grow from 200 to 800 active customers in EMEA" |
| Initiative | What are we actually doing to get there? | Action, project, deliverable | "Run a targeted LinkedIn campaign aimed at HRDs" |
The three families of Key Results
Not all Key Results are created equal. Knowing the typology helps you pick the right metric for the right Objective.
| Type | Description | Example | When to use it |
|---|---|---|---|
| Baseline | Absolute target value to reach. | "Reach an NPS of 50" | When you start from a known, stable measurement. |
| Delta | Measures the gap between a starting point and a target. | "Move NPS from 32 to 50" | When you want to make the trajectory and the magnitude of the change visible. |
| Milestone | Binary checkpoint (hit / missed). | "Obtain ISO 27001 certification" | Sparingly. A milestone is often a disguised Initiative. |
Examples of well-crafted Key Results by context
| Context | Objective | Associated Key Results |
|---|---|---|
| Product | "Ship an onboarding experience that feels indispensable within the first week" | • Day-7 activation rate: from 32% to 55% • Share of users completing 3 key actions: from 41% to 70% • Median time-to-value: from 4 days to under 24 hours |
| People / HR | "Make Serendly a place where talent wants to stay and grow" | • eNPS: from +18 to +35 • Annualized regretted turnover: from 14% to under 8% • Internal mobility rate: from 6% to 15% |
| Sales | "Become the obvious partner for HR leaders at European scale-ups" | • ARR booked in the European scale-up segment: from €1.2M to €2.5M • Win rate on HRD-led deals: from 22% to 35% • Median sales cycle: from 78 days to 55 days |
| Marketing | "Own the conversation on managing distributed teams" | • Monthly organic traffic: from 18k to 50k sessions • Share of Voice on target queries: from 8% to 20% • Qualified inbound leads: from 80/month to 200/month |
| Engineering | "Build a platform teams trust to ship fast and sleep at night" | • Lead time for changes: from 6 days to under 24 hours • Change failure rate: from 18% to under 8% • MTTR on P1 incidents: from 2h30 to under 30 minutes |
Baseline, target, source of measurement: the three mandatory columns
A properly framed Key Result carries three pieces of information, never just one. That's what makes it actually steerable:
| Element | Description | Example |
|---|---|---|
| Baseline (starting point) | The value measured at the start of the cycle. Without a baseline, the delta is meaningless. | Current NPS: 32. |
| Target | The value to reach by the end of the cycle, tagged Committed or Aspirational. | Aspirational target: 50. |
| Source of measurement | The tool, the method, and the cadence that produce the measurement. Essential to avoid end-of-cycle arguments. | Source: Delighted, monthly wave, installed base in the European Enterprise segment. |
A properly written KR therefore looks like: "Move European Enterprise NPS from 32 to 50 (Aspirational, source: Delighted monthly)". The baseline and the source matter as much as the target.
Five frequent bad Key Results, and how to fix them
| Bad KR | Why it's bad | Reformulation |
|---|---|---|
| "Ship product v2" | That's an Initiative, not a KR. Measures a delivery, not a result. | "Move M3 retention from 40% to 60% (Aspirational)." |
| "Improve customer satisfaction" | No baseline, no target, no source. Wishful thinking. | "Move Enterprise CSAT from 7.2 to 8.5 out of 10 (Committed, source: Zendesk post-ticket)." |
| "Hit 100k LinkedIn followers" | Vanity metric, disconnected from the business. | "Generate 500 inbound SQLs from LinkedIn (Committed, source: HubSpot)." |
| "Publish 50 blog articles" | Measures the effort, not the result. Output, not outcome. | "Generate 25,000 monthly organic sessions from the blog (Aspirational, source: GA4)." |
| "Get ISO 27001 certified" | Binary milestone. Fine as a Committed KR, but to requalify if tagged Aspirational. | Keep as Committed on the binary milestone, OR pair with "Move self-assessed security maturity from 3.2 to 4.5 out of 5 (Aspirational)." |
Common mistakes to avoid
| Anti-pattern | Example to avoid | Reformulation |
|---|---|---|
| Confusing Key Result and Initiative | "Redesign the checkout funnel" | "Move checkout conversion from 2.1% to 3.5%" (the redesign becomes an Initiative) |
| KR without a baseline | "Improve customer satisfaction" | "Move CSAT from 7.2 to 8.5 out of 10" |
| Vanity metric | "Hit 100k LinkedIn followers" | "Generate 500 inbound SQLs from LinkedIn" |
| Too many KRs per Objective | 8 to 10 KRs per Objective | Cap at 2-5 KRs. Beyond that, focus is diluted. |
| KR outside the team's control | "Land coverage in the FT and the WSJ" | "Land 6 tier-1 articles in national business press" |
| KR that measures effort, not result | "Publish 50 blog articles" | "Generate 25k monthly organic sessions from the blog" |
Serendly insight: the "so what?" test
To check that a KR really is outcome and not output, ask yourself: "if we hit it, does anything actually change for the customer, the user, or the business?"
If the answer is "well, it means we shipped the project", you have a disguised Initiative. If the answer is "yes, it means our customers are more satisfied, we're signing more, our teams are more engaged", you have a real Key Result.
Scoring Key Results: confidence and grade
Key Results are steered continuously, not at the end of the quarter. Two core practices:
| Practice | Cadence | Purpose |
|---|---|---|
| Confidence score (1-10 or 1-5) | Weekly | Surface the team's read on the likelihood of hitting the target, before the numbers show it. |
| Final grade (0.0 to 1.0) | End of cycle | Reflect what was learned, not just what was hit. A score of 0.7 on an ambitious KR is a success. |
The manager's role in steering Key Results
KRs aren't steered in a spreadsheet, they live in conversations. The manager's job is to:
- Guard the quality of the KR at framing time: measurable, outcome, achievable.
- Track the trajectory in weekly or biweekly team reviews.
- Use 1:1s to surface individual blockers and adjust Initiatives.
- Celebrate the learnings, not just the final grades. A missed KR often reveals more than a hit one.
Serendly tools these conversations so they keep OKRs alive in the day-to-day, without overloading managers.
Putting Key Results in place that actually hold up
A Key Result's quality is decided in the conversation that produced it. Let's talk about how to structure those conversations at scale across your organization.
Request a demoImpact on the organization
Key Results turn ambition into a measurable trajectory. They give teams a clear signal on what matters, support trade-offs between Initiatives, and create a shared language to talk about performance. Provided they measure a real outcome and not the effort put in.
Key takeways for Key Result
- Measures a result (outcome), not a deliverable (output).
- Expressed as a clear number, ratio, or percentage.
- Capped at 2-5 per Objective to preserve focus.
- Ambitious but at least partially under the team''s control.
- Ideally framed as a delta with baseline + target.
- Tracked continuously via confidence score, not only at end of cycle.
Curated related readings
- OKR: definition, structure and use of the Objectives and Key Results framework
- What is an Objective in the OKR framework?
- What is an Initiative in the OKR framework?
- Outcome vs Output: measure the result, not the activity
- Confidence score: measuring conviction on a Key Result
- SMART criteria applied to OKRs: Specific, Measurable, Achievable, Relevant, Time-bound
Synonyms for Key Result : Outcome metric; Success indicator; Kr; Result measure;