Northly
Back to Blogguide

Formulating Key Results: 7 Rules for Measurable Outcomes

Formulating Key Results correctly is an art. Learn the 7 golden rules, avoid typical mistakes, and use our examples from Sales, Marketing, HR, and Engineering.

Martin FörsterMarch 8, 202616 min

Last updated: March 9, 2026

Key ResultFormulierungOKRMessbarkeit
OKR
Cycle
Plan
Execute
Check-in
Review

What Makes a Good Key Result?

A Key Result is the measurable answer to the question: "How do we know we have achieved our Objective?" It does not define what a team does but rather what outcome should result. This difference sounds simple but is the most common stumbling block in OKR formulation.

Good Key Results have five characteristics that distinguish them from classic to-do lists or vague goal formulations:

  • Measurable: Every Key Result contains a number, a percentage, or a clearly defined state. "Improve customer satisfaction" is not a Key Result -- "Increase NPS from 32 to 45" is.
  • Outcome-oriented: Key Results describe a state at the end of the quarter, not activities along the way. "Conduct three customer surveys" is a task. "Increase customer feedback score from 3.2 to 4.1" is an outcome.
  • Influenceable: The team must be able to move the Key Result through its own actions. External factors beyond the team's control turn a Key Result into a gamble.
  • Time-bound: Key Results apply for one OKR cycle -- typically a quarter. The timeframe is implicit but binding.
  • Ambitious: A Key Result that is 100% certainly achievable is too easy. Good Key Results have a 60-70% achievement probability for Moonshot OKRs and 80-100% for Committed OKRs.

Why is formulation so important? Because poorly formulated Key Results undermine the entire OKR process. If Key Results are not measurable, check-ins become opinion discussions instead of data-based assessments. If they describe activities instead of outcomes, the focus shifts from impact thinking to task completion. How to structure the entire OKR formulation process is described in detail in our guide to writing OKRs.

The 7 Golden Rules for Strong Key Results

These seven rules have proven themselves across hundreds of OKR cycles. They help teams formulate Key Results that are clear, motivating, and relevant for steering.

Rule 1: Measurable -- Always with a Number

Every Key Result needs a metric. This can be an absolute number (e.g., "120 new enterprise customers"), a percentage ("Conversion rate from 2.1% to 3.5%"), a monetary amount ("Increase recurring revenue to 500,000 euros"), or a score ("Employee NPS from 28 to 42"). No number, no Key Result.

Rule 2: Outcome-Oriented -- Not Output, but Outcome

Ask yourself: "Is this an activity or an outcome?" If you can start the sentence with "We do X," it is probably an initiative. Key Results begin conceptually with "At the end of the quarter, the following has occurred: ..."

Rule 3: Time-Bound -- One Quarter, One Outcome

Key Results must be achievable within one OKR cycle. If a Key Result realistically requires six months, it is either too large or needs to be broken into sub-steps.

Rule 4: Ambitious but Achievable

The art lies in the balance. Too-easy Key Results demotivate because they present no challenge. Unachievable Key Results frustrate. The sweet spot is where the team says: "This will be hard, but if everything goes well, we can do it."

Rule 5: Independent -- No Causality Chains

Key Results should be independent of each other. If Key Result 2 can only be achieved after Key Result 1 is completed, you have a dependency that can block all progress. Instead, formulate parallel success indicators.

Rule 6: Binary or Metric -- but Never Vague

There are two types: Metric Key Results have a start and target value (e.g., "from 15% to 25%"). Binary Key Results are either fulfilled or not (e.g., "Obtain ISO 27001 certification"). Both are valid as long as the outcome is clearly verifiable. What never works: "Improve customer satisfaction" or "Optimize processes."

Rule 7: Not a Task -- Outcome Instead of Activity

The most important rule for last: A Key Result is not a task and not an initiative. "Publish five blog posts" is a task. "Increase organic traffic from 10,000 to 18,000 monthly visitors" is a Key Result. The blog post is a means to an end -- the Key Result describes the end itself.

Common Mistakes in Key Result Formulation

Even experienced OKR users regularly fall into these traps. The good news: Most mistakes can be fixed with simple corrections.

Mistake 1: Disguising Activities as Key Results

This is the most common mistake of all. Example: "Implement new CRM system" sounds like a Key Result but is a project. The real Key Result would be: "Increase sales pipeline accuracy from 60% to 90%" -- where the CRM is an initiative to achieve this outcome.

Mistake 2: Too Many Key Results per Objective

More than five Key Results per Objective dilutes focus. Ideal is three to five Key Results that together paint a complete picture of success. If you need more, the Objective is probably too broad.

Mistake 3: Not Defining a Baseline

A Key Result like "Increase conversion rate to 5%" is worthless if nobody knows where the conversion rate stands today. Every metric Key Result needs a starting value. Formulate: "Increase conversion rate from 3.2% to 5%."

