OKRs were developed by Andy Grove at Intel in the 1970s, borrowed by John Doerr when he was an engineer there, and introduced by Doerr to Google in 1999. Google adopted them as a startup and never stopped using them. That trajectory — from a semiconductor manufacturer to the internet's most successful advertising business — is a reasonable indication that the system has something useful going for it regardless of industry.

What OKRs are

The structure is simple. An Objective is a qualitative statement of what you want to achieve. It should be short, memorable, and genuinely motivating — something that gives a team a sense of direction and purpose. "Create an outstanding customer experience" is an Objective. "Reduce support ticket volume" is not; that is a metric.

Key Results are the quantitative measures that tell you whether you are achieving the Objective. Each Objective typically has two to five Key Results. They must be measurable — if there is no number attached, it is not a Key Result, it is a task. For the customer experience Objective, Key Results might include reducing average response time, improving customer satisfaction scores, and increasing retention rate.

The relationship between Objectives and Key Results is important: Objectives say what, Key Results say how much. The interplay between them is where the goal-setting discipline lives.

What makes OKRs different

Several features distinguish OKRs from more conventional goal-setting approaches.

Ambitious targets. OKRs are set at a level where consistently achieving 70% represents good performance. This is counterintuitive in organisations where hitting targets is the measure of success. The rationale is that if teams always achieve 100% of their goals, the goals are not ambitious enough. Stretch goals — by definition — should occasionally exceed reach.

Transparency. OKRs are typically visible across the organisation. Everyone can see everyone else's OKRs. This creates alignment — because teams can see whether their goals are pulling in the same direction as other teams' goals — and it creates accountability in a way that private targets do not.

Decoupling from performance management. OKRs should not be directly connected to compensation and promotion. When they are, teams set conservative goals that they are confident of achieving rather than ambitious ones that might stretch the organisation. The incentive to be safe overrides the incentive to be bold. Keeping OKRs separate from evaluation systems preserves their usefulness as a genuine planning tool.

Cadence. OKRs operate at different timescales. Annual OKRs set strategic direction. Quarterly OKRs give teams a planning horizon short enough to be actionable. Weekly check-ins ensure progress is visible and obstacles are addressed in time to matter.

What teams typically get wrong

The most common mistakes are predictable. Writing too many OKRs — more than three to five Objectives at any level — dilutes focus and signals that everything is important, which means nothing is. Using OKRs as a task list rather than a goal-setting system: Key Results should measure outcomes, not completion of activities. Setting OKRs top-down without allowing teams to set their own — roughly 60% of OKRs should be set bottom-up, with managers aligning rather than dictating. And reviewing OKRs only at the end of the quarter, when it is too late to do anything with what you find.

Whether they are right for your organisation

OKRs work well in organisations that are genuinely comfortable with ambiguity, honest about progress, and willing to separate goal-achievement from reward. In organisations where hitting targets is a political matter rather than an operational one, OKRs tend to be gamed rather than used. No framework survives a culture that is determined to resist it.

Used honestly, they are one of the more useful alignment tools available — particularly in organisations where strategy and execution feel disconnected.