Skip to content Skip to footer

OKR (Objectives and Key Results)

Key Takeaways: OKR (Objectives and Key Results) is a modern goal-setting framework that links ambitious goals (Objectives) with measurable results (Key Results). The method creates focus, transparency, and alignment within organizations, enabling teams to work independently on strategic goals. OKRs are typically set quarterly, reviewed regularly, and promote a culture of continuous improvement. Especially for SMEs, the method offers a lean alternative to traditional goal systems.

What are OKRs? Definition and Fundamentals

OKR stands for Objectives and Key Results – a framework for goal setting and strategy execution originally developed at Intel and later popularized by Google. The method helps organizations set ambitious goals, break them down into measurable results, and align all levels of the company toward common priorities.

At its core, every OKR consists of two components: The Objective describes a qualitative, inspiring goal – where do we want to go? The Key Results (typically 2-5 per Objective) define measurable outcomes that show whether the goal has been achieved. While the Objective motivates and provides direction, Key Results make progress quantifiable.

What distinguishes OKRs from traditional goal systems: The method is explicitly designed for ambition. An achieved score of 70-80% is considered a success – 100% would mean the goals were not ambitious enough. This philosophy encourages teams to think beyond the obvious and strive for real breakthroughs.

OKRs promote transparency: Ideally, all OKRs in the company are visible to everyone – from the CEO level to individual teams. This openness creates alignment, prevents silos, and allows everyone to understand how their own work contributes to the corporate strategy.

The method is agile and iterative. OKRs are typically set quarterly and evaluated at the end of the quarter. This frequency allows for rapid adjustments to changing market conditions and prevents teams from sticking to outdated goals.

Structure and Setup of OKRs

A complete OKR set consists of one or more Objectives, each supported by 2-5 Key Results:

Objectives should be:

  • Inspiring – they motivate and provide energy
  • Qualitative – they describe the desired state
  • Time-bound – typically designed for one quarter
  • Actionable – the team can actively work on them
  • Understandable – everyone on the team knows what it is about

Example of a good Objective: “We will become the preferred platform for SMEs in our segment”

Key Results should be:

  • Measurable – with concrete numbers, percentages, or binary criteria
  • Outcome-oriented – describing outcomes, not activities
  • Ambitious but achievable – challenging the team
  • Specific – no vague phrasing
  • Verifiable – clearly assessable at the end of the quarter

Example of good Key Results for the above Objective:

  1. Net Promoter Score increases from 45 to 65
  2. Customer Satisfaction (CSAT) reaches 4.5 out of 5 stars
  3. Repurchase rate increases from 30% to 50%

Typical OKR structure in a company:

Company OKRs: Defined by the management team, these set the strategic direction for the entire company (3-5 Objectives).

Team OKRs: Derived from company OKRs but defined by the team itself. They show how the team contributes to the corporate strategy.

Individual OKRs: Optional. Some companies use them, others avoid them to promote teamwork. If used, they should not be used for performance reviews.

Important: OKRs are not to-do lists. Tasks and projects are a means to an end – Key Results describe the desired outcomes, not the activities.

Benefits of the OKR Method for Companies

The OKR method offers companies – especially SMEs – numerous strategic advantages:

1. Focus and Prioritization: By limiting to 3-5 Objectives per quarter and level, teams are forced to distinguish the most important from the merely important. This prevents fragmentation and ensures that resources are concentrated on critical topics.

2. Alignment and Transparency: When all OKRs are publicly visible, employees understand the connection between their work and the corporate strategy. Departments can collaborate better because they know each other’s priorities. Duplication of work is avoided.

3. Measurability and Accountability: Key Results make progress objectively measurable. Instead of subjective assessments, there are clear metrics. Teams can independently check if they are on track and take corrective action if necessary.

4. Agility and Adaptability: Quarterly OKR cycles allow for rapid course adjustments. If market conditions change or a strategy proves ineffective, it can be corrected in the next quarter – without year-long planning cycles.

5. Ambition and Innovation: The expectation that 70-80% goal achievement is a success encourages teams to think boldly. Instead of setting safe, achievable goals, stretch goals are formulated that require real breakthroughs.

6. Autonomy and Ownership: Teams define their OKRs themselves (within the strategic framework). They decide how to achieve the Key Results. This individual responsibility increases motivation and engagement.

7. Continuous Learning: OKR retrospectives at the end of each quarter create a culture of reflection. Teams analyze what worked and what didn’t, and continuously improve their approach.

8. Decoupling from Compensation: OKRs should not be directly linked to bonuses. This reduces the incentive to set only achievable goals (sandbagging) and promotes honest, ambitious goal setting.

OKRs in SMEs: Practical Implementation