Mistake 4: Using Vanity Metrics

Page views, download numbers, or social media followers are rarely meaningful Key Results. They measure activity, not impact. Ask instead: "Which metric changes when we are truly successful?" More on the difference between relevant and irrelevant metrics in our KPI vs. OKR comparison.

Mistake 5: Binary Instead of Metric (and Vice Versa)

Some outcomes are inherently binary: "Obtain certification" -- yes or no. Adding an artificial metric (e.g., "Meet 80% of certification requirements") makes them less precise, not better. Conversely, gradual improvements should always be formulated as metrics.

Comparison Table: Good vs. Bad Key Results

Bad Key ResultProblemGood Key Result
Improve customer satisfactionNot measurableIncrease NPS from 32 to 45
Create new onboardingActivity, not outcomeReduce time-to-productivity for new employees from 8 to 4 weeks
Write 10 blog postsTask, not outcomeIncrease organic traffic from 10,000 to 18,000 visits/month
Increase revenueNo number, no baselineIncrease MRR from 120,000 euros to 180,000 euros
Write more testsVague, no metricIncrease code coverage from 45% to 80%
Develop marketing strategyProject, not Key ResultIncrease Marketing Qualified Leads from 200 to 500/month
Be more present on social mediaNot operationalizableIncrease engagement rate on Instagram from 2.1% to 4.5%
Respond faster to ticketsNo baseline, vagueReduce average first response time from 4h to under 1h

Key Result Types: Metric, Milestone, and Binary

Not every Key Result fits the same mold. Depending on the context, different types are appropriate, each with its own strengths and limitations.

Metric Key Results (Value-Based)

Metric Key Results define a starting value and a target value for a quantifiable measure. They are the gold standard because they make gradual progress visible.

Structure: "[Metric] from [starting value] to [target value] [change]"

Examples: - "Increase monthly recurring revenue from 80,000 euros to 120,000 euros" - "Reduce average load time of the web app from 3.2s to under 1.5s" - "Increase employee engagement score from 6.2 to 7.8"

Strengths: Progress is measurable at any time, ideal for weekly check-ins. Motivating because partial successes become visible.

Weaknesses: Requires a reliable data source and a known starting value.

Milestone Key Results (Stage-Based)

Milestone Key Results define multiple sequential stages, each marking progress. They are suited for outcomes that are achieved not continuously but in leaps.

Structure: "Achieve [outcome]: Stage 1 = X, Stage 2 = Y, Stage 3 = Z"

Examples: - "Enter new market: Stage 1 = Market analysis completed, Stage 2 = Pilot partner acquired, Stage 3 = First 10 paying customers" - "Establish data privacy compliance: Stage 1 = Gap analysis, Stage 2 = Action plan implemented, Stage 3 = Audit passed"

Strengths: Good for complex, multi-stage outcomes. Each stage is a clear checkpoint.

Weaknesses: Can become a disguised task list if the stages describe activities instead of outcomes.

Binary Key Results (Yes/No)

Binary Key Results are either fulfilled or not. There is no middle ground. They are suited for outcomes that by nature have a clear endpoint.

Structure: "[Outcome] achieved/completed/obtained"

Examples: - "Obtain ISO 27001 certification" - "Series A funding completed" - "MVP deployed with 50 beta users"

Strengths: Maximum clarity. No room for interpretation.

Weaknesses: No gradual progress measurable. In check-ins, the status remains at 0% until the end and then jumps to 100%.

When to Use Which Type?

SituationRecommended Type
Continuous improvement of a metricMetric
Complex outcome with intermediate stepsMilestone
One-time event or stateBinary
Combination of allMix (recommended: max. 1 binary KR per Objective)

Key Result Examples by Department

Theory is good, practice is better. Here you will find over ten concrete Key Result examples from various business areas. All follow the seven golden rules and are directly adaptable. Find even more department-specific OKR examples in our comprehensive article on OKR examples by department.

Sales

  • "Increase quarterly new business revenue from 280,000 euros to 420,000 euros"
  • "Shorten sales cycle length from an average of 45 days to 30 days"
  • "Increase win rate on enterprise deals from 18% to 28%"

Marketing

  • "Increase Marketing Qualified Leads (MQLs) from 350 to 600 per month"
  • "Reduce cost per acquisition (CPA) from 85 euros to 55 euros"
  • "Increase organic search traffic from 25,000 to 40,000 sessions/month"

Product

  • "Increase feature adoption rate of the new dashboard from 15% to 60% of active users"
  • "Reduce median time-to-value for new customers from 14 to 5 days"
  • "Increase app store rating from 3.8 to 4.5 stars"

