In the summer of 1975, Andy Grove, then head of operations at Intel, was watching his company lose a battle it had invented. Japanese semiconductor manufacturers were systematically underpricing Intel's memory chips, and the response from inside the company was a sprawling collection of directives, priorities, and initiatives that pointed in slightly different directions. Grove's fix was not a reorganization or a new strategy document. It was a question he required every manager to answer: what are you trying to achieve this quarter, and how will you know if you got there?
That question became the structural spine of OKRs - Objectives and Key Results - a framework Grove formalized at Intel and that John Doerr later carried to Google in 1999, where it helped a 40-person startup eventually organize 100,000 employees around shared outcomes. The reason it survived decades and scale is not that it is sophisticated. It is that it forces two disciplines that organizations consistently avoid: deciding what matters and defining what done looks like.
You probably work inside some version of this problem right now. Your team has goals. They are written somewhere - a planning document, a slide, a shared folder nobody opens after January. By the time March arrives, the day-to-day has taken over and the goals have become aspirational wallpaper. This is not a motivation problem. It is a structure problem.
What an Objective Actually Is
An Objective is a qualitative statement describing a desired future state. Not a task, not a metric, not a project milestone - a description of the world after you have succeeded. It should be specific enough that someone from outside your team could read it and understand what you are trying to change, and ambitious enough that it cannot be achieved by simply doing what you are already doing slightly better.
The test for a well-written Objective is whether it answers the question: what would be meaningfully different? "Improve customer satisfaction" fails this test because it does not describe a different world - it describes a direction. "Become the vendor our customers recommend to their peers" describes a state of being that is either true or not. You can argue about how to measure it, but you cannot mistake it for something you have already achieved.
The other failure mode is writing a task disguised as an Objective. "Launch the new onboarding flow" is a deliverable. If you ship it and nobody's experience improves, have you succeeded? An Objective built around the outcome - "Make the first week so clear that new users reach their first win without asking for help" - survives the scenario where the original plan doesn't work, because the team can change tactics without losing sight of the destination.
Think of the Objective as a compass heading, not a GPS route. The heading stays constant. The route adjusts to terrain.
The Stretch Question
Grove's original framework distinguished between committed goals - things you are expected to achieve 100% of the time - and aspirational goals, where 70% counts as success. Google later popularized this as the moonshot versus roofshot distinction. The underlying logic is that people optimize for achievement, and if you set goals at the edge of what is currently possible, you get incremental improvement. If you set them beyond that edge, you force a rethink of the approach.
This matters to you practically because the way you set an Objective changes how your team approaches the work. An Objective that reads like a stretch - something that requires the team to work differently rather than just harder - produces different conversations than one that reads like a safe projection. When you review progress at the end of the quarter and you have hit 65%, that number means something different depending on whether you set the goal to be achievable or aspirational. Make the distinction explicit when you write the Objective so that the team knows how to interpret results.
The failure mode here is using stretch framing as a way to never be accountable. "We only got to 60% but this was a moonshot" stops being legitimate after a few quarters if the definition of moonshot keeps shifting. Stretch goals require honest retrospectives about whether the stretch was calibrated to reality or was a way to avoid committing to anything.
Key Point: An Objective describes a future state, not a task or a direction. It should be specific enough to be falsifiable - you should be able to say at the end of a quarter whether you achieved it - and ambitious enough that achieving it would require meaningful change, not just incremental improvement.