The Mathematics of OKRs
Objectives and Key Results (OKRs) are often reduced to corporate cheerleading. In reality, they are a mathematical framework for aligning localized resource allocation (squads) with global company strategy. An Objective is a qualitative vector; a Key Result is a scalar magnitude determining if you moved along that vector.
The Mechanics
A mathematically sound KR must be observable, continuous, and bound to a specific timeframe. It cannot be binary (e.g., "Ship feature X"). It must measure the delta in user behavior caused by shipping feature X.
| Bad KR (Binary Output) | Good KR (Continuous Outcome) |
|---|---|
| Launch the new reporting dashboard by Q2. | Increase percentage of users exporting data weekly from 12% to 25%. |
| Implement SSO login. | Reduce password-related support tickets by 40%. |
Common Mistakes
- Treating OKRs as task lists: KRs measure value, not effort. If you accomplish all tasks but the KR doesn't move, the tasks were wrong.
- Setting sandbagged goals: KRs should be set at a 70% confidence interval. Hitting 100% consistently means the organization is operating defensively.
FAQ
How many OKRs should a squad have?
Exactly one Objective and 2-4 Key Results. Any more indicates a failure to prioritize at the strategic level, effectively delegating strategic conflict to the execution layer.