What are Aspirational OKRs?

Aspirational OKRs, also known as "moonshots" or stretch goals, are deliberately ambitious objectives that exceed an organization's current capabilities. They are scored on a 0.0 to 1.0 scale with an expected average of 0.6 to 0.7, meaning teams are not expected to fully achieve them, but the pursuit drives innovation and outsized growth.

TL;DR

Scoring sweet spot: Aspirational OKRs target 0.6 to 0.7 on the 0.0 to 1.0 scoring scale; hitting 1.0 means the bar was set too low.
Two-track system: Most mature OKR programs run aspirational and committed OKRs in parallel, with different scoring expectations and review cadences.
Carry forward, not write off: Aspirational OKRs persist across quarters until achieved, unlike committed OKRs which expire at cycle end.
Wrong fit for survival mode: Teams under existential pressure, hard regulatory deadlines, or low psychological safety should default to committed OKRs.

What problems do aspirational OKRs solve?

Aspirational OKRs solve four problems that incremental goal-setting cannot.

Anti-sandbagging: Teams that score 1.0 every quarter learn to set safer goals next quarter. Aspirational OKRs break the loop by making 0.6 to 0.7 the win condition.
Innovation forcing function: A 10x goal cannot be hit by improving the current approach 10%. The math forces a redesign, not an optimization.
Talent magnet: Ambitious goals signal that the company is solving problems worth a strong operator's career years.
Alignment to vision: Aspirational OKRs translate a long-horizon vision into a goal the current quarter can start moving toward.

OKRs are big, not incremental. We don't expect to hit all of them. If we do, we're not setting them aggressively enough.

― John Doerr, author of Measure What Matters

Aspirational OKRs vs committed OKRs

Most mature OKR programs run a two-track system. Committed OKRs are operational commitments the team must hit; aspirational OKRs are stretch bets the team is willing to fall short on. Mixing the two scoring expectations is one of the most common OKR mistakes.

Dimension	Aspirational OKRs	Committed OKRs
Target score	0.6 to 0.7	0.9 to 1.0
Confidence at quarter start	50% or less	90% or higher
What "miss" means	Expected, useful signal	Resource or planning failure
Resource model	Discover what's needed mid-cycle	Resources locked at planning
Cycle behavior	Carry forward across quarters	Expire at cycle end
Best fit	Innovation bets, new markets, R&D	Roadmap delivery, SLAs, compliance

How to write aspirational OKRs

Effective aspirational OKRs share five drafting decisions. Skip any of them and the goal collapses into either a fantasy or a disguised committed OKR.

Anchor the objective to a customer or market outcome, not an internal milestone. "Become the default OKR platform for European mid-market" beats "Ship 12 product features."
Make every key result a number with meaningful magnitude. Weak metrics let the team rationalize incremental work.
Pre-commit to a confidence score under 50%. If the team is confident at planning, the goal isn't aspirational.
Decouple the score from compensation. Tying aspirational scores to bonus checks is the fastest way to kill ambitious goal-setting.
Plan the OKR cycle for mid-quarter pivots. Aspirational OKRs surface information the original plan didn't have.

Where aspirational OKR rollouts typically break

Most aspirational OKR programs fail in predictable ways. The failures are rarely about goal-setting theory; they are about how the program interacts with the rest of the organization.

Score-to-bonus drift: Once finance asks how OKR scores feed performance reviews, the team starts sandbagging the next quarter. Keep aspirational scores out of the comp cycle.
Mixed scoring expectations: Leaders praise a 0.9 on an aspirational OKR, and the team learns the real target was always 0.9. The next aspirational OKR is a committed OKR in disguise.
No mid-cycle course correction: The quarterly cadence assumes the plan survives contact with reality. Aspirational OKRs rarely do. Without a check-in, the team grinds against a stale plan.
Too many aspirational bets at once: A team running four aspirational OKRs is running zero. Focus is a feature, not a constraint.
Senior leaders absent from the goal: Aspirational OKRs need air cover. If the leader who signed off goes quiet at the first miss, the next ambitious goal lands flat.

