OKR: Objectives and Key Results -- Method, Examples, and Implementation Guide

Most OKR implementations don’t fail because of the method. They fail because organizations introduce OKR as a new goal system without retiring the old one — and suddenly run two systems in parallel that reward different things. Felipe Castro, one of the most influential OKR consultants globally, puts it plainly: “OKR is not an employee performance tool. It is a strategic focus framework.”¹ Confuse the two, and you produce a system that punishes teams for missing ambitious targets — thereby destroying the very ambition OKR is supposed to enable.

This article explains where OKR comes from, how to write Objectives and Key Results properly, how to implement the framework in DACH companies, where it hits its limits — and how to connect OKR with innovation management so that innovation doesn’t remain a declaration of intent.

What Is OKR?

OKR stands for Objectives and Key Results. The framework consists of two elements:

• Objective: A qualitative, inspiring directional statement. What do we want to achieve? A good Objective is ambitious, understandable, and motivating — but not measurable.
• Key Results: Quantitative, measurable outcomes that indicate whether the Objective has been achieved. Typically three to five per Objective. Key Results are outcomes, not tasks (outputs).

The critical distinction: A Key Result is not a to-do. “Conduct customer survey” is a task. “Increase Net Promoter Score from 32 to 45” is a Key Result. The task describes what you do. The Key Result describes what changes as a result. This confusion is the most common mistake in OKR formulation — and it has consequences: when Key Results are tasks, progress is measured by whether boxes get checked, not whether impact is created.

Where Does OKR Come From? The Story Behind the Method

From MBO to OKR: Andy Grove and Intel

The intellectual root of OKR is Peter Drucker’s Management by Objectives (MBO, 1954).² Drucker argued that employees need clear goals they help shape in order to work effectively. The problem: in practice, MBO was degraded to an annual target-setting conversation — top-down, bureaucratic, backward-looking.

Andy Grove, CEO of Intel, transformed MBO into a more dynamic system in the 1970s. In his book High Output Management (1983), he described the core principles: goals must be ambitious, progress must be measured frequently, and the system must create transparency across the entire organization.³ Grove initially called his method “iMBOs” (Intel Management by Objectives) before the name OKR took hold.

John Doerr and Google: The Breakthrough

In 1999, John Doerr, then a venture capital partner at Kleiner Perkins, introduced OKR to Google — at a point when the company had 40 employees. Doerr had learned OKR at Intel under Andy Grove and was convinced the framework would help Google maintain focus as the company grew exponentially.⁴

Google has used OKR continuously ever since. Larry Page described the impact: “OKRs have helped lead us to 10x growth, many times over. They’ve helped make our crazily bold mission of ‘organizing the world’s information’ perhaps even achievable.”⁴

In 2018, Doerr published Measure What Matters, which became the standard reference and popularized OKR worldwide. The book documents OKR implementations at Google, Intel, the Gates Foundation, Bono’s ONE Campaign, and numerous other organizations.⁴

The Theoretical Foundation: Locke & Latham

OKR is not just a practitioner framework — it has a solid scientific foundation. Edwin Locke and Gary Latham’s Goal-Setting Theory, developed over 35 years of research and summarized in A Theory of Goal Setting and Task Performance (1990), provides the theoretical basis.⁵ Their central findings:

1. Specific, difficult goals lead to better performance than vague goals (“Do your best”). The effect size is robust: across more than 1,000 studies, performance improvements of 10 to 25 percent were observed compared to non-specific goals.
2. Commitment amplifies the effect. Goals that employees participated in formulating generate higher engagement than imposed goals.
3. Feedback is essential. Goals without regular feedback don’t work — because people can’t assess their own progress.
4. Task complexity moderates the effect. For highly complex tasks (like innovation), teams need learning goals rather than performance goals — “Understand why customers churn” rather than “Reduce churn by 15 percent.”

OKR translates this research into organizational practice: Objectives provide the specific direction, Key Results provide measurable feedback, the quarterly cadence enforces regular review, and team participation in OKR formulation secures commitment.

OKR Structure: How to Write Good OKRs

The Anatomy of a Good Objective

An Objective answers: “Where do we want to go?” It is:

• Qualitative: No numbers in the Objective. The numbers belong in Key Results.
• Inspiring: It should motivate the team to get up in the morning.
• Time-bound: Typically one quarter.
• Ambitious but not absurd: Google distinguishes between “Committed OKRs” (must be achieved at 100%) and “Aspirational OKRs” (60-70% achievement counts as success).⁶

