Committed OKR (Rooftop OKR)
A Committed OKR is a goal where 100% achievement is expected and required. It represents a firm commitment to the organization and typically relates to business-critical outcomes such as compliance, reliability, or essential revenue targets.
What is a Committed OKR?
A Committed OKR (also called Rooftop OKR) is an OKR where full achievement is expected. Unlike Moonshot OKRs, Committed OKRs are not stretch goals – missing one signals a serious problem requiring immediate attention.
When to Use Committed OKRs?
- Regulatory compliance: Data protection requirements, security standards, GDPR compliance
- Contractual obligations: SLAs and committed deliverables for customers
- Infrastructure reliability: Uptime guarantees, performance standards
- Business-critical revenue: Revenue targets funding ongoing operations
- Safety-related goals: Workplace safety, information security
A missed Committed OKR is not a "normal" failure – it requires root cause analysis and immediate action.
Committed OKR vs. Moonshot OKR
| Aspect | Committed OKR | Moonshot OKR |
|---|---|---|
| Expected achievement | 100% | 60–70% |
| Scoring interpretation | Below 1.0 = problem | 0.7 = success |
| Typical use | Operations, compliance | Innovation, growth |
| Consequence of missing | Root cause analysis | Learn and adapt |
Example of a Committed OKR
Objective: Ensure platform reliability for enterprise customers
- KR1: Maintain 99.9% uptime (maximum 8.7 hours downtime per year)
- KR2: Apply all critical security patches within 24 hours
- KR3: Keep Mean Time to Recovery (MTTR) under 30 minutes
All three Key Results must be achieved at 100%.
Best Practices for Committed OKRs
- Label clearly: Every OKR set should transparently show which OKRs are Committed and which are Moonshot
- Plan realistically: Committed OKRs should be planned based on reliable data and experience
- Allocate resources: Committed OKRs have resource priority over Moonshot OKRs
- Early warning system: Regular check-ins are especially important for Committed OKRs
Committed OKRs in Northly
Northly enables explicit labeling of OKRs as Committed or Moonshot. Scoring is adjusted accordingly, and the early warning system prioritizes Committed OKRs that are off track, ensuring timely corrective action.
Related Terms
Moonshot OKR (Aspirational OKR)
A Moonshot OKR (also called Aspirational OKR or Stretch OKR) is an intentionally over-ambitious goal where 60–70% achievement already counts as success. It pushes teams beyond their comfort zone and fosters innovation and creative thinking.
OKR Scoring
OKR Scoring is the structured process of evaluating Key Result achievement at the end of an OKR cycle. Typically a 0.0 to 1.0 scale is used, where a score of 0.7 (70%) is considered successful for stretch goals.
Key Result
A Key Result is a quantitative, measurable outcome that indicates progress toward an Objective. Each Key Result has a clear metric, a starting value, and a target value, answering the question: "How do we know we're on the right track?"
Frequently Asked Questions
What happens if a Committed OKR isn't achieved?
A missed Committed OKR requires root cause analysis: Why was the goal missed? Were resources insufficient, planning unrealistic, or were there unforeseen obstacles? The team must take immediate action.
How many Committed OKRs should a team have?
Typically 30–40% of OKRs are Committed and 60–70% are Moonshots. The exact mix depends on the industry – highly regulated industries tend to have more Committed OKRs.
Can a Committed OKR also be ambitious?
Committed OKRs should be planned realistically since 100% achievement is expected. The ambition lies in the importance of the goal, not its unreachability. For ambitious stretch targets, use Moonshot OKRs.
How do I distinguish Committed and Moonshot OKRs for my team?
Ask yourself: What happens if we miss this goal? If missing has business-critical consequences (compliance, SLAs, operations), it's a Committed OKR. If it's primarily about growth and innovation, it's a Moonshot.