OKR Framework

Origin & evolution

Andy Grove developed the system at Intel in the early 1970s, building on the Management by Objectives ideas Peter Drucker had introduced in the 1950s. Grove's contribution was sharper: he separated the direction (the objective) from the proof of progress (the key results), and he insisted on a scoring ritual that treated 70% achievement as success, so teams would set genuinely ambitious targets. He described the system in High Output Management (1983), still one of the most honest management books written. John Doerr learned OKRs as a young engineer at Intel, then carried the method to Google in 1999 as a venture partner at Kleiner Perkins. The Google adoption is what spread OKRs from Silicon Valley to the broader startup world. Doerr's Measure What Matters (2018) became the canonical text for the current era. Christina Wodtke's Radical Focus (2016) is the operational complement that many teams find more practical to run against.

How it works in practice

The typical cycle is quarterly. A company sets three to five objectives, each with three to five key results. Teams nest their own objectives beneath the company level, connecting them with explicit supporting relationships so the cascade is visible without being mechanical.

An objective should be qualitative, memorable, and time-bound: "Make our onboarding the best in the category this quarter." A key result attached to it should be quantitative, falsifiable, and outcome🏆OutcomeStrategyA desired business or user outcomeView reference →-oriented: "Time-to-first-value drops from 14 minutes to 6 minutes by end of quarter." The test for a key result is whether a neutral observer could score it at the end of the cycle without interpretation.

A worked example. A product team sets the objective "Earn our users' trust with data." Key results: user-reported confidence in data accuracy moves from 58% to 80% (measured in quarterly survey); data freshness SLA drops from 24-hour lag to under 1 hour; zero data incidents🚨IncidentDevOps & PlatformA production incidentView reference → rated P1 during the quarter. Each key result has an owner, a starting baseline, and a target. At quarter end, the team scores each 0 to 1.0. A score of 0.7 is a healthy outcome; 1.0 consistently suggests the targets were too conservative.

When to use it (and when not)

OKRs work best at the start of a new strategic cycle, when forming or restructuring a team around a shared scoreboard, and when leadership needs🫀NeedUserA user need, pain, desire, or constraintView reference → horizontal alignment without micromanaging tactics. They are at their most useful when the team has activity but no shared direction, or when strategy exists in slide decks that nobody operates against day to day.

The most consistent failure mode is writing key results that measure activity, not outcomes. "Ship 12 features⭐FeatureProduct SpecificationA product capability or featureView reference →" is a task☑️TaskProduct SpecificationA unit of work within a story or epicView reference →, not a result. A key result should describe a change in the world, not a change in the team's output log. A second failure is attaching OKRs to compensation. Grove's original design kept them separate from performance reviews precisely to preserve the ambition: if a low score costs money, teams set conservative targets and game the scoring. A third failure is rigid cascading, where team OKRs🏅Team OKRTeam & OrganisationA team-level OKRView reference → become administrative copies of company OKRs with no meaningful translation. The cascade should carry the direction, not the wording.

In the Unified Product Graph

OKR Framework is a tree framework in the strategy category. It maps four entity types across three levels of the tree.

• The Objective slot holds an objective🏁ObjectiveStrategyA strategic goal (OKR)View reference → entity: the qualitative direction for the cycle.
• Key Result 1 and Key Result 2 slots each hold a key_result📈Key ResultStrategyA measurable result tied to an objectiveView reference → entity: the quantitative measures of progress against that objective.
• The Initiatives🚀InitiativeStrategyA large coordinated effort to achieve a strategic goalView reference → slot holds an initiative🚀InitiativeStrategyA large coordinated effort to achieve a strategic goalView reference → entity: the work the team is doing to move the key results.

The Unified Product Graph models the full chain from objective through key results to initiatives, and from key results through to the metric🔢MetricStrategyA unified metric that measures progress, health, or behaviour across the productView reference → entities that the scoring depends on. An objective set at company level can support team-level objectives through explicit edges, making the cascade queryable without requiring manual maintenance of mirrored spreadsheets.