Weak Objective	Strong Objective	Why Better?
Increase revenue	Show our customers that our new service solves their problem	Direction instead of metric, inspiring instead of generic
Improve website	Become the best source of information for service innovation in the DACH region	Ambitious, directional, cross-team
Increase customer satisfaction	Delight customers so much that they actively recommend us	Outcome-oriented, emotional, specific enough

The Anatomy of Good Key Results

A Key Result answers: “How do we know we’ve arrived?” It is:

• Quantitative: Measurable with a clear metric.
• Outcome-oriented: It describes a result, not an activity.
• Ambitious: 60-70 percent achievement on Aspirational OKRs counts as success.
• Within the team’s influence: The team must be able to influence the Key Result — it doesn’t need to control it alone, but its actions must move the value.

Weak Key Result (Output)	Strong Key Result (Outcome)	Why Better?
Conduct 3 customer interviews	Identify three validated customer segments with distinct needs profiles	Result instead of activity
Launch new feature	Increase adoption rate of new feature among existing customers to 40%	Impact instead of delivery
Publish 5 blog articles	Increase organic traffic to service innovation pages by 30%	Impact instead of output

OKR Example: Innovation Program at an Insurance Company

Context: A major DACH insurer wants to systematically build its innovation capability. The innovation team formulated an OKR set for the first quarter:

Company-Level Objective: Become the most innovative insurer in the DACH region.

Team-Level Objective: Prove that our new claims service solves real customer problems.

Key Result	Measurement	Target (Q2)
KR1: Customer Effort Score in new claims process	CES survey after claims filing	from 4.8 to 3.2 (lower = better)
KR2: Cycle time from claims filing to first feedback	System process time	from 72h to 24h
KR3: Share of digitally processed claims	System data	from 12% to 35%
KR4: Referral rate after claims experience	Post-claims NPS survey	from -8 to +15

Why this OKR set works:

• The Objective is qualitative and inspiring.
• The Key Results are outcomes (customer impact), not outputs (features).
• Four Key Results, not eight — the team can track all of them.
• The metric mix: customer satisfaction (CES), process efficiency (cycle time), adoption (digital share), and loyalty (NPS). No single metric can be optimized in isolation without affecting the others.

OKR Cadence: Rhythm and Alignment

The Quarterly Rhythm

OKR operates in quarterly cycles. This fundamentally distinguishes it from annual target agreements:

Phase	Timing	Duration	Activity
OKR Planning	Start of quarter	1-2 days	Set company OKRs, derive team OKRs, ensure alignment
Weekly Check-in	Weekly	15-30 min	Track Key Result progress, identify blockers
Mid-Quarter Review	Mid-quarter	1 hour	Are we on track? Do we need to adjust priorities?
OKR Review	End of quarter	2 hours	Evaluate achievement (grading), document learnings
OKR Retrospective	After review	1 hour	Process improvement: How can we use OKR itself better?

Alignment: Company, Team, Individual

OKR creates transparency across the entire organization. Direction flows top-down, specification bottom-up:

1. Company OKRs set the strategic direction (2-3 Objectives per quarter).
2. Team OKRs translate the direction into team-specific goals. Teams formulate their own OKRs — but must be able to explain how their OKRs contribute to the Company OKRs.
3. Individual OKRs are optional and debated. Google uses them. Many OKR experts advise against them because they risk turning OKR into a performance management system.¹

The alignment trap in DACH companies: In hierarchically structured organizations, “alignment” is often interpreted as “the board sets the goals, the teams execute.” That is MBO, not OKR. Genuine OKR alignment means: teams understand the strategic direction and independently define how they contribute. The difference isn’t semantic — it’s cultural. And it explains why OKR implementations in DACH companies regularly fail in the first quarter: leadership sets Company OKRs, teams wait for instructions, and nobody has explained that they’re now supposed to decide for themselves.

Strategic OKRs: The Annual Layer

Beyond quarterly OKRs, many organizations formulate annual strategic OKRs (also called “MOALs” — Mid-term Goals or Annual OKRs). These set the frame within which quarterly OKRs are formulated. The architecture:

• Annual strategic OKRs: Where do we want to be in 12 months?
• Quarterly OKRs: What is our contribution this quarter?
• Weekly check-ins: Are we on track?

This three-layer structure solves a problem that OKR alone doesn’t address: quarterly goals can tempt organizations to think only in 90-day cycles. Strategic OKRs anchor the long-term course.

Implementing OKR: Step by Step

Phase 1: Select Pilot Teams (Weeks 1-2)

Don’t start with the entire organization. Choose a team that is intrinsically motivated, has good data availability, and whose leader actively supports OKR. Two to three pilot teams are ideal — enough for comparability, few enough for intensive coaching.

