Committed vs. Aspirational OKR Classification
Separate must-do operational goals from moonshot stretch goals
Google's OKR practice divides goals into two distinct categories with fundamentally different expectations. Committed OKRs are tied to operational metrics -- product releases, revenue targets, hiring goals -- and must be achieved in full (score of 1.0). Any miss requires a postmortem to understand what went wrong in planning or execution. These are the goals the organization has agreed to deliver.
Aspirational OKRs represent bigger-picture, higher-risk, future-oriented ideas. They can originate from any level and aim to mobilize the entire organization. By design, they are challenging to achieve, with an expected average score of 0.7 and high variance. Failures at a rate of about 40% are considered normal and even healthy.
The key discipline is labeling each OKR correctly at the outset. Mislabeling a committed goal as aspirational means teams may not take it seriously enough. Mislabeling an aspirational goal as committed creates defensive behavior and unhealthy priority inversions. The relative weighting between the two baskets is a strategic cultural decision that should be revisited each cycle based on business conditions.
- Not all goals carry the same weight or risk -- classifying them explicitly prevents confusion about expectations.
- Committed OKRs protect the business; aspirational OKRs transform it.
- A team's committed plus aspirational OKRs should credibly consume somewhat more than available resources -- otherwise they're all effectively commits.
- Living in the 70% zone for aspirational goals requires a liberal sprinkling of moonshots and willingness to court failure.
- Inventory All Proposed OKRsGather all OKRs from across the organization for the upcoming cycle. Before assigning any labels, have each team present what they plan to accomplish and why it matters.
- Apply the Classification TestFor each OKR, ask: Is this something we must deliver (a customer commitment, a product release, a revenue target)? If yes, it's committed. Is this something that would transform our business but we don't yet know how to fully achieve? If yes, it's aspirational.Pro tipUse the customer litmus test for aspirational goals: If you asked your customers what they really want, does your aspirational objective meet or exceed their request? If not, it's too timid.WarningDon't mark aspirational OKRs as committed to create urgency -- this breeds defensiveness and destaffs real commitments.
- Set Scoring Expectations ExplicitlyCommunicate clearly: committed OKRs expect a 1.0 score, with any miss requiring a postmortem. Aspirational OKRs expect an average of 0.7. This prevents the confusion of treating all goals with the same yardstick.
- Calibrate the Basket RatioDecide the strategic balance between committed and aspirational OKRs for this cycle. Are you in survival mode needing operational excellence? Weight toward committed. Are you seeking market disruption? Weight toward aspirational. This ratio is a cultural choice that should evolve.Pro tipCommitted OKRs should credibly consume most but not all available resources. If a team can meet all their OKRs without full headcount, they're either hoarding resources or not pushing hard enough.WarningIf you have zero aspirational OKRs, you're guaranteed not to achieve anything breakthrough. If you have zero committed OKRs, your operational foundation may crumble.
- Carry Forward Unfinished Aspirational OKRsUnlike committed OKRs which are retired after each cycle, aspirational OKRs should remain on the list until completed. Dropping them due to lack of progress disguises persistent resource or prioritization problems.Pro tipIf an aspirational OKR stalls, consider reassigning it to a different team with both the expertise and bandwidth to tackle it more effectively.
Chrome's 20 million user target in 2008 was clearly aspirational -- they started from zero. When they missed, they didn't abandon the goal. They carried it forward, raising it to 50 million (missed at 38 million), then 111 million. Each failure drove innovation in distribution, marketing, and platform expansion.
The Gates Foundation balanced committed OKRs (like achieving 80% vaccination coverage in 90% of districts, a measurable operational target) with aspirational OKRs (like global eradication of malaria by 2040). The committed goals kept the operation accountable; the aspirational goals maintained the transformative ambition.
This classification evolved at Google as the company matured its OKR practice. Early on, all OKRs were treated similarly, but leaders discovered that mixing operational must-haves with ambitious moonshots without differentiation caused confusion. Teams didn't know whether a 70% score was excellent (for a stretch goal) or concerning (for an operational commitment). Google formalized the two-basket system in their internal OKR playbook, creating different scoring expectations and different management responses for each type.