OKR in Transformation: Objectives and Key Results That Actually Land

01

What OKRs are

OKR stands for Objectives and Key Results: a goal-setting method that separates qualitative direction from quantitative progress.

In method terms, OKR is the evolution of Peter Drucker's Management by Objectives from the 1950s. Andy Grove shaped today's OKR logic at Intel, and John Doerr carried it to Google. The real break with the old world is a shift in perspective: away from "Did we complete our tasks?" toward "Did we make real progress?" Output becomes outcome.

So much for the theory you will find in any OKR guide. For a transformation, it is not enough.

03

The third dimension: OKR and the 3C diagnosis

This is the most important framing in this piece. OKR is, at its core, a coordination instrument. It synchronizes goals across teams, creates focus, and makes progress visible. That is a lot, but it is one of three dimensions.

The behavioral science behind ChangeMaker® describes three success factors for any transformation, the 3C method: concerns, competencies, coordination. Map them onto OKR and the gap appears immediately.

An objective on a slide changes no behavior. If the people involved do not own the goal (concerns), or lack the capability to reach the key results (competencies), the best OKR set stays a well-formatted statement of intent. That is the single most common reason OKR programs wither.

The evidence supports the link. A McKinsey analysis of 60 publicly listed companies found that transformations with the highest active employee involvement (21 to 30%) delivered +67% higher excess returns over 24 months versus the industry benchmark, compared with programs that involved almost no one.1 Involvement is concerns, not coordination. OKR alone does not address it.

05

The cycle mismatch: not every transformation theme fits a quarter

OKR runs on a shared clock: one quarter, reset for the whole organization at the same time. That fits themes that actually move on a quarterly rhythm, such as a marketing campaign, a pricing test, or a sales push into a new segment. It fits far less well themes whose natural duration is longer than a quarter and cannot be compressed into one without becoming artificial.

A new production strategy is the clearest case. Retooling a plant, qualifying a new supplier base, or shifting a manufacturing footprint runs on capex approval, equipment lead times, and safety and quality gates that take eighteen months or more from first decision to first measurable output. Force that into quarterly key results and one of two things happens: the key results turn into soft proxies with no real movement quarter to quarter, or the quarter turns into a re-planning ceremony that produces status slides instead of progress.

This is not just intuition. Benchmark comparisons of OKR cadences find that quarterly cycles suit fast-moving, quarter-length themes such as product adjustments, marketing, and go-to-market work, while capital-intensive and regulated environments such as manufacturing move on longer, more gradual cycles and are usually better served by annual or multi-year goals.4 OKR practitioners note directly that quarterly OKRs may simply not be suitable for long-term, strategic objectives. One industry write-up frames the tension well: quarterly cycles are deceptively short when you set strategic goals, but painfully long when you actually need feedback on them. A separate benchmark across 330 organizations found that 93% of them modify OKRs mid-cycle, a sign of how often the timebox breaks under themes it was not built to hold.

This connects directly to the concerns dimension in the 3C model. The entire premise of a key result is that people can see their own progress and feel it moving, and that feeling is what sustains commitment quarter after quarter. When an initiative's natural duration is measured in months or years rather than weeks, no key result exists that can show real movement inside a single quarter, or the one that does exist simply does not move. The team is not failing to work. The work itself cannot compress. But from the outside, a flat or barely-moving key result reads exactly like stalled effort, and after one or two quarters of that, people stop believing the goal is theirs to move. The commitment erodes not because anyone lacked buy-in at the start, but because the format never lets that buy-in show results. An infrastructure change is the sharpest example: a new ERP backbone or a plant-wide control system migration can consume a full year of disciplined work before a single meaningful metric shifts, and an OKR set that expects quarterly progress on it manufactures the exact concerns problem described earlier, regardless of how motivated or capable the team is.

Most transformations contain these larger topics at their core. For the usual mixture of big and small, an initiative program is usually the more honest instrument. It carries the same building blocks as the OKR ladder, meaning objective, milestones, owner, but it does not need a shared timebox to function. Each measure gets its own start date, duration, and review rhythm, set by what the measure actually requires: a supplier qualification might run fourteen months, a pilot line changeover six weeks, a safety certification nine months, all inside the same production strategy and tracked side by side. Progress is reported by milestone and degree of completion per measure, not forced into a quarter that has no relationship to the underlying work.

07

What makes a good key result

The most common mistake: key results that describe activities instead of outcomes. "Run three workshops" is an activity. "Cut cycle time from 12 days to 7" is an outcome. That difference decides whether a key result steers or just keeps people busy.

Good key results are:

09

OKR in practice: a customer example