Common mistake: The pilot team is the innovation team because “they’re already agile.” Innovation is the wrong pilot — the results are too long-term to become visible within a quarter. Better: an operational team with clear metrics (customer service, sales).

Phase 2: OKR Training (Weeks 2-3)

Every team needs training that conveys three things:

1. What OKR is and what it isn’t. OKR is not a performance review tool, not task management, not a substitute for strategy.
2. How to write good OKRs. Practice the outcome-vs.-output distinction — with real examples from the team’s own work context.
3. How the OKR cadence works. Planning, weekly check-in, review, retrospective.

Phase 3: Write First OKRs (Weeks 3-4)

The pilot teams write their first OKRs. Important: the first round won’t be perfect. That’s the point. OKR is a learning process — the quality of OKRs improves with each quarter.

Quality check for initial OKRs:

• Does each Objective have at most 3-5 Key Results?
• Are the Key Results measurable (not “improve” but “from X to Y”)?
• Are the Key Results outcomes, not outputs?
• Can the team influence the Key Results?
• Are the OKRs ambitious enough that 100% achievement is unlikely?

Phase 4: Run the First Quarter (Weeks 4-16)

Establish weekly check-ins. Conduct the mid-quarter review. At quarter’s end: review (What did we achieve?) and retrospective (How can we use OKR better?).

Phase 5: Scaling (From Quarter 2)

After the pilot quarter: evaluate learnings, adjust the OKR process, onboard additional teams. Full scaling across the entire organization typically takes four to six quarters.

OKR and Innovation: Why the Framework Is Indispensable for Innovation Management

The Problem: Innovation Without Focus

Most innovation programs in DACH companies suffer from a structural problem: they have a budget, a team, and a mandate — but no mechanism to ensure the innovation team works on the strategically most important topics. Innovation metrics measure output (number of ideas, projects in the pipeline), not strategic impact.

OKR solves this problem by coupling innovation to strategic priorities:

Without OKR	With OKR
”We should be innovative"	"This quarter, we prove that our new digital claims service reduces the Customer Effort Score by 30%“
Innovation as an open-ended project with no deadline	Innovation in quarterly sprints with clear outcome expectations
Innovation team works on what’s interesting	Innovation team works on what’s strategically relevant
Success = activity (workshops, prototypes, pitches)	Success = impact (customer behavior, market reaction, learning progress)

OKRs for Innovation Teams: The Learning Goal Distinction

Locke and Latham warn: for highly complex, uncertain tasks, specific performance goals can be counterproductive — they tempt people to pursue known paths rather than explore new ones.⁵ For innovation teams, this means: Key Results must be formulated as learning goals, not performance goals.

Performance Goal (Problematic)	Learning Goal (Better for Innovation)
Launch 3 new services	Validate 3 service hypotheses with real customers
Generate 500,000 euros in revenue with new product	Confirm or refute the 3 most critical assumptions of our business model with market data
Achieve NPS of 50 in the new service	Understand which 3 factors drive referrals in the new service

This distinction isn’t academic. An innovation team at a DACH automotive manufacturer set itself the Key Result “Launch 3 new digital services.” The result: three services went live, but none were used by customers because validation was skipped in order to “hit” the Key Result. A learning goal would have prevented this.

OKR and the Innovation Portfolio

OKR supplements innovation portfolio management with the focus mechanism that many portfolios lack. The architecture:

1. Strategic OKRs (annual): Define which innovation fields the organization invests in.
2. Portfolio OKRs (quarterly): Measure the health of the innovation portfolio (pipeline index, experimentation velocity, innovation rate).
3. Project OKRs (quarterly): Individual innovation projects have their own OKRs that connect to portfolio OKRs.

OKR Compared to Other Methods

Dimension	OKR	KPI	MBO	Balanced Scorecard
Question	What do we focus on this quarter?	Are we operationally healthy?	What should each employee achieve this year?	Are we strategically on course?
Direction	Bidirectional (top-down + bottom-up)	Bottom-up (measurement)	Top-down (mandated)	Top-down (strategy translation)
Cycle	Quarterly	Ongoing	Annual	Annual + quarterly review
Ambition level	60-70% = success (stretch goals)	100% = standard	100% = expectation	100% = expectation
Linked to compensation	No (explicitly decoupled)	Often (bonus trigger)	Yes (target agreement)	Possible (variable)
Strength	Focus, transparency, speed	Operational management	Clarity of expectations	Multidimensional strategic view
Weakness	No strategic framework, quarterly focus	No direction-setting	Bureaucratic, top-down, annual	Can become unwieldy

