# OKR in Mid-Sized Companies: Benefits, Effort and Scope

Author: Marin Niehues, Niehues Consulting · Published: 2025-02-27 · Updated: 2026-11-16 · Delivery & Steering
Source: https://www.niehuesconsulting.com/blog/okr-for-mid-sized-companies/

OKRs link corporate goals to measurable results in short cycles and give mid-sized companies focus and transparency. The effort is concentrated in the first two cycles; after that the rhythm runs on about one working day per team and quarter. Andy Grove developed the method at Intel from Peter Drucker's management by objectives; John Doerr brought it to Google and described it in "Measure What Matters". Mid-sized companies with short decision paths use it particularly directly, because management passes goals straight into the business units and sees results within a quarter. This article provides an overview and does not constitute legal advice.

**OKRs turn a strategy into a sequence of verifiable quarterly goals. Every team can read from its own contribution whether the company goal is coming closer.**

## What do OKRs deliver?

OKRs translate the strategy into a few quarterly goals with measurable results and thereby force prioritization. OKR stands for Objectives and Key Results. An objective describes qualitatively what is to be achieved in a given period. For each objective, three to five key results define the measurable outcomes by which success becomes visible. The usual period is a quarter. Whoever formulates an objective decides what takes precedence. Whoever sets key results agrees how progress will be checked.

An example from delivery shows the format. The objective reads "Our customers receive their orders reliably on the promised date". The key results, here with illustrative values:

- On-time delivery rises from 82 to 95 percent.
- Customer escalations fall from 14 to no more than 5 per month.
- Lead time from order intake to delivery shortens from 12 to 8 working days.

Each team derives its own objective from this, for example production planning or logistics. The result is a goal tree that reaches from management down to the individual team.

## OKR examples for sales, production or HR

OKRs work in every function, provided the key results measure outcomes. The following examples show the format with illustrative values.

**Three functional examples**
- Sales. Objective: "We win mid-sized customers in the new segment as regular customers." Key results: 12 new customers in the segment; win rate on qualified proposals from 20 to 30 percent; average order value of new customers at least 40,000 euros.
- Production. Objective: "Line 2 delivers predictably." Key results: overall equipment effectiveness from 68 to 78 percent; unplanned downtime from 9 to 4 hours per week; scrap rate below 1.5 percent.
- HR. Objective: "New specialists become productive quickly." Key results: time to fill critical roles from 90 to 60 days; 90 percent of new hires with a completed onboarding plan after four weeks; resignations during probation halved.

A common mistake shows up in a simple test: "Run training for all sales staff" is an activity. The key result measures what the training is meant to achieve, for example the win rate.

## Benefits for mid-sized companies

The first benefit is focus. A few goals per quarter force prioritization, and that prioritization happens in management, where it belongs. Initiatives that contribute to no goal become visible and are dropped.

The second benefit is transparency. All goals are visible to everyone involved. Dependencies between business units surface early, because a team sees which results of other teams it relies on. In organizations that have grown on informal agreements, this creates a shared working basis.

The third benefit is pace. The quarter breaks the annual plan into deliverable stages and allows course corrections before a year has passed. Mid-sized companies have a structural advantage here: with few management layers, a goal tree with two to three levels is sufficient. Strategy execution thereby gains a fixed cadence, which the article on [strategy execution](/blog/strategy-execution-why-strategies-fail/) also describes as a prerequisite.

## How much effort do OKRs require?

In steady state, OKRs require about one working day per team and quarter, roughly twice that in the first two cycles. A cycle starts with a kick-off and ends with a review including a retrospective; in between come weekly check-ins and a mid-quarter review. A coordinator maintains the goal tree and facilitates the rhythm.

**Calculation: effort per team and quarter**
- Kick-off with goal setting: 2 to 3 hours
- Weekly check-ins: 13 weeks at 15 to 20 minutes, about 3 to 4 hours
- Mid-quarter review: 1 hour
- End-of-quarter review with retrospective: 2 hours
- Total: about 8 to 10 hours per team, roughly one working day. The coordinator comes on top, typically one to two days per month for ten teams.

For goal setting, a distinction between two types of goal has proven useful. Committed goals are achieved in full, and operations plan with them. Aspirational goals are deliberately set beyond safe reach. At Google, according to John Doerr's account, a score of around 0.7 on aspirational goals counts as success. The goal-setting research of Edwin Locke and Gary Latham supports this approach: over decades, their studies show that specific and challenging goals lead to higher performance than an instruction to do one's best. This distinction gives teams the freedom to plan ambitiously without putting reliable operations at risk.

## Where OKRs have their full effect

OKRs steer change and growth. They have their greatest effect in initiatives with a clear target picture: new markets, process improvements, product launches, transformation. For ongoing operations, KPIs remain the steering instrument. KPIs secure day-to-day business, OKRs direct improvement work.

OKRs also need to be distinguished from classic target agreements. Management by objectives, as Drucker described it, sets annual goals per manager, confidentially and usually linked to pay. OKRs set quarterly goals per team, open to everyone and separate from pay.

## Why do OKR rollouts fail?

OKR rollouts mostly fail because of five mistakes, and none of them lies in the method itself. Management is better off knowing these limits in advance:

