What are Committed OKRs?

Committed OKRs are non-negotiable Objectives and Key Results a team agrees to deliver at 100% within a single cycle, usually a quarter. They cover work the organization must finish to stay on plan: revenue commitments, regulatory deadlines, launch dates. Falling short counts as a miss, not a stretch outcome.

TL;DR

100% is the bar: Committed OKRs are scored against full delivery, not against the 0.7 threshold used for aspirational goals.
Scoped to current operations: They map to revenue, retention, compliance, and shipping work the company already plans to fund this quarter.
Owner is named, not implied: Each committed OKR has a single accountable owner and a weekly confidence read tied to the OKR check-in cadence.
Most teams overcommit by 2-3x: The first cycle usually exposes more must-hit work than the team can actually deliver, which forces a real prioritization conversation.

Why "committed" sits next to "aspirational" in the OKR model

The committed and aspirational distinction comes from how Google internally separated must-hit work from moonshots. John Doerr formalized the split in Measure What Matters: committed OKRs are graded against 1.0, aspirational ones against 0.7, and conflating the two breaks the scoring math.

The point of keeping committed OKRs in the framework is to stop the goal-setting conversation from drifting entirely into ambition theater. Without a committed track, teams set only moonshots, miss the boring revenue commitments, and discover at the end of the quarter that no one was accountable for the work the business actually depended on.

Committed objectives are designed to be achieved in full (100 percent) within a set time frame. They must be met in full.

― John Doerr, author of Measure What Matters

What separates a committed OKR from an aspirational one

Both types share the same Objective + Key Results structure. What changes is the contract attached to scoring.

Dimension	Committed OKR	Aspirational OKR
Target completion	100%	60-70% counts as success
Also called	Roof shot	Moonshot, stretch, 10x
Typical scope	Revenue, retention, launch dates, compliance	New market entry, product reinvention, category creation
Resources	Fully funded before the cycle starts	Often requires pulling resources mid-cycle
Failure signal	Process or prioritization problem	Acceptable, expected on a fraction of attempts
Confidence at planning	High (above 70%)	Low to moderate (30-50%)

A useful test: if missing the target would force a board update or a customer apology, it belongs in the committed track. If missing the target would simply be a quarter where the bet didn't pay off, it belongs in the aspirational track. See the full breakdown in our aspirational vs committed OKRs guide.

How committed OKRs get set and tracked

Setting committed OKRs is closer to capacity planning than to brainstorming. The work has to fit inside the cycle and the team that owns it.

Start from the OKR cycle plan. List the outcomes the business has already committed to externally: signed revenue, contract renewals, regulatory filings, product launches with announced dates.
Translate each commitment into one Objective. Combine related work where possible to keep the total list short. Five committed OKRs per team is a high ceiling.
Define Key Results that prove the Objective in numbers. Each Key Result needs a baseline, a target, and a measurement source named at planning time, not improvised later.
Pressure-test capacity. If the team can articulate even one realistic scenario where they miss, the OKR is aspirational, not committed. Move it or cut it.
Assign one owner per OKR. Joint ownership reliably becomes nobody's ownership by week six.
Score weekly against confidence, not progress. A 70% confidence read is a yellow flag and triggers a check-in conversation.

Where committed OKR programs typically break

Three failure modes show up repeatedly when teams try to formalize the committed track:

Treating everything as committed. When the list runs past five Objectives per team, "committed" stops meaning anything and the cycle ends with a long tail of yellow scores no one acts on.
Calling stretch work committed for political reasons. Leadership pressure to look ambitious turns aspirational bets into committed targets, scoring tanks, and the team learns to pad next quarter's targets.
Skipping the capacity check. Committed OKRs assume the team can actually do the work. If hiring, vendor delivery, or another team's dependency is unresolved at planning, the commitment is a guess.

The fix in each case is the same: enforce the 100% bar at planning time, before the OKR enters the cycle. The grading conversation at the end is too late.

Using committed OKRs alongside aspirational ones

Most mature OKR programs run a mix. The exact ratio shifts with company stage, but a few patterns hold:

Early-stage and turnaround teams lean committed (often 80%+ committed) because survival depends on hitting specific revenue or runway numbers.
Scale-up and steady-state teams typically split 60-70% committed, 30-40% aspirational, giving room for the bets that drive next year's growth without abandoning this year's plan.
R&D and innovation labs invert the ratio, with aspirational OKRs in the majority and a small committed track for hygiene work.

The decision isn't ideological. It tracks how much of the team's quarter is already spoken for by external commitments before the OKR exercise starts.

What is the difference between committed and aspirational OKRs?

Committed OKRs are graded against 100% completion and cover work the team must deliver. Aspirational OKRs are graded against roughly 70% and cover stretch ambitions where falling short is expected. The split was formalized at Google and is documented in Measure What Matters.

How do you score a committed OKR?

Score each Key Result against its target, then average the Key Result scores for the Objective. A committed OKR is considered successful only when it scores at or near 1.0. Anything below 0.8 on a committed OKR signals a planning or execution problem, not an acceptable stretch result. See our OKR scoring guide for the full method.

Can a committed OKR be changed mid-cycle?

Yes, but rarely. A committed OKR should only be rescoped mid-cycle if the underlying business commitment has changed (a deal collapsed, a regulation moved, a customer cancelled). Rescoping because the team is behind is usually a sign the OKR was aspirational from the start.

How many committed OKRs should a team have per quarter?

Three to five is the practical ceiling for most teams. Beyond five, weekly attention fragments and the "100% or miss" contract stops being credible. Teams with more than five commitments typically need to merge related Objectives or shift work outside the OKR system.

Are KPIs the same as committed OKRs?

No. KPIs are ongoing health metrics the team monitors continuously, while committed OKRs are time-boxed Objectives with specific completion targets for the cycle. A KPI like "monthly active users" runs forever; a committed OKR like "grow MAU from 40k to 55k by end of Q3" attaches a deadline and a delivery contract. See our OKRs vs KPIs comparison for the boundary.

Who decides whether an OKR is committed or aspirational?

The OKR owner proposes the classification at planning, but it is ratified by the team's manager and aligned with the broader cycle plan. Putting the call in a single person's hands without review reliably produces mislabeled OKRs, because the political incentive is to label stretch work as committed.