Committed vs Aspirational OKRs

What is the difference between committed and aspirational OKRs?

committed vs aspirational OKRs is a key topic in modern project management and teamwork. A committed OKR is a goal the organization agrees will be achieved, and the team is willing to move schedules and resources to deliver it. An aspirational OKR expresses how the team would like the world to look, without yet having a clear path or the resources to get there.

Google’s own OKR playbook states the split plainly: “The expected score for a committed OKR is 1.0; a score of less than 1.0 requires explanation for the miss, as it shows errors in planning and/or execution.” Aspirational OKRs, by contrast, “have an expected average score of 0.7, with high variance.”

That variance matters. A committed OKR is pass or fail. An aspirational OKR is read as a band, because the whole point is that the team is exploring.

The two types share the same structure: one objective, three to five key results, a numeric target, a baseline, and a deadline. Only the contract around the score changes.

Where does the 0.7 expectation come from?

It comes from Google’s published OKR guidance, public since 2016 on re:Work and popularized by John Doerr’s *Measure What Matters*. Google’s guidance sets the sweet spot somewhere in the 60–70% range and notes that scoring consistently higher may mean the goals are not being set high enough.

The nuance most teams miss: the 0.7 norm was never meant for every OKR in the company. Google’s playbook splits it by type. Applying 0.7 to a committed OKR turns a broken promise into an acceptable result. Applying 1.0 to an aspirational OKR turns ambition into a disciplinary hearing.

A second nuance: 0.7 is an average across a portfolio, not a target for each goal. If every stretch OKR lands at exactly 0.7, the team has learned to aim at the score rather than the outcome. High variance is the healthy signal.

How do you label OKRs without creating bureaucracy?

Use one visible marker and one field: an “A” or “C” in front of the objective title, plus the type recorded wherever the goal lives. Then apply three rules. Label at planning, never at grading — if the label first appears in the retro deck, it is an alibi. Label the objective, and state explicitly when one key result inside an aspirational objective is a hard commitment, because that is the line a grader reads. And never relabel to soften a result; if a stretch goal becomes achievable, relabel it in the next cycle.

A useful test at planning time: ask “if we miss this by 20%, who outside this team is harmed?” A customer, a regulator, a partner, or another team’s roadmap means committed. “Nobody, we just learned something” means aspirational.

What mix should a team actually run?

Most mature programs run mostly committed OKRs with one or two aspirational bets. The exact ratio should follow how much of the quarter is already spoken for by external commitments before the OKR exercise starts.

Google’s playbook adds a resource test that is more useful than any ratio: a team’s committed OKRs should credibly consume most, but not all, of its available resources. Committed plus aspirational OKRs together should credibly consume somewhat more than the team has. If the full set fits comfortably inside capacity, the goals are effectively all commitments and nothing is stretching.

Worked example: a team of eight

A platform team of eight engineers has 8 people × 10 working days × 6 productive hours = 480 hours per two-week sprint, or roughly 6,240 hours across a 13-week quarter after holidays.

• Committed OKR: migrate the billing service, estimated at 3,400 hours. That is 54% of capacity.
• Committed OKR: cut p95 checkout latency, estimated at 1,200 hours. Running total: 74%.
• Aspirational OKR: reduce infrastructure spend per transaction by 40%, estimated at 2,600 hours if everything works.

The committed work fits with 26% slack for support, incidents, and interviews. Adding the aspirational bet pushes demand to 115% of capacity. That is the intended shape: commitments are safe, the stretch is not, and the team knows which one gets sacrificed when the quarter gets hard.

Reverse the labels and the plan collapses. If the infrastructure bet is labeled committed, the team will defend it in every prioritization meeting and let the billing migration slip. If the migration is labeled aspirational, nobody will move anything to protect it.

How do you grade each type?

Grade a committed OKR as pass or fail, and grade an aspirational OKR on a band. In both cases the objective score is the average of its key results, unless weights were agreed before the cycle started.

For aspirational goals, a common reading is 0.7–1.0 as green, 0.4–0.6 as yellow, and 0.0–0.3 as red. That band is a communication device, not a performance rating.

Worked example: a committed OKR that scored 0.86

A support team commits to “make onboarding predictable for every new enterprise account.” Four key results, each worth 25%:

Average: (0.90 + 0.93 + 0.83 + 0.80) ÷ 4 = 0.865. The team “mostly” delivered. Under a committed label, that is a miss, and the review should ask which estimate was wrong and which dependency was not secured. Under an aspirational label, 0.865 would be a strong quarter. The same spreadsheet produces two completely different conversations, which is exactly why the label cannot be decided after the fact.

Read aspirational scores on a band instead: 0.7–1.0 green, 0.4–0.6 yellow, 0.0–0.3 red. A product team that lands 0.57 on a self-serve bet has a yellow quarter — the direction is plausible, the motion is not working, and the useful output is a specific story about which lever moved, not a grade.

Why does mixing the labels destroy both meanings?

Because an unlabeled 0.7 can be either a success or a failure, and the team will assume whichever interpretation is safer. Google’s playbook names this as its first classic trap.