OKR + BSC: The Optimal Combination

The question “OKR or BSC?” is the wrong question. The Balanced Scorecard provides the strategic framework (four perspectives, Strategy Map, cause-and-effect chains). OKR provides the focus mechanism for execution. The architecture:

• BSC: Defines strategic direction (annual). What goals do we have across financial, customer, process, and learning perspectives?
• OKR: Translates BSC goals into quarterly focus. What is the most important progress this quarter in each perspective?
• KPIs: Measure ongoing operational health. Are our standard processes stable?

For DACH companies that must simultaneously manage long-term strategy cycles and agile innovation projects, this three-layer model isn’t optional — it’s essential.

The Most Common OKR Mistakes

Mistake 1: Too Many OKRs

More than three to five Objectives per quarter destroys focus — and focus is OKR’s primary value. When everything is a priority, nothing is. Google recommends: two to three Objectives per level (company, team), each with three to five Key Results.⁶

In practice: A mid-sized machinery manufacturer introduced OKR and formulated eight Objectives with a total of 34 Key Results in the first quarter. The result: weekly check-ins lasted two hours, no team could keep all Key Results in mind, and after six weeks everyone ignored the OKRs and worked on whatever was urgent.

Mistake 2: Key Results as Task Lists

When Key Results describe tasks instead of outcomes, OKR becomes a disguised project management tool. “Conduct 3 workshops” is not a Key Result. “Identify 3 validated customer segments” is. The test: if you can achieve the Key Result without anything in the world having changed, it’s a task, not an outcome.

Mistake 3: Linking OKR to Compensation

When OKR achievement affects bonuses, teams will set conservative targets — because ambitious targets punish when missed. This destroys OKR’s core: stretch goals where 60-70 percent achievement is a success. Google, Intel, and most successful OKR implementations explicitly decouple OKR from compensation.⁴

Mistake 4: OKR Without Transparency

OKR derives its power from organization-wide transparency. If only the leadership team knows the Company OKRs, the alignment mechanism is missing. Google makes all OKRs — from Larry Page to the intern — visible internally.⁶

Mistake 5: OKR as a Strategy Substitute

OKR doesn’t define what the organization should do strategically. OKR defines what it focuses on to execute the strategy. Without a clear strategy, OKRs become a collection of quarterly wishes with no strategic coherence. In combination with the Balanced Scorecard, this problem is solvable: the BSC provides the strategy, OKR the focus.

Mistake 6: Forcing OKR into the Existing Culture

OKR presupposes a culture where teams autonomously formulate goals, transparency about progress prevails, and missing ambitious targets isn’t failure. In DACH companies with strong hierarchy, control culture, and zero-error mentality, OKR encounters structural resistance. The solution isn’t to “adapt” OKR (i.e., water it down) but to build the cultural prerequisites in parallel — starting with a pilot that proves autonomy and transparency produce better results than command-and-control.

OKR in DACH Companies: Practical Experiences

The Cultural Challenge

DACH companies face a specific hurdle: leadership culture in many German, Austrian, and Swiss organizations is shaped by clear hierarchies, precision, and risk avoidance. OKR demands the opposite: ambition (stretch goals), transparency (everyone sees everyone’s OKRs), and tolerance for shortfall (60-70 percent achievement is success).

A study by Kudernatsch (2023) on OKR implementations in German-speaking companies identifies the biggest obstacles:⁷

• Lack of strategic clarity: Without a clear corporate strategy, the anchor for Company OKRs is missing.
• Departmental silos: OKR forces cross-functional alignment that meets resistance in siloed organizations.
• Linkage to target agreements: Many DACH companies have contractually anchored annual target agreement systems. Introducing OKR alongside these creates two competing systems.

Practical Example: Technology Company in the DACH Region

A major DACH technology company introduced OKR over three years in stages:

Year 1 (Pilot): Three product teams test OKR. Finding: teams formulated Key Results as task lists. Coaching and retraining corrected the problem in the second quarter.

Year 2 (Scaling): 15 teams use OKR. Company OKRs are formulated by the executive board. Finding: quarterly planning collides with the existing annual budget process. Solution: quarterly budget reserve for OKR-driven initiatives.

Year 3 (Normalization): OKR is standard process. Annual target agreements are replaced by a new performance framework that separates OKR contribution from individual development. Key learning: the OKR implementation didn’t take three months but three years — because it required a culture change, not just a new tool.

Frequently Asked Questions

What is OKR in simple terms?

