Objective

Origin & evolution

The objective inherits from Peter Drucker's Management by Objectives, but its modern shape was forged at Intel in the 1970s by Andy Grove. Grove split a goal into two parts: a qualitative statement of intent and the measurable indicators that prove it. He documented the method in High Output Management (1983), framing the objective as the answer to "Where do I want to go?" while the key results answered "How will I pace myself to see if I am getting there?"

John Doerr learned the method directly from Grove at Intel, where he attended Grove's internal OKR course in 1975. Doerr carried it to Google in 1999 and spent the following decades spreading it, eventually setting it down in Measure What Matters (2018). His goal formula made the objective's role explicit: "I will (objective) as measured by (key results)." The objective is the verb phrase before the comma, and it carries the meaning while the key results carry the proof.

Christina Wodtke sharpened the discipline in Radical Focus (2016). She argued the objective should be qualitative, time-bound, and singular, written to be aspirational and a little uncomfortable, so the team feels the stretch. Her test for a good objective is whether it reads like something worth fighting for on a Monday morning. The live debate now is less about what an objective is than about how many a team should hold. The consensus that hardened across Grove, Doerr, and Wodtke is that one objective per team per quarter beats a portfolio🧸PortfolioPortfolioA grouping of products by strategic axisView reference → of five competing ones, because focus is the scarce resource the format exists to protect.

How it works in practice

A payments startup enters Q3 with churn climbing and a roadmap🛣️RoadmapProduct SpecificationA strategic plan of features and milestonesView reference → pulling in four directions. Leadership picks one objective: "Make new merchants feel safe enough to process real volume in week one." There is no number in it on purpose. The sentence names a felt state, merchant confidence, and a moment, the first week, that the whole company can picture.

The qualitative framing does work that a metric🔢MetricStrategyA unified metric that measures progress, health, or behaviour across the productView reference → could not. A growth PM who wanted to push a referral campaign sees it does not serve week-one confidence and drops it. A support lead reprioritises onboarding documentation because it obviously does. By the time key results get attached (activation rate, first-week processed volume, support tickets🆘Support TicketCustomer SuccessCustomer support request or issueView reference → per new merchant), the objective has already filtered the roadmap. The measurement comes next; the direction came first.

Objective vs. its neighbours

• Outcome🏆OutcomeStrategyA desired business or user outcomeView reference →: an outcome is a measurable change in behaviour, so it carries a target by definition. An objective is intentionally unmeasured; it supplies the direction that an outcome then quantifies. A team can pursue the same outcome under different objectives in different quarters.
• Key result: the key result is the objective's evidence🔎EvidenceValidationData supporting or refuting a hypothesisView reference →. The objective says where; the key result says how far and by when. An objective with no key result is the canonical anti-pattern, a wish with a deadline.
• Vision🔭VisionStrategyA long-term aspirational statement of the future stateView reference →: a vision is the multi-year destination with no fixed end date. An objective is the slice of that destination a team commits to for one quarter, which is why visions persist while objectives are retired or renewed every cycle.

In the graph

In the Unified Product Graph, objective🏁ObjectiveStrategyA strategic goal (OKR) lives in the Strategy & Outcomes region and acts as its anchor, the point where aspirational language meets measurable proof. It is guided from above by vision_guides_objectiveVisionguidesObjectivecross-domain and rolls up through objective_rolls_up_to_strategic_theme. Below it, objective_achieved_through_key_resultObjectiveachieved throughKey Resulthierarchy carries the accountability, and feature_drives_key_resultFeaturedrivesKey Resultcross-domain lets delivery work connect back without the objective ever holding a number itself. That structure encodes the anti-pattern as a missing edge: an objective🏁ObjectiveStrategyA strategic goal (OKR) with no outgoing objective_achieved_through_key_resultObjectiveachieved throughKey Resulthierarchy is queryably a wish, visible to anyone auditing the graph for goals that cannot be proven.