Primary source
Measure What Matters (book_cube)
A 4-part summary series covering OKR principles, company cases and CFR integration.
Primary source
Measure What Matters (book_cube)
A 4-part summary series covering OKR principles, company cases and CFR integration.
Measure What Matters
Authors: John Doerr
Publisher: Portfolio; МИФ (русское издание)
Length: —
John Doerr's practical framework for execution: prioritization, transparency, tracking and continuous performance conversations.
Original
TranslationManagement / Leadership / Processes / Strategy
Measure What Matters is best read as an operating rhythm handbook, not a static template. The lasting value comes from combining goals, metrics, feedback and culture in one execution system.
1. Book map
Part 1. OKR in action
Google, Intel, Remind, Nuna, MyFitnessPal, Intuit, the Gates Foundation, Chrome and YouTube: the book explains OKR through practical operating stories.
Part 2. New ways of working
OKR is paired with CFR (conversations, feedback, recognition), including examples of moving away from annual reviews toward continuous performance dialogue.
Core focus
The main value is not only in writing goals, but in turning prioritization, transparency and execution rhythm into a coherent management system.
Why this matters for engineering leaders
Useful as an implementation playbook: cascading priorities, monitoring progress, and running retrospectives that actually change the next cycle.
2. Four OKR superpowers
1. Prioritization and commitment
OKRs answer what matters now. A small number of objectives creates focus, while key results make outcomes testable.
2. Alignment and transparency
Top-down direction plus bottom-up contribution keeps cross-functional expectations visible and coordinated.
3. Tracking and adaptation
Goal setting alone is not enough. Weekly check-ins and mid-cycle corrections are required for real execution.
4. Stretch for exceptional outcomes
Google-style split between committed and aspirational OKRs balances reliability and long-horizon bets.
3. Case highlights
Early OKR adoption created a shared language for priorities and execution at scale.
Intel / Operation Crush
Tight alignment and focused execution can win a market battle even when the technical starting point is imperfect.
Remind
At an early growth stage, OKRs helped the team protect focus amid rapidly expanding scope.
Nuna
Relaunch worked after leaders adopted OKRs first, then cascaded the practice through management and teams.
MyFitnessPal
After acquisition, OKRs helped negotiate demand vs. capacity and avoid cross-org execution chaos.
Intuit
Transparent goals improved business-IT coordination and made trade-offs easier to discuss.
Bill & Melinda Gates Foundation
OKRs helped leadership enter complex operating context quickly despite limited day-to-day immersion.
Google Chrome / YouTube
Long-horizon stretch goals forced strategic bets (for example V8 and watch-time as a North Star metric).
Adobe / Lumeris
Without performance-process and culture changes, OKR adoption stalls. CFR helps close that gap.
4. Monitoring and scoring
- For aspirational OKRs, ~0.7 can still indicate a healthy stretch, not failure.
- Typical status bands: green > 0.7, yellow 0.4-0.6, red < 0.4.
- Committed OKRs are stricter: materially below 1.0 is generally treated as under-delivery.
- Numbers need context: what enabled progress, what blocked it, and what changes next cycle.
5. CFR as a companion system
Conversations
Frequent, structured manager-employee dialogue about goals, blockers and priorities.
Feedback
Two-way and timely feedback on behaviors and outcomes instead of once-a-year summaries.
Recognition
Visible acknowledgment of meaningful contributions, including small improvements that compound.
Caveat in practice
Several stories are inspirational but not implementation-complete. Without explicit ownership, routine review and management discipline, OKRs quickly degrade into a reporting artifact.
6. Common anti-patterns
Running 8-10 objectives per cycle and losing strategic focus.
Writing key results as task lists instead of measurable outcomes.
Mixing committed and aspirational OKRs without explicit rules.
Using OKR as top-down control only, without bottom-up corrections.
Keeping annual review cadence while claiming continuous OKR management.
Tying compensation mechanically to KR percentages and encouraging metric theater.
7. Working patterns for leads
Limit scope to 1-3 objectives per team level and 2-5 key results per objective.
Write KRs as verifiable outcomes (adoption, reliability, delivery, revenue), not activities.
Run weekly check-ins with monthly reprioritization where context changes.
Separate committed and aspirational goals to preserve both reliability and innovation.
End each cycle with a short retro: what worked, what failed systemically, what changes next.
Operate OKR and CFR together so goals, feedback and recognition reinforce each other.
8. Quarter-one rollout sketch
- Step 1 (weeks 1-2): define 1-2 company/domain objectives and explain committed vs aspirational rules.
- Step 2 (weeks 2-3): cascade goals to teams, gather bottom-up KRs, resolve dependency conflicts.
- Step 3 (weeks 4-5): start weekly check-ins with explicit KR owners and transparent status.
- Step 4 (mid-cycle): adjust scope if market, architecture, or staffing context shifts.
- Step 5 (cycle end): run KR + CFR retrospective and refine rules for the next quarter.