When not to use aspirational OKRs

Aspirational OKRs are the wrong tool in three specific situations, even for organizations otherwise running a strong OKR program.

Runway pressure. A startup with under 12 months of runway needs committed delivery, not stretch ambition. Set committed OKRs against the metrics that extend runway.
Hard regulatory or contractual deadlines. A SOC 2 audit window or a signed SLA is a committed OKR by definition. Calling it aspirational softens accountability without changing the deadline.
Low psychological safety. Teams that fear visible failure will sandbag aspirational OKRs into committed OKRs anyway. Fix the safety problem first.

Edwin Locke and Gary Latham's 1990 meta-analysis "A Theory of Goal Setting and Task Performance" found that specific, challenging goals outperformed easy or "do your best" goals in roughly 90% of studies reviewed. The performance gap collapsed when goals exceeded participants' perceived ability, which is the empirical case against aspirational OKRs without the cultural foundation to support them.

Examples of aspirational OKRs

Two illustrative aspirational OKRs, each as one objective with three key results.

Product organization (B2B SaaS)

Objective: Become the default goal-management platform for European mid-market companies.
KR1: Grow EU mid-market ARR from EUR 8M to EUR 25M.
KR2: Reach a net retention rate of 130% in the EU mid-market segment.
KR3: Publish 50 named customer case studies from EU mid-market accounts.

Internal platform team

Objective: Eliminate the build-and-deploy bottleneck for product engineering.
KR1: Cut median PR-to-production time from 4 days to 4 hours.
KR2: Take deployment failure rate from 6% to under 1%.
KR3: Reach 95% engineer satisfaction with the internal platform on the quarterly survey.

Using aspirational OKRs in your next planning cycle

Aspirational OKRs are not a separate methodology. They are one half of a two-track system that pairs with committed OKRs to keep day-to-day delivery and long-horizon ambition running in parallel. Most organizations introduce aspirational OKRs only after a few cycles of committed OKRs have stabilized the cadence, the scoring conversation, and the connection between organizational alignment and quarterly planning.

Once that foundation is there, three operating defaults make the difference between a program that compounds and one that quietly degrades into committed OKRs in disguise: cap aspirational OKRs at one or two per team per quarter, keep aspirational scores out of the compensation cycle, and carry unfinished aspirational OKRs forward instead of writing them off at quarter end.

What is the difference between aspirational and committed OKRs?

Committed OKRs are operational goals the team must deliver, scored against a 0.9 to 1.0 target. Aspirational OKRs are stretch goals scored against a 0.6 to 0.7 target, and they often carry forward across multiple quarters until achieved.

What score should an aspirational OKR have?

Aspirational OKRs target a final score of 0.6 to 0.7 on the 0.0 to 1.0 scale. Google's published guidance treats 0.7 as the expected average score for aspirational goals; consistently scoring 1.0 is a signal the targets were not ambitious enough.

Are aspirational OKRs the same as moonshots?

Aspirational OKRs and moonshots are closely related but not identical. Moonshots are the most ambitious end of the aspirational spectrum, often 10x rather than 10%, while aspirational OKRs cover any goal set deliberately beyond current capability.

How many aspirational OKRs should a team set?

One or two aspirational OKRs per team per quarter is the standard cap. Running more than two splits attention across stretch bets that each need full focus, so the practical result is that no aspirational OKR gets the resourcing it actually needs.

Should aspirational OKR scores affect compensation?

No. Tying aspirational OKR scores to bonuses or performance reviews is the fastest way to kill ambitious goal-setting, because individuals rationally start sandbagging targets to protect their compensation. Keep aspirational scoring decoupled from comp.

When should a team avoid aspirational OKRs?

Avoid aspirational OKRs when the organization has short runway, hard regulatory deadlines, or low psychological safety. In those conditions, committed OKRs produce better outcomes because the team needs predictable delivery, not stretch ambition.