Many SMEs hesitate to introduce OKRs because the method seems complex or they fear it only works for tech giants like Google. In fact, OKRs are particularly suitable for smaller organizations:

Step 1: Secure commitment from the top
OKRs only work if the management is fully behind them. Management should understand the method, set OKRs themselves, and act as role models.

Step 2: Start with a pilot
Instead of converting the entire company at once, start with one or two teams for 1-2 quarters. Gather experience, identify best practices, and then roll it out gradually.

Step 3: Training and Workshops
Invest in initial training. Employees must understand how to formulate good OKRs and how the method differs from previous goal systems. An external coach can be valuable, especially at the beginning.

Step 4: Define Company OKRs
The leadership team defines 3-5 strategic Objectives for the next quarter. These should reflect the most important priorities and be challenging.

Step 5: Derive Team OKRs
Teams derive their OKRs from the company OKRs. Important: They are not dictated top-down but formulated by the team itself. Management provides the framework (“What should we contribute to?”), and the team decides on the how.

Step 6: Make OKRs transparent
Use a simple tool (Google Sheets, Notion, specialized OKR software) or a physical board to make all OKRs visible. Everyone should be able to view the OKRs of other teams.

Step 7: Establish regular check-ins
Weekly or bi-weekly check-ins within the team ensure that OKRs remain active. Teams discuss progress, obstacles, and necessary adjustments.

Step 8: Quarterly Assessment and Retrospective
At the end of the quarter, OKRs are assessed (0-100% or 0.0-1.0 score). More important than the number is the reflection: What did we learn? What will we do differently next quarter?

Tips for SMEs:

  • Keep it simple – less is more
  • Avoid tool overkill – a spreadsheet is enough to start
  • Be patient – it takes 2-3 cycles for OKRs to work well
  • Adapt the method to your culture – there is no “perfect” implementation
  • Celebrate learning successes, even if Key Results were not achieved

The OKR Cycle: From Planning to Retrospective

A typical OKR cycle includes several phases:

1. Planning (week before quarter start):
The management team defines company OKRs based on strategy, market development, and learnings from the previous quarter. These are shared and explained to the entire company.

2. Team OKR Draft (first week of the quarter):
Teams develop their OKR drafts. They consider: How can we contribute to the company OKRs? What are our most important levers? Initial drafts are discussed with other teams and management to ensure alignment.

3. OKR Finalization and Kickoff (second week):
Team OKRs are finalized, published, and presented in the kickoff meeting. Each team presents its OKRs and explains how they contribute to the strategy.

4. Execution and Check-ins (weeks 3-12):
Teams work on their OKRs. Weekly or bi-weekly check-ins provide rhythm. In these short meetings (15-30 min), the team discusses:
– What progress have we made?
– What score do we currently expect?
– What obstacles are there?
– What do we need to move forward?

5. Mid-Quarter Review (week 6-7):
Optional checkpoint at the halfway mark. Are we on track? Do we need to adjust anything? In case of dramatic changes (market shock, strategic pivot), OKRs can be adjusted here – but this should remain an exception.

6. OKR Scoring (last week of the quarter):
Teams assess their Key Results objectively. Typical scoring scale:
– 0.0-0.3: We didn’t make it
– 0.4-0.6: Progress, but below expectations
– 0.7-0.8: Success! (Target range)
– 0.9-1.0: Over-fulfillment – were the goals too low?

7. Retrospective (last week/first week of new quarter):
The team reflects:
– What worked well?
– What didn’t work? Why?
– Which assumptions were wrong?
– What do we learn for the next quarter?
– Which processes/tools do we need to improve?

This rhythm creates predictability and structure without being rigid. The regularity ensures that strategy does not become an annual mandatory exercise but remains a living part of daily work.

Practical Examples and Best Practices

Example 1: Software Startup (15 employees)

Company Objective: “We establish ourselves as the leading solution for SME accounting in the DACH region”

Key Results:
1. Reach 500 paying customers (currently: 180)
2. Achieve a customer retention rate of 85% (currently: 72%)
3. Average deal size increases to 150 EUR/month (currently: 95 EUR)

Product Team OKR:
Objective: “Our product becomes an indispensable tool in our customers’ daily business”
KR1: Feature adoption rate (active use of at least 5 features) increases to 60%
KR2: Time-to-value under 48h (customer generates first invoice within 2 days)
KR3: Mobile app rating increases to 4.5 stars

Example 2: Craft Business (25 employees)

Company Objective: “We will become the most digital electrician in the region”

Key Results:
1. 90% of all orders are recorded and billed digitally
2. Average response time to customer inquiries under 2 hours
3. Customer reviews average 4.7 out of 5 stars

Installation Team OKR:
Objective: “Our projects run according to plan and transparently”
KR1: 95% of all projects stay on schedule (currently: 70%)
KR2: Material reorders are reduced by 60%
KR3: Customer satisfaction after project completion: 4.8 stars

