12 Week Year vs OKRs: which system should you actually run?
Founder of Pilot · runs his own work in 12-week cycles ·
Short answer: OKRs are an alignment system — they excel at pointing many teams at shared outcomes. The 12 Week Year is an execution system — it excels at making one person or one team do the work, week after week. If you’re under ~50 people, or you’re an individual, run the 12-week system. If you’re aligning departments, run OKRs — and consider 12-week execution underneath them.
The comparison, dimension by dimension
Both systems reject annual planning, and both use roughly quarter-length cycles. The resemblance ends there. OKRs — from Andy Grove’s Intel via John Doerr’s Google — answer “what should everyone be aiming at, and are we getting there?” The 12 Week Year, from Brian P. Moran and Michael Lennington’s book, answers “did I do the things I committed to this week?” One measures outcomes; the other measures the lead measures that produce outcomes.
| Dimension | 12-week system | OKRs |
|---|---|---|
| Unit of commitment | 12-week goals with weekly tactics | Quarterly/annual Objectives with Key Results |
| What gets measured | Execution: % of committed actions done weekly | Outcomes: progress toward key results |
| Review rhythm | Weekly scorecard + WAM (15–30 min) | Bi-weekly/monthly check-ins, quarterly grading |
| Feedback latency | Days — a bad week is caught Friday | Weeks to months — a bad quarter is graded after |
| Built for | Individuals & teams of ~1–50 | Aligning many teams; 50–10,000+ people |
| Core failure mode | Too many goals, skipped scoring | Set-and-forget; check-in theater |
| Typical score target | ≥85% weekly execution | ~70% key-result attainment ('stretch') |
| Origin | The 12 Week Year (Moran & Lennington) | Intel (Grove) → Google (Doerr) |
Where OKRs win
Alignment at scale. When 12 teams could each locally optimize in conflicting directions, published objectives with measurable key results are the best-known coordination tool. OKRs also handle outcome uncertainty gracefully: a stretch key result graded at 70% is a fine quarter. If that’s your situation — many teams, genuine strategy communication problems — use a real OKR platform (Mooncamp and Perdoo are good), not Pilot.
Where the 12-week system wins
Execution certainty. OKRs famously say nothing about Monday morning: you can hold beautiful check-ins about a key result drifting sideways for eleven weeks. The 12-week system’s weekly tactics and execution score close that gap — commitments are weekly, binary, and scored, so drift is caught in days. For individuals and teams small enough to fit in one meeting, the alignment machinery of OKRs is pure overhead; the execution machinery of the 12-week method is exactly the missing piece.
The honest hybrid
At 50+ people, the strongest setup we’ve seen is OKRs for direction, 12-week execution underneath: company objectives set the “what matters”, each team translates its slice into a 12-week plan with weekly tactics, and the weekly score becomes the leading indicator for every key result. The systems meet in the weekly meeting, where scores do the reporting and humans do the unblocking.
Frequently asked questions
Yes, and larger companies often should: OKRs set the direction at company level, and teams execute their slice in 12-week cycles with weekly tactics and scores. The systems conflict only when you try to make OKRs do weekly execution or 12-week plans do company-wide alignment — each is bad at the other's job.
Chose weekly execution?
Pilot is the 12-week system as software: plans, scores, WAMs, and a scoreboard your team actually looks at.