HR / People

  • "Reduce voluntary turnover from 18% to below 10% annually"
  • "Reduce time-to-hire for engineering positions from 62 to 35 days"
  • "Increase employee NPS from 22 to 40"

Engineering

  • "Increase deployment frequency from 2x/month to 2x/week"
  • "Reduce mean time to recovery (MTTR) from 4 hours to under 30 minutes"
  • "Increase automated test coverage from 45% to 80% of critical paths"

Customer Success

  • "Increase net revenue retention from 95% to 110%"
  • "Increase average CSAT score in support from 3.6 to 4.4"
  • "Increase onboarding completion rate from 65% to 90%"

Practical tip: Use these examples as a starting point, not a blueprint. Every team should formulate its Key Results based on its own context, its own data, and its own ambition level. A Key Result that was copied rather than self-developed rarely generates real commitment.

Quality Checklist: How to Evaluate Your Key Results

Before you finalize your Key Results, review each one against this checklist. Award 0 (not met), 1 (partially met), or 2 (fully met) for each criterion. A good Key Result achieves at least 12 out of 16 points.

The 8-Point Checklist

1. Measurability (0-2) Does the Key Result contain a clear metric with a target value? Does a reliable data source exist for measurement?

2. Outcome Orientation (0-2) Does the Key Result describe an outcome or an activity (output)? Can it be formulated as "At the end of the quarter, the following has occurred: ..."?

3. Influenceability (0-2) Can the team significantly influence the outcome through its own actions? Or does it primarily depend on external factors?

4. Ambition Level (0-2) Is the Key Result challenging enough to require top performance? At the same time realistic enough not to frustrate?

5. Achievability Within Time Frame (0-2) Is the Key Result achievable within one quarter? Or would it need to be broken into smaller parts?

6. Strategic Relevance (0-2) Does the Key Result visibly contribute to the overarching Objective? Would the Objective still be considered achieved without this Key Result?

7. Clarity of Formulation (0-2) Would every person on the team understand the Key Result the same way? Is there room for interpretation?

8. Independence (0-2) Is the Key Result independent of other Key Results in the same set? Or does one block the other?

Scoring Interpretation

ScoreRatingRecommendation
14-16ExcellentApprove
12-13GoodMake minor adjustments
9-11Needs revisionFundamentally rework
0-8UnusableReformulate completely

This checklist works excellently in peer reviews. Have another team evaluate your Key Results -- the external perspective uncovers blind spots and simultaneously strengthens OKR understanding across the entire organization. Find detailed templates for such reviews in our article on OKR templates.

AI-Powered Key Result Optimization with Northly

Formulating high-quality Key Results is a skill that grows with experience. But what if an intelligent system could accelerate the learning process? This is exactly where AI-powered optimization comes in.

Typical Weaknesses That AI Recognizes Instantly

A well-trained AI analyzes Key Results for patterns that often escape human reviewers:

  • Activity disguise: The AI recognizes when a Key Result is actually a task -- even when it is cleverly formulated as an outcome. Example: "Conduct customer survey with 500 participants" sounds measurable but is an activity. The AI suggests: "Increase customer satisfaction score (CSAT) from 3.4 to 4.2."
  • Missing baseline: When a Key Result names a target value but no starting value, the AI flags the gap and asks for the current status.
  • Inconsistent ambition levels: Within an OKR set, all Key Results should have a similar ambition level. If three Key Results are easily achievable and one is utopian, the AI identifies the imbalance.
  • Duplications across teams: In larger organizations, different teams sometimes unknowingly formulate the same Key Results. The AI identifies overlaps and suggests alignment.

How Optimization Works in Northly

Northly's AI assistant accompanies the entire formulation process:

1. Enter draft: The team formulates its Key Results as usual. 2. Instant analysis: The AI evaluates each Key Result against the quality checklist and shows the score in real time. 3. Improvement suggestions: For each criterion below "good," the AI provides concrete alternative formulations. 4. Historical comparison: Based on past cycles, the system recognizes whether a target value is realistic or whether the team regularly over- or underestimates. 5. Approval: The team decides which suggestions to adopt. The AI supports -- the team decides.

The Impact in Numbers

Companies using AI-powered Key Result optimization report concrete improvements:

  • 35% fewer activity-based Key Results after the first AI-supported cycle
  • 50% faster OKR plannings because formulation discussions become shorter
  • Higher check-in quality because measurable Key Results automatically enable better progress conversations

The AI does not replace the team's thinking -- it accelerates it. Anyone who has internalized the seven golden rules will formulate good Key Results without AI. But those who use the AI as a sparring partner reach high-quality outcomes faster and more consistently.

Martin Förster

Gründer von Northly und OKR-Berater mit über 8 Jahren Erfahrung in der strategischen Unternehmensberatung. Hilft Teams, Strategie und Umsetzung mit Objectives and Key Results zu verbinden.

LinkedIn-Profil →