Committed vs. Aspirational OKRs: How to Prioritize When Everything Can't Be Top
Many small and medium sized organizations don't run a full department-by-department OKR cascade. Instead, everyone works off the same 3 to 5 shared Objectives for the quarter. That's a good thing. It keeps the whole organization focused on the same priorities instead of splintering into 10 different agendas. But it creates a problem the moment resources get tight: if all the Objectives look equally important on the page, how does a team know which one to protect when they can't do everything at once? The answer is to explicitly label each Objective as either committed or aspirational.
What Committed and Aspirational Actually Mean
This distinction comes from Google's own OKR practice, described in detail in Google's re:Work guide to goal setting. A committed Objective is one the organization has agreed must be hit this cycle. It's already resourced, it may depend on external commitments like a customer deadline or a regulatory filing, and missing it has real consequences. An aspirational Objective is a stretch goal. It represents real ambition and upside, but the organization accepts going in that it might land at 70% and that's still a win. Both types are valuable. The mistake is treating them the same way when it comes to prioritizing time and attention.
Why This Matters Most Without a Team-Level Cascade
In a large organization with a full cascade, a marketing team might work almost entirely off one department Objective, so prioritization is somewhat built in. In a smaller organization where everyone shares the same 3 to 5 Objectives, that built-in filter doesn't exist. Every employee is, in effect, choosing which of the shared Objectives to lean into on any given day. Without a committed/aspirational label, that choice gets made by instinct, or worse, by whichever Objective was mentioned most recently in a meeting. Labeling the Objectives up front removes the guesswork: when someone has two hours and three things they could work on, the committed Objective wins.
How to Decide Which Objectives Are Committed
Not every Objective deserves the committed label, and treating everything as committed defeats the purpose entirely. A useful filter is to ask three questions. Is this Objective already resourced with people and budget, or does it depend on funding or hiring that hasn't happened yet? Does it have a hard external dependency, such as a customer contract, a compliance deadline, or a partner commitment, where missing it creates a real cost? And is the path to achieving it reasonably well understood, or is it still an open question the organization is exploring? Objectives that are resourced, externally tied, and well understood belong in the committed bucket. Objectives that are exploratory, dependent on things going right, or represent a genuine stretch belong in the aspirational bucket.
How Scoring and Expectations Should Differ
The label should change how success is judged at the end of the cycle, not just how people prioritize during it. A committed Objective that lands at 70% is a missed commitment and deserves a real conversation about what went wrong, whether it was under-resourced, or whether the timeline was unrealistic. An aspirational Objective landing at 60-70% is exactly what a stretch goal is supposed to look like. As Christina Wodtke writes in Radical Focus, a stretch Objective you hit 100% of the time was never actually a stretch, it was a sandbagged target. Holding both types of Objectives to the same 100% bar either punishes ambition or hides real misses behind a culture of lowered expectations. Keeping the bar different for each type keeps both honest.
A Worked Example
Picture a 40-person software organization running three shared Objectives for the quarter with no team-level cascade underneath them. "Ship the enterprise SSO feature our largest customer is contractually waiting on" is marked committed, because it's fully staffed, has a signed customer deadline, and the engineering work is well understood. "Cut average onboarding time for new customers in half" is marked aspirational, because the team has ideas but hasn't validated which changes will move the number, and a 50% cut is a genuine stretch. "Explore a self-serve pricing tier as a new growth channel" is also marked aspirational, since it's an open bet with no committed budget yet. Everyone in the organization now knows: if the SSO work and the onboarding project both need attention on the same afternoon, SSO wins, because a missed commitment there has a contractual cost the other two Objectives don't carry.
Making the Label Visible, Not Just Understood
A label that only lives in a planning document gets forgotten by week three. It should show up wherever the Objective itself shows up, in the OKR tool, in the weekly check-in, and in any status update sent to leadership. When a committed Objective starts slipping, that should trigger a different kind of conversation than an aspirational one falling behind. Making the distinction visible everywhere, not just at planning time, is what turns it from a one-time exercise into an actual prioritization tool the whole organization uses every week.
References
- Set Goals with OKRs — Google re:Work
- How OKRs Can Help Your Team Set and Achieve Bold Goals — Harvard Business Review
- Radical Focus: Achieving Your Most Important Goals with Objectives and Key Results — Christina Wodtke
- Measure What Matters — John Doerr