A moonshot is an OKR target set at 10x ambition; teams expect to reach 60-70% at best. A roofshot is a committed target set to be achieved 100%. Both types belong in a healthy OKR program. Mixing them without distinction is one of the most common reasons OKR programs lose credibility within two quarters.
In this guide
- What Is a Moonshot in Business?
- What Is a Roofshot OKR?
- What Is the Difference Between Moonshots and Roofshots?
- Why Most Companies Get This Wrong (And Why It Kills OKR Programs)
- How Do You Decide Whether an OKR Should Be a Moonshot or Roofshot?
- How OKRs Bridge Stage-Gate Governance and Agile Delivery
- What Does a Hybrid Moonshot and Roofshot OKR Program Look Like?
- How Do You Score Moonshots and Roofshots Differently?
- Frequently asked questions
What Is a Moonshot in Business?
The term entered mainstream strategy vocabulary through Google’s X division, which describes a moonshot as a “10x improvement” on a known problem, not a 10% optimisation. In OKR terms, a moonshot key result is a target you genuinely do not know how to hit today. Reaching 70% is considered a success. Reaching 100% signals the target was set too low.
The logic is deliberate. When a team sets a target they already know how to hit, the planning process defaults to the familiar. Moonshots force a different kind of thinking: resource reallocation, new methods, partnerships that would not surface in a conventional planning cycle.
Ambitious targets don’t cause teams to fail. Treating ambitious targets as performance commitments does.
The failure mode is specific. When a leadership team sees a 70% score on a moonshot and reads it as underperformance, the team learns quickly to set safer targets. Within two or three quarters, the OKR program converges on goals that are easy to achieve and meaningless to track. The moonshot vocabulary survives; the stretch intent does not.
What Is a Roofshot OKR?
A roofshot (also called a committed OKR) is a target the team commits to hitting 100%. Missing it is not a “learning opportunity.” It requires a root-cause conversation and a recovery plan. Roofshots govern the work that keeps the business running: retention targets, delivery SLAs, compliance milestones, revenue commitments.
The name comes from the idea of shooting for the roof rather than the moon. Ambitious enough to require real effort, but defined by what the structure can hold, not what imagination allows. You are not trying to reinvent; you are trying to deliver reliably.
Roofshots carry a different planning burden. Because the team commits to 100%, the target must be backed by a credible plan covering resourcing, dependencies, and risk mitigation before the quarter starts. Agreeing to a roofshot without that plan is not commitment; it is optimism with a deadline.
A roofshot without a delivery plan is a number written on a whiteboard. It is not a commitment.
What Is the Difference Between Moonshots and Roofshots?
The distinction is not about difficulty. Both require real effort. The difference lies in what a miss means and what the team should do when it happens.
| Dimension | Moonshot | Roofshot |
|---|---|---|
| Target ambition | 10x, beyond current capability | Achievable 100% with strong execution |
| Success at 70% | Yes, expected and accepted | No, triggers a review conversation |
| Miss signal | Learning, re-scope, iterate | Execution breakdown: investigate |
| Planning requirement | Direction plus hypothesis | Full delivery plan required |
| Best for | Innovation, growth, new markets | Operations, delivery, compliance, retention |
| OKR score calibration | 0.6 to 0.7 equals success | 1.0 expected; below 0.7 is an issue |
| Compensation link | Never — removes risk appetite | Sometimes, but with care |
Why Most Companies Get This Wrong (And Why It Kills OKR Programs)
The conventional advice says: set ambitious OKRs, stretch your team, aim for the moon. What this advice rarely explains is that ambition without target-type discipline creates a category error that surfaces at quarter-end review.
The pattern goes like this. A leadership team, energised by OKR training, sets every objective as a moonshot. The sales team sets a 10x pipeline target. Operations sets a 10x efficiency target. Finance sets a 10x cost reduction goal. Quarter end arrives. Everyone scores 0.5 to 0.6. Leadership reads the room as underperformance. Teams feel demotivated. The OKR programme quietly gets abandoned before Q3.
The underlying problem is that some work cannot be moonshot. SLA commitments, payroll systems, regulatory deadlines, customer retention floors: these require 100% delivery, not 70%. Setting a moonshot target on a committed operational outcome tells the team it is acceptable to deliver 70% of payroll on time. It is not.
Common OKR Failure Pattern
The target-type confusion described above is a structural problem. Teams that run all OKRs as moonshots without committed targets lose accountability within two to three quarters. The solution is not fewer OKRs. It is clearer target-type assignments before the quarter begins.
The fix is not choosing one type over the other. A well-run OKR program needs both. Moonshots where the ceiling should be pushed. Roofshots where the floor cannot drop. The discipline is in knowing which is which before the quarter starts, not after it ends.
How Do You Decide Whether an OKR Should Be a Moonshot or Roofshot?
Three questions resolve the ambiguity in most cases:
What happens if this goal reaches 70%?
If 70% delivery is acceptable and creates meaningful progress, it is a moonshot. If 70% delivery causes harm to customers, the business, or regulatory standing, it is a roofshot.
Does the team already know how to reach the target?
If the path is unknown and requires new approaches: moonshot. If the path is known and requires disciplined execution: roofshot.
Is this goal connected to performance evaluation or compensation?
Never link moonshots to individual compensation. It destroys risk appetite immediately. Roofshots can be linked if calibrated carefully, but Google’s own OKR guidance recommends separating performance ratings from OKR scores entirely.
A practical starting point: in a quarter with 4 to 6 company-level OKRs, roughly 60 to 70% should be roofshots that protect operational performance, with 30 to 40% as moonshots that test growth and innovation hypotheses. These proportions shift by function. An R&D team may run more moonshots; a customer success team runs more roofshots.
Ready to Run Both Moonshot and Roofshot OKRs?
How OKRs Bridge Stage-Gate Governance and Agile Delivery
The moonshot/roofshot distinction is not a target-setting problem. It is a systems problem, and most organisations are solving the wrong one.
Two different execution models run inside most organisations simultaneously, and they operate on different logic. Stage-gate models govern large project portfolios: phase reviews, go/no-go decisions, investment gates. These are the structures that protect against runaway spend on low-probability outcomes. Agile delivery models run in parallel: sprint cycles, two-week iterations, continuous deployment. These are the structures that keep teams moving when the goal is known but the path is uncertain.
OKR key results are the most natural gate criteria that exist: measurable, time-boxed, aligned to strategy. Most portfolio governance functions have not realised this yet.
The bridge works like this: quarterly key results function as stage-gate criteria, defining what the project portfolio must prove by quarter-end before the next phase unlocks. Sprint goals operate as the execution units within that frame. A moonshot OKR at the company level drives a series of agile sprints that test the hypothesis. A roofshot OKR at the team level drives a series of committed sprint deliveries with known scope.
The problem most organisations face is structural: their stage-gate governance and their agile delivery model operate in separate tools, separate meetings, and separate planning cycles. Strategy sits in one place. Execution data sits in another. OKRs get scored in a spreadsheet. The connections are made manually, or not at all.
Connected OKR + PPM Architecture
Strategy, project execution, and OKR governance in one connected system
A connected OKR and PPM integration connects strategy directly to project execution. Quarterly key results cascade to project portfolios. Sprint-level tasks link back to the OKRs they serve. AI-powered quality review scores every key result before the quarter starts, catching vague targets that would blur the moonshot/roofshot line before they waste 90 days. AI-powered alignment tracking ensures stretch and committed goals cascade correctly from company level to individual contributors.
A connected platform supports both target types natively, without requiring a separate portfolio tool, a separate performance tool, or a manual data reconciliation process.
For teams managing agile goal management at scale, the distinction between moonshots and roofshots maps cleanly onto sprint planning. Innovation sprints align to moonshot OKRs. Delivery sprints align to roofshot OKRs. The cadence is the same. The accountability model differs.
What Does a Hybrid Moonshot and Roofshot OKR Program Look Like?
A company at 500 to 2,000 employees running a mature OKR program typically structures the quarter as follows:
The moonshot objective is assigned to a growth squad with access to new resource. The roofshot objective is owned by customer success with a delivery plan, risk register, and weekly check-in cadence already in place. Both objectives sit in the same OKR platform, scored on the same cadence, visible in the same executive dashboard, but evaluated against different success criteria.
The key discipline is labelling each OKR as moonshot or roofshot before the quarter begins, not after it ends. When teams skip this step, every missed target generates the same uncomfortable conversation: was this a stretch that fell short, or a commitment that failed? Without the label, there is no clear answer.
How Do You Score Moonshots and Roofshots Differently?
OKR scoring runs on a 0.0 to 1.0 scale. The scoring interpretation differs by target type:
Moonshot Scoring
Roofshot Scoring
One scoring principle applies to both types: never use the same rubric for both in the same OKR review. A 0.7 on a roofshot is a problem. A 0.7 on a moonshot is a win. Teams that do not distinguish the two types during review training learn the wrong lesson from the same data.
Speed without direction is faster failure. But so is precision without ambition. You need both target types to run a complete OKR program.
Key Takeaways
- →Moonshots are 10x targets where 70% delivery is success. Roofshots are committed targets where 100% delivery is expected.
- →The distinction is not about difficulty. It is about what a miss means and what the team should do when it happens.
- →Setting all OKRs as moonshots is one of the fastest ways to destroy an OKR program’s credibility.
- →OKR quarterly key results serve as natural stage-gate criteria, connecting portfolio governance to agile execution in a single cycle.
- →A healthy OKR program runs both types simultaneously: moonshots where the ceiling should be pushed, roofshots where the floor cannot drop.
Get Started
Frequently Asked Questions
A moonshot OKR is a stretch objective set at 10x ambition. Teams expect to reach 70% at best. It signals direction and tests what the organisation is capable of, not what it can guarantee.
A roofshot OKR is a committed target set to be achieved 100%, not partially. It governs delivery, operations, and business-critical outcomes where missing the number has direct consequences for customers or the business.
Moonshots are aspirational targets designed to push innovation; a 70% score is success. Roofshots are committed targets designed to guarantee results; anything below 100% requires a root-cause review. Most OKR programmes need both types running simultaneously.
No. Setting all OKRs as moonshots is one of the most common OKR mistakes. It erodes accountability. Teams that miss committed targets every quarter stop trusting the OKR process entirely; the programme collapses within two to three quarters.
A connected OKR platform supports both target types natively. AI-powered quality review flags ambiguity in key results before the quarter starts, and alignment tracking ensures stretch and committed goals cascade correctly from company level to individual contributors, all in one platform.