- Too many goals: five objectives per team with five key results each make a task list. One to three objectives per team is the upper limit.
- Activities instead of outcomes: key results that list measures record the teams' effort and leave their impact open.
- Linking to bonuses: rewarding the score produces cautious goals.
- Missing rhythm: without weekly check-ins, OKRs become a quarterly ritual that nobody reads.
- Unclear decision rights: when two goals compete for the same resources and nobody decides, the conflict remains open.

The drawbacks of the method itself are limited and well known. It costs management time and demands discipline over several cycles. It also makes goal conflicts visible that were previously hidden. For organizations whose business barely changes over years, good KPI steering is sufficient.

## Pay, works council and software

Two decisions determine the effect. The first concerns pay: John Doerr recommends separating OKRs from bonuses, because otherwise ambition falls. Performance appraisal and pay are better based on a broader picture, in which OKRs are one element. The second concerns decision rights. When two goals compete for the same resources, it must be clear who decides. With clear decision rights, a goal conflict becomes a question of prioritization.

Where a works council exists, it belongs in the planning early. Co-determination rights arise as soon as software records goals and progress per person or team and is therefore suitable for monitoring performance, and likewise when OKRs feed into appraisal or pay. A works agreement that sets out purpose and data scope and rules out performance assessment via the software has proven effective.

For software, a simple sequence applies. For the pilot, a spreadsheet or an existing task management tool is sufficient. Dedicated OKR software pays off once more than ten teams are working with OKRs and dependencies between goal trees need to be visible. Selection criteria are the linking of goals across levels and support for the check-in rhythm. Access control comes on top, since it matters for the works agreement.

## Rollout as a delivery task

An OKR rollout succeeds as an initiative with a pilot and a rhythm, followed by transfer. A pilot unit works with the method for two quarters, management accompanies the kick-off personally, and a coordinator takes on facilitation. Based on the experience gained, the method is adapted to the organization and transferred to further units. How goal systems interact with structure and delivery capability is described in the article [characteristics and metrics of a high-performing organization](/blog/high-performing-organisation/).

[Niehues Consulting](/) supports companies in this rollout from the perspective of delivery. In delivery management and organization design, Niehues Consulting defines roles and rhythm and settles decision paths so that OKRs run reliably in day-to-day business. The initiatives that arise from the key results are steered by Marin Niehues as delivery manager or product owner through to the result. The approach follows the Niehues Delivery Model with the phases Understand, Build and Roll out. For OKRs, three of its review questions matter: Which business outcome should change measurably? What is the baseline, and how do we measure success? Are users enabled and processes adapted?

**OKR compared with alternatives**
Criterion | Annual goals with target agreements | OKRs on your own | With Niehues Consulting
Goal horizon | Year | Quarter | Quarter, aligned with annual planning
Visibility | Goals per manager | Goals per team without an overall picture | Goal tree from management to team
Commitment | Annual review meeting | Discipline of individual teams | Fixed rhythm with responsibilities and decision paths
Anchoring | HR process | Individual teams | Pilot unit with transfer to the whole organization

**Recommendation for management**
Companies introducing OKRs start with a pilot unit and a clear rhythm. Management formulates the company goals itself, pay remains decoupled, and decision rights are clarified in advance. For initial orientation, Niehues Consulting offers a free [initial consultation](/#kontakt) of 30 minutes.

**Sources**
- Doerr, John: Measure What Matters, book, 2018
- Grove, Andrew S.: High Output Management, book, 1983
- Drucker, Peter F.: The Practice of Management, book, 1954
- Locke, Edwin A.; Latham, Gary P.: Building a Practically Useful Theory of Goal Setting and Task Motivation, American Psychologist, journal article, 2002
- German federal legislator: Betriebsverfassungsgesetz (Works Constitution Act), section 87 co-determination rights, statute, 1972

## Frequently asked questions

### What does OKR mean?

OKR stands for Objectives and Key Results. An objective names a goal qualitatively, and the associated key results make progress measurable. A cycle usually lasts one quarter.

### How many OKRs should a team have?

A team should have one to three objectives with three to five key results each. The limit forces the prioritization that the method is about. More goals spread capacity without any of them moving forward noticeably.

### What is the difference between OKRs and KPIs?

KPIs steer ongoing operations and stay permanently in view, while OKRs direct a quarter's change work. OKRs are reset every cycle. A key result can improve a KPI, for example on-time delivery.

### What is the difference between OKR and MBO?

Management by objectives sets confidential annual goals per person and usually links them to pay; OKRs set open quarterly goals per team without a bonus link. Target agreements thus serve performance appraisal, OKRs serve steering. Both can run side by side as long as they stay clearly separate.

### Should OKRs be tied to bonuses?

No, OKRs should not be tied to bonuses. John Doerr recommends separating them, because linking leads to cautious goals. At most, OKRs feed into performance appraisal as one element among several.

### How long does an OKR rollout take in a mid-sized company?

A rollout takes about a year: two quarters of piloting in one unit, then step-by-step transfer to further units. The rhythm settles over several cycles. The first two quarters require the most effort.

### Does the works council have to be involved in OKRs?

Yes, as soon as software records goals and progress or OKRs feed into appraisal and pay, the works council has co-determination rights in Germany. A works agreement on purpose and data scope has proven effective. Clarify the details with your legal advisers.

### Which software is suitable for OKRs?

For the pilot, a spreadsheet or an existing task management tool is enough; dedicated OKR software pays off from about ten teams. What matters is the linking of goals across levels and support for weekly check-ins. Access control must fit the works agreement.