Best Practices:

  • Start with Why: Always explain the context. Why are these OKRs important? How do they contribute to the strategy?
  • Link OKRs with weekly work: Regularly ask in team meetings: “How does what we are doing this week contribute to our OKRs?”
  • Visualize progress: Use dashboards or physical boards to make progress visible
  • Celebrate wins: Even if the final score is only 0.7 – acknowledge successes
  • Learn from failures: Failed OKRs are learning opportunities, not catastrophes
  • Bidirectional OKR development: Bottom-up input is just as important as top-down direction
  • Separate OKRs from performance reviews: Otherwise, only safe goals will be set

Typical Mistakes and How to Avoid Them

1. Misusing OKRs as a to-do list
Mistake: Key Results describe activities instead of outcomes (“Write 5 blog posts” instead of “Increase website traffic by 30%”)
Solution: Always ask: “Why are we doing this? What is the desired outcome?” Formulate the outcome as a Key Result.

2. Setting too many OKRs
Mistake: Teams have 8-10 Objectives, leading to fragmentation
Solution: Maximum 3-5 Objectives per level and quarter. Focus is the goal.

3. Formulating “business as usual” as OKRs
Mistake: Routine tasks are declared as OKRs (“Answer all customer inquiries”)
Solution: OKRs should describe ambitious goals that go beyond daily business. BAU tasks do not belong in OKRs.

4. Setting unrealistic OKRs
Mistake: Goals are so ambitious that even 30% achievement is unrealistic
Solution: Ambitious ≠ impossible. With 70-80% effort, 70-80% of Key Results should be achievable.

5. Dictating OKRs top-down
Mistake: Management prescribes which OKRs teams must have
Solution: Management provides the strategic framework, teams develop their OKRs themselves. This increases commitment.

6. “Set and forget”
Mistake: OKRs are defined in January and only brought out again in December
Solution: Quarterly cycles, weekly check-ins, and visible dashboards keep OKRs alive.

7. Lack of measurability
Mistake: Key Results are vague (“Improve customer satisfaction”)
Solution: Every Key Result needs a clear metric and target value (“Increase NPS from 40 to 60”)

8. Linking OKRs to compensation
Mistake: Bonuses depend directly on OKR achievement
Solution: Decouple OKRs from individual performance assessment. Otherwise, only safe goals will be set (sandbagging).

9. Lack of transparency
Mistake: OKRs are only known to the team itself or management
Solution: Make all OKRs public (internally). Transparency is a core principle of the method.

10. Giving up too early
Mistake: After the first quarter, OKRs are dismissed as “not working”
Solution: The learning curve is steep. Give the method 3 quarters before judging.

Frequently Asked Questions (FAQ)

How do OKRs differ from traditional goal-setting systems such as MbO?
OKRs are more agile (quarterly instead of annually), more transparent (all OKRs are visible), more ambitious (70-80% goal achievement is success), and decoupled from compensation. Management by Objectives (MbO) often works with individual, confidential annual goals linked to performance reviews. OKRs promote teamwork and radical transparency, while MbO focuses more on individual responsibility.
How many OKRs should a team have?
Ideally 3-5 Objectives per quarter, each with 2-5 Key Results. More leads to a loss of focus. If you have more potential goals, prioritize rigorously: What is truly critical for this quarter? The rest can move to the next quarter or be differentiated as “Committed” vs. “Aspirational” OKRs.
Do we need special software for OKRs?
To start, a Google Sheet or Notion is perfectly sufficient. Specialized OKR tools (Ally, Perdoo, Weekdone, 7Geese) offer advantages for larger organizations: automatic tracking, visualizations, check-in reminders. For SMEs up to 50 employees, they are not strictly necessary. More important than the tool is the discipline to review OKRs regularly.
Can we combine OKRs with Scrum?
Absolutely – many companies do this successfully. OKRs define the strategic goals (“What do we want to achieve?”), while Scrum structures the implementation (“How do we work?”). Sprint goals can align with current OKRs. In sprint reviews, not only is the increment shown, but progress against Key Results is also discussed. The combination creates strategic alignment plus operational excellence.
What should we do if we significantly miss our OKRs?
First: Honestly analyze why. Were the goals unrealistic? Have conditions changed? Did we measure the wrong things? These learnings are valuable for the next quarter. Celebrate partial progress anyway. And importantly: Missed OKRs must not have negative consequences for the team – otherwise, only safe goals will be set in the future. Failed ambitious OKRs are better than achieved mediocre ones.

Would you like to introduce OKRs in your company? We accompany you from strategy definition to workshops for OKR development and ongoing support during your first quarters. Schedule a free initial consultation and find out how OKRs can make your company more focused and agile.