Most teams that struggle with OKRs are not failing at execution. They are failing at classification. They run every Objective through the same rulebook, score every Key Result against the same bar, and then wonder why the system feels punishing in some quarters and toothless in others.
The fix is older than the criticism. Google has long treated OKRs as two distinct things, not one — a split that emerged when Google adopted the framework from Andy Grove’s Intel, where every OKR had been aspirational. Committed OKRs are promises you must deliver. Aspirational OKRs are stretch goals that pull learning out of a team. The two need different scoring, different resourcing, and different conversations when they fall short. If you missed the introduction to the framework itself, the origins and definition of OKR cover the basics; this guide is the next layer.
The short version: the most common cause of OKR failure is mixing these two types. Treat them the same and the system breaks in predictable ways — which the rest of this article maps out, with examples for each.
The Two Types of OKRs at a Glance: Committed vs Aspirational
Google’s distinction is not a small style preference. It changes the meaning of nearly every part of an OKR — the purpose, the mindset, the definition of success, and what a missed target means after the quarter ends. What Matters, John Doerr’s OKR resource, frames the difference as binary delivery versus expected stretch.
| Dimension | Committed OKR | Aspirational OKR |
|---|---|---|
| Primary purpose | Deliver a defined outcome on a defined timeline | Push for stretch, learning, and innovation |
| Mindset | Promise and commitment | Experiment and invention |
| Definition of success | 1.0 is success | ~0.7 is success |
| Risk tolerance | Low — risks should be minimized | High — risks are expected and accepted |
| Clarity of solution | Path and execution plan clear upfront | Solution is unclear at the start |
| Resource planning | Resources and owners locked before commitment | Resources are intentionally a little short |
| Time horizon | Fixed, usually one quarter | Can stretch across several quarters |
| What a miss means | A signal of broken planning or execution | An expected outcome that drives iteration |
Why Google separates the two
The split is psychological more than procedural. A goal you must hit and a goal you are stretching toward should not be scored on the same scale, because they ask the team to behave in opposite ways. One demands certainty. The other demands risk. Compressing both into a single rulebook forces teams to pick one behavior and apply it to the wrong goals.
Committed OKRs: Promises You Must Deliver
A Committed OKR is, in plain terms, a promise. It describes work the team must complete inside the quarter, at the agreed scope, on the agreed date. Think of it as the load-bearing work that keeps the business running: regulatory deadlines, partner contracts, migration cutovers, infrastructure ready before peak season.
For this type, success is 1.0. Anything less is a miss. That sounds harsh until you compare it to a useful analogy: a Committed OKR is more like a flight departure time than a wish. “We take off at 10:00” is a promise to the passengers and to the airport slot, not a hope that 10:00-ish will work out. If the flight is late, the response is to analyze why and fix the system — not to pretend 10:15 was close enough.
Definition: three non-negotiable attributes
A Committed OKR carries three properties that cannot be waived without quietly reclassifying it as Aspirational.
(1) Clear timeline and resources. The team knows what to do, who owns it, and when it ships. If a major unknown is still in play, the OKR is not ready to be committed.
(2) Binary success criteria. Committed OKRs are not scored on a curve. The promise is kept or it is not.
(3) High-integrity commitment. Committed OKRs usually come from external or irreversible constraints:
- Customer or partner commitments
- Regulatory or compliance deadlines
- Infrastructure work needed before a launch or peak traffic event
Examples: SOC 2, migrations, partner launches
Real Committed OKRs tend to look concrete and dated, because they are.
- Migrate 100% of customer data to the new database architecture by the end of Q3
- Earn SOC 2 Type II certification by December 1
- Ship the iOS app to the App Store by June 30, per the partner contract
Each example has a defined scope, a fixed deadline, and a real consequence if missed. Partial delivery still counts as a miss — there is no half-certification and no half-launch.
When a Committed OKR is missed: post-mortem, not blame
Missing a Committed OKR should trigger a post-mortem, not a blame session. The goal is to understand what broke in the system, not to find someone to punish.
Useful questions during the review:
- Did we underestimate the complexity?
- Did we reassign resources without adjusting scope?
- Were dependencies unclear or unmanaged?
Healthy teams treat a missed Committed OKR as a signal about the quality of planning and prioritization, not as a verdict on the individuals involved. That distinction is what keeps the framework honest over time.
Aspirational OKRs: Stretch Goals That Drive Learning
An Aspirational OKR describes the future a team is trying to build, even when the path to get there is unclear. It exists to pull learning, experimentation, and outsized results out of the team. For this type, 0.7 is success, and consistently scoring 1.0 is itself a signal — usually that the goals are not ambitious enough.
The closest equivalent in English-speaking product work is “stretch goal” — the term Jack Welch popularized at GE in the 1990s, well before Google adopted OKRs. If you have used that phrase before, an Aspirational OKR is essentially the formal, scored version of it.
Definition: four defining qualities
Aspirational OKRs differ from Committed OKRs in four important ways.
(1) Challenge, not certainty. The OKR should push the team toward creative approaches, not toward applying the current playbook harder.
(2) Uncertainty by design. The direction is known; the exact method is not. Discovery and iteration are expected.
(3) Beyond current capacity. If existing resources can hit the goal comfortably, the target is probably too conservative.
(4) Can stretch across quarters. The priority is what matters, not whether the OKR can be checked off quickly.
Examples: DAU, NPS, brand awareness
Aspirational OKRs describe where the company wants to be, without prescribing how to get there.
Objective: Turn the product into a platform customers depend on every day.
- Lift daily active usage from 30% to 65%
- Improve NPS from 28 to 50 or higher
- Reduce time-to-value from 14 days to 3 days
Objective: Establish leadership in industry intelligence.
- Grow organic traffic from 12,000 to 50,000 monthly visitors
- Secure speaking slots at five tier-one industry conferences
- Lift brand awareness from 8% to 25%
These OKRs explain where the company wants to go, not the specific tactics for getting there. The tactics are what the team has to figure out.
Questions that help shape an Aspirational OKR
When a challenge feels vague, three questions sharpen it.
- “If we had slightly more resources and most things went well, what could we realistically achieve?”
- “If today’s constraints disappeared, what would success look like in two to three years?”
- “What outcome would genuinely surprise and delight our customers?”
Why Mixing the Two Breaks Teams
Mixing Committed and Aspirational OKRs is not a labeling problem. It changes how the team behaves, and the damage shows up later, not in the quarter where the mistake was made.
The pattern usually breaks in one of two directions.
Treating an Aspirational OKR as Committed: teams turn defensive
When a stretch goal is scored as a promise, teams stop optimizing for outcomes and start optimizing for safety.
- They lower the bar at planning time.
- They inflate the resources they ask for.
- They avoid bets that might fail.
Over a few quarters, OKRs become a conservative planning document, and innovation slows to whatever the team is sure it can deliver.
Treating a Committed OKR as Aspirational: deadlines slip, trust breaks
The reverse failure is just as common. When a real promise gets treated as a stretch goal, deadlines drift. Dependencies fall down the priority list. “We committed to this” quietly becomes “we got most of the way there, which should be fine” — and trust with customers, partners, and leadership starts eroding.
The silent damage: missed expectations and distorted incentives
In both directions, the damage is not immediate. It accumulates quietly through missed expectations and distorted incentives. By the time leadership notices, the patterns have been baked into how the team writes goals, scores them, and talks about success. That is the harder problem to fix, which is why classification matters before execution starts.
How to Classify Your OKRs From Day One
The cleanest way to avoid the mixing problem is to classify each OKR before the quarter begins, not after the scoring conversation gets awkward. A short checklist works in most cases.
For each OKR, answer:
- Is the outcome required? If a customer, partner, regulator, or launch dependency is waiting on it, treat it as Committed.
- Is the path clear? If the team knows what to do, who owns it, and when it ships, it is a Committed candidate. If “how” is genuinely unclear, it is Aspirational.
- Would a 0.7 score be a good outcome? If yes, it is Aspirational. If 0.7 means a missed promise, it is Committed.
- What does a miss mean? A post-mortem on broken planning means Committed. An expected step in iteration means Aspirational.
- Is the OKR labeled? A simple “C” or “A” tag next to each Objective prevents quiet drift later in the quarter.
Once you have answered these for each OKR, share the classifications with everyone scoring or reviewing the work. The conversations that go wrong at quarter-end almost always trace back to people scoring an OKR under assumptions the goal-setter never agreed to.
When scope, risk, or constraints change mid-quarter, revisit the classification. An OKR that started as Aspirational can become Committed if a customer ends up depending on it; an OKR that started as Committed can move the other way if the team genuinely discovers the path was unclear. The label should describe the goal as it stands now, not as it was written on day one.
Conclusion
Two OKR types, scored two different ways, with two different conversations when they miss. Committed OKRs are promises; success is 1.0, and a miss is a planning post-mortem. Aspirational OKRs are stretch goals; success is roughly 0.7, and a “miss” is part of the learning cycle. Mixing them is the most common cause of OKR programs that feel either punishing or pointless.
The next post in this OKR series covers the practical side — a five-step guide to implementing OKRs in practice, including how to run the classification step above as part of the quarterly kickoff. After that, the series continues with the twelve most common OKR mistakes and a checklist for connecting OKRs to performance reviews.
OKR series:
Leave a Reply