Committed OKR, Roofshot and Operational OKR: firm commitments

A Committed OKR is an Objective or a Key Result the team commits to hitting at 100%. It's the functional opposite of the Aspirational OKR, which is fine at 70%.

The Committed OKR is the tool for operational predictability. It's used for customer commitments, regulatory compliance, critical milestones, or any outcome whose failure would carry serious consequences.

Roofshot OKR: aim for the roof, not the moon

A Roofshot OKR is the most common form of Committed OKR. The term contrasts with moonshot: you're not aiming for the moon, you're aiming for the roof. A roofshot is ambitious yet reasonable, and the team can reasonably hit it at 100% through disciplined execution.

Example: "Land SOC 2 Type II compliance by end of quarter". It's ambitious (long, expensive), but it's not a moonshot: it's rigorous execution.

Operational OKR: the critical operational goal

An Operational OKR is a Committed OKR on the routine functioning of the business, as opposed to transformation or innovation Objectives. Examples:

• Maintain a 99.9% availability SLA.
• Keep support response time under 2 hours.
• Deliver 100% of billed contracts on time.

Operational OKRs sometimes get pushback in the OKR community on the grounds that they look more like KPIs than progress goals. Fair point. But they have a use: making it explicit that operational performance is a cycle priority, especially when it's under threat.

Committed vs Aspirational: side-by-side

The right Committed / Aspirational blend

A mature OKR team blends both. A 50/50 ratio between Committed and Aspirational is sometimes cited, but that's a contextual heuristic, not a universal rule. The right ratio depends on the nature of the team:

• Product / Growth team in transformation mode: leaning 30% Committed, 70% Aspirational.
• Customer Success or Sales team on a mature portfolio: leaning 60-70% Committed.
• Security, Legal, Finance team: predominantly Committed, Aspirational stays the exception.
• Platform Engineering team: balanced blend, depending on phase (initial build vs mature run).

Rather than aiming for a ratio, ask: "if we tag this OKR Aspirational, what would the concrete cost of a 0.7 score actually be?". The answer calibrates the blend naturally.

What to avoid in all cases:

• Too many Committed: the team plays it safe, ambition dies, OKRs become a budget.
• Too many Aspirational: the team loses operational predictability, customer or regulatory commitments are at risk.

Example: a well-calibrated Committed KR vs an over-calibrated one

Well-calibrated. Platform team. Committed KR: "Maintain API availability above 99.9% in production." 100% is reachable through solid operational discipline. The team knows what to do to guarantee that result. Missing at 99.5% calls for serious analysis.

Over-calibrated. Same team. Committed KR: "Achieve 100% availability (zero downtime) on the production API this quarter." Strict 100% is humanly out of reach (third-party incidents, cloud dependencies, etc.). The team will overload its Initiatives to chase an objective no team in the world hits at 100%, and end up frustrated. That goal should have been Aspirational, or Committed at 99.95%.

Common Committed OKR mistakes

• Tagging every OKR as Committed to secure scores. Symptom: every OKR ends up at 0.95-1.0. The method loses its innovation role.
• Not explicitly tagging Committed vs Aspirational. Symptom: end-of-cycle conversations turn into negotiations about "what we promised". To settle at framing time.
• Tying Aspirational to variable comp. Toxic. Aspirational must stay strictly decoupled.
• Confusing Committed OKR and KPI. A Committed OKR is a commitment for the cycle, a KPI tracks continuous health. The two coexist.

Serendly insight: a Committed OKR must survive scrutiny

A good test for whether an OKR is truly Committed: "if we hit it at 80%, is that a serious failure that warrants analysis?". If yes, it's genuinely Committed. If the answer is "no, 80% is great", it's really Aspirational. Relabel it.

Calibrate your OKR commitments

Getting the Committed/Aspirational blend right is a management skill that develops cycle after cycle. Let's talk about how we support that calibration.

Request a demo