Objectives and Key Results (OKRs)

Definition

Objectives and Key Results (OKRs) is a goal-setting framework that pairs a small set of inspirational, qualitative objectives with three to five measurable key results per objective. An objective answers "what are we trying to achieve?" — a key result answers "how will we know we did it?" The framework forces alignment, ambition, and transparent measurement in one structure.

OKRs are not KPIs. KPIs measure operational health continuously; OKRs measure strategic progress quarterly. A team needs both — KPIs to keep the lights on, OKRs to move the organisation forward.

History

OKRs originated at Intel in the 1970s, formalised by Andy Grove from earlier Peter Drucker work on management by objectives (MBO). John Doerr brought OKRs to Google in 1999, where they became central to the company's scaling. Doerr's 2018 book Measure What Matters popularised the framework across technology, finance, manufacturing, government, and increasingly construction and infrastructure.

Anatomy of a Good OKR

A well-formed objective is:

• Qualitative — not a metric, but a direction.
• Inspirational — meaningful enough that the team cares.
• Time-bound — typically quarterly.
• Singular in focus — not a paragraph of strategic ambitions.

A well-formed key result is:

• Quantitative — measurable, with a baseline and a target.
• Outcome-based — not activity-based. "Ship the feature" is an activity; "achieve 40% feature adoption" is an outcome.
• Ambitious — a 70% achievement on a stretch KR is considered good; 100% on every KR suggests sandbagging.
• Bounded in number — three to five per objective.

Real-World Construction Example

A major contractor adopted OKRs at the executive level to align a 12-project portfolio. One quarter's objective: "Become the safest contractor in the regional market by reputation and measurement." Key results: lost-time injury frequency rate (LTIFR) below 0.4 (from 0.8 baseline); near-miss reporting frequency above 1.2 per 1,000 hours (from 0.6); third-party safety audit score above 92% (from 78%); 100% of supervisors certified on the updated incident-investigation course. The OKR ran across project boundaries: cost and schedule continued to be governed by project-level controls; safety strategic ambition was governed by the corporate OKR. The framework made it visible which projects were pulling their weight and which were not — three quarters in, the LTIFR target was hit and the framework was extended to quality and productivity.

Real-World IT / Agile Example

A payments product squad's quarterly objective: "Make the new checkout experience genuinely better than the old one for our top-100 merchants." Key results: increase top-100 conversion rate from 3.4% to 4.0%; reduce checkout abandonment from 28% to 22%; achieve NPS of +45 on the new checkout (from +28); achieve 95th-percentile checkout latency below 800ms. Notice that no key result is an activity — every one is an outcome the customer feels. The squad shipped four major features that quarter but those features were instruments, not objectives. Conversation in stand-ups and reviews focused on metric movement, not feature checklists. That is the OKR discipline in operation.

Cadence

The standard cadence is:

• Annual — strategic objectives for the organisation.
• Quarterly — team-level objectives derived from annual.
• Weekly — short check-in on key result progress.
• End of quarter — scoring and retrospective.

Quarterly is the standard team cadence in technology and increasingly in capital projects; some programmes run on a tranche cadence of 12–16 weeks aligned to the programme's increment plan.

Project Controls Perspective

OKRs and project controls are complementary, not competing. Project controls measure delivery against baseline — outputs. OKRs measure progress against strategic intent — outcomes. The two should connect: a project's quarterly contribution to a corporate OKR should be visible, and a project that delivers on time and budget but does not advance any OKR is suspect strategically. Mature PMOs publish an OKR-contribution view alongside the standard cost-and-schedule dashboard.

Common Mistakes

• Confusing key results with tasks ("ship the feature" instead of "achieve 40% adoption").
• Cascading OKRs hierarchically until every individual has 15 OKRs — focus is destroyed.
• Sandbagging targets to ensure 100% delivery and a bonus.
• Linking OKRs directly to compensation, which guarantees sandbagging.
• Treating OKRs as a parallel reporting system instead of integrating with existing operational rhythms.
• Setting OKRs without honest baselines — a target without a baseline is theatre.
• Refusing to retire or rewrite OKRs mid-quarter when conditions change materially.

Expert Tips

• Three to five objectives per team, three to five KRs per objective. Beyond that, attention collapses.
• Score on a 0–1 scale and aim for 0.7. Hitting every KR at 1.0 means the targets were too soft.
• Separate aspirational OKRs from committed ones. Aspirational targets at 0.7 are a win; committed targets must hit 1.0.
• Decouple OKRs from compensation. Compensation links destroy honesty.
• Use the weekly check-in to surface obstacles, not to chase numbers. If a KR is in trouble, the question is what to do about it, not who to blame.

Key Takeaways

• Objectives are qualitative directions; key results are quantitative outcomes.
• Outcomes, not activities. "Adoption" not "shipped."
• Three to five OKRs per team, three to five KRs per objective. Less is more.
• 0.7 is a good score on a stretch OKR; 1.0 every time means sandbagging.
• Don't link OKRs to compensation if you want honesty.

Related Concepts

OKRs interlock with KPIs, Program Management, Agile Project Management, Stakeholder Engagement, and Lessons Learned. OKR setting templates and worked examples are at PMMilestone.org.