OKR (Objectives and Key Results) is a goal management framework that helps organizations focus on what matters most. An Objective describes qualitatively what you want to achieve. Key Results describe quantitatively how you know you’ve achieved it. OKRs are set quarterly, reviewed weekly, and evaluated at quarter’s end. The core: few, ambitious goals instead of many small ones.

How many OKRs should a team have?

Two to three Objectives per quarter, each with three to five Key Results. More than five Objectives destroys focus. More than five Key Results per Objective dilutes measurability. If the team can’t keep all Key Results in mind, there are too many.

What is the difference between OKR and KPI?

KPIs measure the ongoing health of existing processes (e.g., churn rate, cycle time, revenue). OKRs define progress on strategic changes (e.g., “reduce Customer Effort Score from 4.8 to 3.2”). KPIs are constants — measured continuously. OKRs are change targets — reset quarterly. The same metric can be both a KPI and a Key Result, but the context differs: as a KPI it is reported; as a Key Result it is actively managed.

Why should OKRs not be linked to compensation?

Because linking to bonus or salary increases causes teams to set conservative targets. The core of OKR is stretch goals — ambitious targets where 60-70 percent achievement is a success. If missing 100 percent costs a bonus, teams will formulate safe goals and destroy the innovation incentive.

How does OKR work for innovation teams?

Innovation teams need learning goals rather than performance goals as Key Results. Instead of “Launch 3 new services” (performance goal), you formulate “Validate 3 service hypotheses with real customers” (learning goal). The difference: a performance goal penalizes exploration. A learning goal rewards it.

What is the difference between OKR and the Balanced Scorecard?

The Balanced Scorecard is a strategic management instrument with four perspectives and an annual cycle. OKR is a focus framework with a quarterly cycle. The BSC asks: “Are we strategically on course?” OKR asks: “What do we focus on this quarter?” In practice, they complement each other: the BSC provides the strategic framework, OKR the tactical focus.

Methodology & Sources

This article draws on 12 academic and practitioner sources, including the foundational works by Drucker (1954), Grove (1983), and Doerr (2018), goal-setting theory by Locke & Latham (1990/2002), Google’s public OKR documentation, the OKR practice literature by Castro and Niven/Lamorte, and DACH-specific implementation experiences.

SERP finding: The German-language top-10 results for “OKR” are introductory articles and tool comparisons. None systematically connects OKR to innovation management, explains the Locke & Latham foundation, explicitly distinguishes learning from performance goals for innovation teams, or offers a structured method comparison (OKR vs. BSC vs. KPI vs. MBO). This article closes these four gaps.

Limitations: Google’s OKR practice is extensively documented but not generalizable as a single case study. DACH-specific empirical data on OKR effectiveness at the organizational level is scarce. The OKR + BSC combination is proven in practice but little studied academically.

Disclosure: SI Labs supports companies in developing service innovation capabilities. OKR is one of the frameworks we use in the context of service innovation — not a standalone consulting product.

References

Footnotes

1. Castro, Felipe. OKR: The Ultimate Guide. felipecastro.com, continuously updated. Castro emphasizes decoupling OKR from performance reviews as a central success condition. ↩ ↩²

2. Drucker, Peter F. The Practice of Management. Harper & Brothers, 1954. Introduction of Management by Objectives (MBO). ↩

3. Grove, Andrew S. High Output Management. Random House, 1983. Chapters 5-6: Transformation of MBO into a dynamic goal system at Intel. ↩

4. Doerr, John. Measure What Matters: How Google, Bono, and the Gates Foundation Rock the World with OKRs. Penguin, 2018. Standard reference on the OKR method with case studies from Google, Intel, Gates Foundation, and other organizations. ↩ ↩² ↩³ ↩⁴

5. Locke, Edwin A. and Gary P. Latham. A Theory of Goal Setting and Task Performance. Prentice-Hall, 1990. Supplemented by: Locke, Edwin A. and Gary P. Latham. “Building a practically useful theory of goal setting and task motivation: A 35-year odyssey.” American Psychologist 57, no. 9 (2002): 705—717. Effect size: 10-25% performance improvement from specific, difficult goals. Warning: for highly complex tasks, use learning goals instead of performance goals. ↩ ↩²

6. Google. re:Work — Guide: Set goals with OKRs. rework.withgoogle.com. Public documentation of Google’s OKR practice. Distinction between Committed (100% expected) and Aspirational (60-70% = success) OKRs. ↩ ↩² ↩³

7. Kudernatsch, Daniela. Objectives and Key Results in der Praxis: OKR in deutschen Unternehmen erfolgreich einfuhren. Schaffer-Poeschel, 2023. Analysis of the biggest hurdles in OKR implementations in DACH companies. ↩