OKRs in strategy execution: when the method works and when it doesn't

What do OKRs deliver in strategy execution?

OKRs translate a strategy into goals you can check each quarter. An objective describes what you want to achieve; the key results make it measurable, so you know when you've gotten there.

The real gain is rarely the goal system itself. It's the rhythm that comes with it: every three months, the same group sits down and takes a look. Many companies that benefit from OKRs would have benefited just as much from any other fixed rhythm.

The second gain is visibility across department lines. When sales and production see their goals side by side, contradictions surface that would have gone unnoticed in separate meetings.

What has to be in place first?

One thing, and it isn't negotiable: the direction has to be decided.

OKRs are a translation tool. They take a decision and break it down. If there is no decision, you still end up with a goal system, but it simply describes day-to-day business in a new form. That only becomes obvious after two or three quarters, and then the method gets blamed for failing, even though the missing piece was the decision that should have come first.

A simple test: can management say in two sentences what the company is betting on for the next three years and what it's giving up to do it? If not, what you need is a strategy process, not a new method.

How do you derive OKRs from your strategy?

In the StrategyFrame®, objectives and key results are the fourth and final element of the target picture, formulated in the FOCUS step. What happens next determines the impact: in the CASCADE step, they are derived across all levels until every team knows what it's working on this quarter. OKRs without that second part remain a goal system for management.

In three steps, and the first one is skipped most often.

• Take the fields of action from the strategy, not from the departments. If every department derives its own OKRs from its day-to-day business, you get a collection, not a system.
• No more than three objectives per quarter for the company. A leadership team can't seriously track more than that. Everything else is day-to-day business and doesn't need a goal.
• Key results measure impact, not activity. "Concept created" is not a key result, it's a task. "New customers from the new segment at 15%" is one.

The examples show the difference between a key result and an action: it contains a number you can read off at the end of the quarter, not an activity. "Run ESG training" would be an action. "50% trained" is a result.

And then comes the step almost everyone leaves out: vertical alignment. When every level formulates its goals on its own, you get sets that are plausible individually and don't fit together. Before the quarter starts, someone goes through all the levels and checks for consistency: does the division goal really pay into the company goal? And are the resources where the result is expected? The outcome is an aligned package for the next quarter, including actions and owners. That package sets the direction for everyone.

The third point is the hardest, and most rollouts fail there, not because of the method. A goal system made of activities is a to-do list with extra maintenance.

When does a quarterly rhythm not fit?

More often than the OKR literature suggests. Three cases from mid-sized companies:

• Long project cycles. If you build plants and your projects run eighteen months, you can't define a meaningful quarterly milestone without inventing one.
• Highly seasonal business. When two quarters decide the year, an even quarterly cadence is an artificial frame.
• Small leadership teams below roughly a hundred employees. There, the same group already meets weekly. The gain from formalizing is small; the maintenance effort stays.

In these cases, an annual initiative plan with fixed review dates works better. It delivers the same thing, visibility and rhythm, without forcing a cadence that doesn't fit the business.

What are the most common mistakes in rolling out OKRs?

• Too many goals. Three objectives with three key results each are nine numbers someone has to maintain. Five objectives are fifteen, and at that point nobody maintains them. The longer the list of priorities, the smaller the chance of completing even one of them.
• An approach that's too rigid. Demanding weekly tracking, an explanation for every deviation and a meeting for everything doesn't create engagement. It creates a sense of bureaucracy. The system invites it, because everything can be counted. Monthly reviews and a recalibration each quarter are enough.
• No answer to the everyday question. Many employees struggle to connect their daily work to the goals. The question behind it is fair: if I'm doing something, it should pay into the strategy. If you have no answer, you get invented connections or quiet resistance.
• OKRs for everyone. Rolling them out across the entire company at once overwhelms the organization. The leadership team alone, for two quarters, is the more solid start.
• Tying goals to bonuses. As soon as money depends on the degree of goal attainment, goals get formulated cautiously. And with that, the benefit is gone.
• Tool before method. Selecting software is the most enjoyable part of the rollout and the least important. The first two quarters work fine in a spreadsheet.

What are the alternatives?

The most common one is also the simplest: a list of initiatives with owners, deadlines and a fixed review cadence. For most mid-sized companies it does exactly what OKRs do, without its own vocabulary and without a rollout project.

If you prefer to steer by metrics, the Balanced Scorecard offers an older but robust framework. It is more cumbersome and, in return, less prone to the quarterly pressure that leads to cautious goals under OKRs.

The choice of method rarely decides success. The fixed date does.