The failure runs in both directions. Marking a committed OKR as aspirational increases the chance it fails: the team does not take it seriously, does not move other priorities to protect it, and treats the shortfall as normal. A launch date that other teams built their quarter around quietly becomes a maybe.

Marking an aspirational OKR as committed creates defensiveness. The team cannot find a way to deliver, so it either burns out or games the metric, and it learns that ambition is punished. Next quarter it sets targets it can hit without changing anything.

The second-order effect is worse. Once labels stop predicting consequences, the rational move for every team is to label everything committed and set comfortable targets. The portfolio becomes a list of certainties, and the organization loses the mechanism it created to find upside.

When does an aspirational OKR become committed?

When the path is clear enough to promise. The usual pattern is that a stretch goal stays on the list for several cycles, carries forward unmet key results, and is relabeled committed once the team knows how to finish it within one cycle. Two signals mark the shift: the team can name the sequence of work and the resources required, and a miss would now damage someone outside the team because other plans have started to depend on it. The reverse move should be rare and loud — legitimate when a dependency collapses, but it needs a written note and a named owner, not a quiet edit in the goal tool.

How do you keep the labels honest across a quarter?

Three habits do most of the work. Review last cycle’s labels before setting new ones, and ask whether any “aspirational” goal was a commitment in disguise. Keep scores out of compensation — the moment pay attaches to a number, every stretch target becomes a commitment in everyone’s head. Write one line of context per score, because six months later that sentence is the only thing that explains the quarter.

Make the labels visible where the work happens, too. If goals live in a spreadsheet only managers open, the label never reaches the people making daily trade-offs.

Where does Doitify fit?

The label is a promise about resources, and resources live in the same place as tasks, owners, and deadlines. When goals sit in one tool and the work sits in another, the committed/aspirational distinction becomes a quarterly argument instead of a planning constraint.

Doitify is built for that link: an objective becomes a project with tasks, sub-tasks, checklists, owners, and dates, and progress rolls up in work and performance reports. Kanban boards, Gantt charts, sprints, backlogs, and workload views show whether the committed work actually has capacity behind it — the only test that matters when a stretch goal starts competing for the same people.

A transparency note: Doitify is our product, and we build it because this problem is common. The split itself runs fine on a whiteboard and a shared document. A tool helps when you need the labels to survive contact with a real quarter.

What mistakes should you avoid?

• Using 0.7 as a universal target. It applies to aspirational OKRs; commitments are graded at 1.0.
• Labeling in hindsight. A stretch label added after the result is a negotiation, not a plan.
• Setting only aspirational OKRs. Nothing is promised, and the boring revenue commitments go unowned.
• Setting only committed OKRs. The portfolio becomes a plan, and the organization stops discovering what is possible.
• Filling capacity with commitments. If the committed set uses 100% of resources, there is no room for the bet or for reality.
• Rewarding the score instead of the outcome. A team that hits 1.0 on a sandbagged target has learned the wrong lesson.
• Skipping the guardrail key result. A growth goal without a quality or cost guardrail invites damage the score will never show.

How do you write a committed OKR that still leaves room to learn?

The label is not a mood; it is a promise about what happens when the number is missed. Write committed OKRs with a clear deliverable, a date, and a single owner. Write aspirational OKRs with a direction, a stretch threshold, and an explicit learning question.

Here is the same team writing both:

• Committed: “Reduce average support first-response time from 9.4 hours to under 4 hours by 31 March, owned by the support lead.” The team must reorganize shifts and staffing to hit it. Missing the target triggers a written explanation and a recovery plan.
• Aspirational: “Cut the share of tickets that require a second contact from 31% to 15% by year end, owned by the support lead, exploring self-service and routing changes.” Hitting 19% is a strong result. Missing 25% is a signal that the hypothesis was wrong, not that the team failed.

The language test is simple. Committed goals use verbs the team controls: ship, migrate, reduce, sign, close. Aspirational goals often include “explore”, “test whether”, or “redesign” because the path is genuinely uncertain. If a committed OKR contains “explore”, it is mislabeled. If an aspirational OKR contains a hard contractual deadline, it is secretly committed.

Grade them differently, too. Committed goals are pass or fail with a recovery conversation. Aspirational goals get a 0–1 score and a short retrospective on what the score taught you. Teams that apply the same red-amber-green dashboard to both labels end up with either sandbagged commitments or demoralized stretch goals.

Conclusion

The committed/aspirational split is not a labeling convention. It is a contract about what the organization will fund, what other teams can depend on, and how a shortfall will be read.

Get it right and two things happen at once: the promises get kept, because the team is allowed to protect them, and the bets get made, because nobody is punished for missing a target designed to be missed. Get it wrong and you get the worst of both — commitments that slip quietly and ambitions that never get funded.

Label at planning. Grade by type. Fund the commitments first. Then let one or two goals be genuinely unreasonable.

If this post on committed vs aspirational OKRs was helpful, you might also enjoy How to Prevent Resource Overallocation (Step-by-Step Guide) and Project Planning: A Complete Step-by-Step Guide.