Radical Focus by Christina Wodtke: Achieving Your Most Important Goals with OKRs – A Complete Summary

Quick Orientation

“Radical Focus (2nd Edition)” by Christina Wodtke offers a comprehensive guide to implementing Objectives and Key Results (OKRs) to achieve significant goals. Wodtke, a seasoned Silicon Valley expert, combines a fictional narrative with a practical framework to illustrate how OKRs can transform a struggling company by instilling focus, alignment, and a culture of accountability and learning. The book is relevant for startups, large enterprises, teams, and individuals seeking a robust system for setting and relentlessly pursuing their most important objectives.

This summary aims to capture every core theme, argument, example, and actionable tip from “Radical Focus,” presented in plain language and a structured format for easy understanding and application. It covers the foundational principles of OKRs, practical implementation advice, real-world examples, and strategies for overcoming common challenges, ensuring you have a complete understanding of how to use radical focus to achieve breakthrough results.

Foreword to the Second Edition (by Marty Cagan)

Marty Cagan emphasizes that while the OKR technique is valuable, its success is deeply intertwined with a culture of empowerment within product teams. He highlights the common pitfall of “OKR Theatre,” where companies try to apply the OKR mechanics without fostering the necessary cultural shift.

The Indispensable Link Between OKRs and Culture

The foreword explains that OKRs emerged from companies already possessing a culture of empowerment. Attempting to superimpose OKRs onto a command-and-control environment often fails to yield the desired benefits.

• Core Issue: Many teams struggle to get value from OKRs because they focus on the technique without addressing the underlying cultural need for empowerment.
• Empowerment Defined: OKRs are designed to empower teams by giving them problems to solve (Objectives) and focusing their work on outcomes (Key Results).
• The “OKR Theatre” Trap: Applying OKRs in a top-down culture often results in a superficial adoption known as “OKR Theatre,” where the motions are followed without genuine impact.
• Culture as Prerequisite: Cagan likens applying OKRs without an empowered culture to buying high-performance skis before learning to ski; the tool is useless without the foundational skill and environment.
• Effort Required: True success with OKRs requires the hard work of embracing a culture of empowerment, not just the easier task of applying a technique.
• Book’s Value: Wodtke’s book is lauded for addressing both the culture of empowerment (through its fictional case study) and the OKR technique itself.

This section sets the stage by warning readers that OKRs are not a magic bullet and require a committed effort to change organizational culture for them to be truly effective.

Introduction to the Second Edition (by Christina Wodtke)

Christina Wodtke reflects on the evolution of OKR adoption since the first edition, noting both their widespread use and the common struggles organizations face. She emphasizes that OKRs are more than just goal setting; they provide a framework for actually achieving those goals, particularly for efforts beyond “business as usual”.

Why a Second Edition and the Core of OKRs

Wodtke explains the necessity of this updated edition to address misconceptions and reinforce the core principles that make OKRs effective, fearing they might otherwise become another discarded management fad.

• Evolution of OKRs: Initially focused on start-ups, OKRs have been adopted by organizations of all sizes, from one-person consultancies to large corporations like Pepsico and Walmart.
• Core Principles: The fundamental strength of OKRs lies in a focused, inspiring, and measurable goal that is tracked regularly.
• Misinterpretations and Dilution: The popularity of OKRs has led to misapplications, such as software rebranding project management as OKRs and consultants watering down the framework.
• Key to Effectiveness: Wodtke stresses that the elements making OKRs work (like focusing on outcomes over outputs and embracing difficult aspects) are often the first to be compromised.
• Beyond Goal Setting: Unlike methods like KPIs or SMART goals, OKRs come with a framework for achievement.
• Book’s Updated Content: The second edition expands significantly on practical advice for various organizational contexts while keeping the fictional case study largely intact.
• Urgency of Correct Application: Wodtke expresses a concern that OKRs could be dismissed as a fad if their core principles are not properly understood and applied.
• Call to Action: The introduction encourages readers to start working on their goals today, emphasizing that life is too short for procrastination.

This introduction reinforces that OKRs are a powerful tool when understood and implemented correctly, adaptable to diverse environments but reliant on maintaining their core, results-oriented, and focused nature.

Foreword to the First Edition (by Marty Cagan)

Marty Cagan shares his early career experience at Hewlett-Packard with “Management by Objectives” (MBO), highlighting two foundational principles that are still central to high-performing teams and the OKR system.

Principles of Performance and Motivation

Cagan outlines the core ideas behind MBOs that evolved into OKRs: empowering individuals by defining what needs to be done, not how, and measuring progress by results, not just output.

• Empowerment through Objectives: Referencing General George Patton, Cagan emphasizes telling people what needs to be achieved and allowing them to devise the methods, fostering motivation and their best work.
• Measuring by Results: HP’s tagline, “When Performance Is Measured by Results,” underscores that success is about solving underlying business problems, not merely releasing features.
• Evolution to OKRs: The MBO system was refined over time, notably at Intel, leading to the contemporary OKR system.
• Common Pitfall: Many organizations still operate by dictating roadmaps of features (the “how”) rather than empowering teams with problems to solve, leading to “feature factories”.
• Output vs. Outcome: A persistent issue is measuring progress by output (features delivered) instead of outcome (business problems solved).
• Universality of OKRs: Cagan asserts that these techniques are successful in organizations of all sizes, helping to unleash the potential of smart employees.

This foreword champions OKRs as a means to shift organizations from a feature-focused, command-and-control model to one that empowers teams and measures success by tangible outcomes.

Introduction to the First Edition (by Christina Wodtke)

Christina Wodtke begins by challenging the notion that an “idea” is the most valuable part of a new venture, drawing a parallel with Neil Gaiman’s experience with aspiring writers. She argues that execution—transforming an idea into reality—is the far more difficult and crucial endeavor.

From Idea to Reality: The Need for a System

Wodtke emphasizes that the true challenge lies not in conceiving ideas, but in the hard work of execution, especially when coordinating a team. This necessitates a system to maintain focus and drive progress.

• Ideas vs. Execution: Ideas are relatively easy to generate; the real difficulty is in finding the right form for an idea and making it valuable and accessible to consumers.
• Teamwork Amplifies Difficulty: Execution becomes even harder when a team is involved, requiring hiring, focusing efforts, and maintaining shared purpose.
• Protecting Time, Not Ideas: It’s not the idea that needs protection, but the time required to make it real.
• The Three-Part System: Wodtke introduces her system for achieving goals:
  1. Set inspiring and measurable goals (using OKRs).
  3. Ensure continuous progress toward the desired end state, despite other demands.
  5. Establish a cadence for remembering goals and mutual accountability.

Understanding OKRs and Their Components

The introduction provides a foundational explanation of Objectives and Key Results (OKRs) and how they function to unite and motivate a company.

• OKR Definition: “O” stands for Objective (what you want to do, e.g., launch a killer game), and “KR” for Key Results (how you know if you’ve achieved it, e.g., 25K downloads/day).
• Objective Characteristics: The Objective should be inspiring and qualitative, motivating even those not driven by numbers. A good Objective makes you eager to work on it.
• Key Result Characteristics: Key Results are quantitative and keep the Objective grounded and measurable. Good Key Results should be ambitious enough to be slightly scary.
• Timing: OKRs are typically set annually and/or quarterly.

Tying Actions to Goals and The Importance of Cadence

Wodtke explains how to translate long-term OKRs into weekly actions and the importance of regular rituals to maintain focus and accountability.

• Important/Urgent Matrix: We often get sidetracked by urgent but unimportant tasks. OKRs help by making important, non-urgent goals urgent through time-constraints (quarterly focus).
• Weekly Priorities: Each Monday, setting a few key tasks to complete against the OKR helps maintain progress.
• Accountability: Having someone (a friend, coach, or team) hold you responsible increases the likelihood of completion.
• Learning from Tracking: Reviewing weekly priorities reveals what enables or hinders progress, helping individuals and managers understand capabilities and address roadblocks.
• Commit/Celebrate Cadence: Starting each week with a public commitment to priorities and ending with a Friday celebration of accomplishments creates a habit of execution and high performance.

Beware of Distractions: The Atalanta Analogy

The introduction uses the myth of Atalanta to illustrate how distractions (golden apples) can derail even the most capable individuals or startups from their primary goals.

• Startup Enemy: A startup’s main enemy is time, and the enemy of timely execution is distraction.
• Examples of Distractions: These can range from tempting conference appearances to catering to a single large customer’s specific demands, or dealing with a problematic employee.
• The Solution: Setting good goals (OKRs) and committing to them weekly, while celebrating victories, allows a company to maintain focused growth despite distractions.

The introduction concludes by setting up the narrative part of the book, “The Executioner’s Tale,” as a fable about a startup learning this crucial system for turning dreams into reality.

The Executioner’s Tale

This section is a fictional narrative illustrating the struggles of a startup, TeaBee, and how its founders, Hanna and Jack, learn to implement OKRs to save their company. The story unfolds over several months, highlighting common entrepreneurial challenges.

Six Months Ago … The Genesis of TeaBee

Hanna and Jack, two Stanford graduates, co-found TeaBee with a vision to bring artisanal loose-leaf tea to fine restaurants and discerning cafés. Hanna, with a business background, becomes CEO, while Jack, a design student, takes on the role of president, focusing on the product.

• Initial Vision: Connect great tea producers with high-end establishments that often neglect tea quality.
• Early Operations: They raise some initial funding, set up an office, hire engineers, and build a website for tea producers and buyers. Hanna closes a few deals, and Jack focuses on branding.
• Emerging Problem: After six months, they face an imbalance: many tea producers sign up, but few buyers, leading to a lopsided and unprofitable market.
• Founders Selling: To understand buyer psychology better, Hanna and Jack decide to engage in direct sales themselves.

Hanna Finds Another Great Customer & Jack’s Resistance

Hanna secures a large order from a restaurant supplier, which sells tea and other goods to various restaurants. Jack is initially pleased by the revenue but concerned it deviates from their plan of targeting fine dining establishments directly.

• Shift in Customer Base: Hanna argues that restaurants are hesitant to work with a new company like TeaBee, while suppliers are more willing and can place their tea in many restaurants.
• TeaBee’s Mission Questioned: Hanna believes selling through suppliers still aligns with their mission of “Bringing great tea to people who love it”.
• Packaging Preoccupation: Jack, meanwhile, is engrossed in discussing packaging design with their new graphic designer, Anya, demonstrating his focus on aesthetics.
• Contractual Issue: A new large supplier contract stipulates not using TeaBee’s website due to its perceived difficulty, requiring Hanna to manually input orders.
• Jack’s Discontent: Jack expresses displeasure with selling to suppliers, whom he believes don’t care about tea quality and might compromise TeaBee’s values. Hanna counters that it’s about product-market fit and mutual benefit.

Hanna Suggests a Pivot

Weeks later, recognizing that sales to restaurant suppliers are far more efficient and substantial than direct sales to restaurants, Hanna proposes a pivot: focusing TeaBee’s efforts exclusively on restaurant suppliers.

• Evidence for Pivot: Supplier sales are larger and cycles are manageable, whereas restaurants are slow to commit. This aligns with the startup principle of changing tactics without changing overall strategy.
• Jack’s Concerns: Jack worries suppliers might pressure them to lower quality or harm tea producers. He is also concerned about brand presence if suppliers control packaging.
• Hanna’s Reassurance: Hanna argues they should solve current problems, not imagined ones, and that a mutually beneficial relationship will protect their interests.
• Seeking External Advice: Unable to fully resolve their disagreement, they decide to consult Jim Frost, their first angel investor, for an objective perspective.

Jim Is Holding Court at Starbucks & The Revolving Door Test

Hanna and Jack meet Jim at Starbucks. Jim, a Valley veteran, shares the “revolving door test” story from Intel: when facing a tough decision, Andy Grove and Gordon Moore asked what a new, unburdened CEO would do. This clarity helped Intel pivot out of the memory business successfully.

• Jim’s Insight on Founders: Jim observes other struggling entrepreneurs, noting some run out of money, while others run out of heart, which is more fatal.
• Applying the Test: Jim asks Hanna and Jack what a new CEO would do at TeaBee. Jack admits a new CEO would seriously consider focusing on suppliers due to the money but reiterates his fear of quality compromise.
• Shared Principles: Hanna affirms she also wouldn’t build a company selling a poor product, aiming to change the world, not replicate mediocrity.
• Jack’s Reluctant Agreement: Jack concedes that if he were a new CEO, he would commit to the pivot towards suppliers, recognizing they’ve found product-market fit.
• Jim Introduces OKRs: Jim recommends using Objectives and Key Results (OKRs) to maintain focus and team output during the transition, explaining the concept of a bold, qualitative Objective and three quantitative Key Results.

Defining Early OKRs

Hanna, Jack, and Jim begin to formulate TeaBee’s first OKRs. Hanna suggests an Objective: “Prove our value to the restaurant suppliers”. They debate Key Results, with Jack suggesting “no bargaining” as a sign of value, which Hanna dismisses as unrealistic.

• Stretch Goals: Jim clarifies that KRs need to be hard goals with about a 50/50 chance of achievement to push the team.
• Initial KRs Discussed: They discuss revenue targets and a retention metric (reorders), settling on 70% reorders after Jim pushes back on 30% being too low.
• Website Improvement as a KR: Jack wants suppliers to use the website for orders, leading to the idea of OKRs around fixing the site for supplier needs.
• Shared Understanding: Despite the initial difficulty, Hanna and Jack leave the meeting with tangible goals they can both support.

Hanna Announces the Pivot & Initial Team Reaction

Hanna and Jack announce the pivot to focus solely on restaurant suppliers to their team, explaining the rationale and introducing the OKR process.

• Team Concerns: Erik, the lead programmer, is particularly upset, feeling the company is abandoning its mission to help farmers and small businesses by dealing with “corporate” suppliers.
• Founders’ Justification: Jack and Hanna explain that this new model still benefits tea growers by providing larger, more predictable orders and that TeaBee will protect their interests.
• Presenting First OKRs: Hanna writes the company’s OKRs on the board:
  • Objective: Establish clear value to restaurant suppliers as a quality tea provider.
    • KR: Reorders at 70% (later adjusted to 60% after team discussion).
    • KR: 50% of reorders self-serve.
    • KR: Revenue of $250K.
• Additional OKRs Introduced: Hanna adds more objectives related to building a valuable platform for suppliers, an effective sales team, and a responsive customer service approach, each with their own KRs.
• Lingering Issue: When asked about existing restaurant customers, Jack impulsively says they can keep them, a point Hanna internally flags but doesn’t immediately contest to avoid more conflict.

Distractions and Misalignment: Tastings and Website Neglect

Despite the new OKRs, Jack continues to schedule tea tastings at coworking spaces, believing they build brand recognition and generate sales, even if these customers are not restaurant suppliers. Hanna struggles with manual data entry for large supplier orders because Jack hasn’t prioritized fixing the website to accommodate their needs.

• Hanna’s Frustration: Hanna argues the tastings are a waste of time and don’t contribute to their agreed-upon OKRs focused on suppliers. She is also overwhelmed by data entry.
• Jack’s Justification: Jack sees tastings as networking and brand building, securing a small order with a coworking space manager. He dismisses Hanna’s concerns about an upcoming sales call, missing her point about focus.
• Erik’s Influence: Erik, the lead programmer, reinforces Jack’s resistance to the pivot, expressing disdain for suppliers and suggesting they are ripping off farmers. He also uses the delay in receiving the bulk order spec from Jack as an excuse for not working on it. This further pulls Jack away from critical product work.

Mounting Tensions and Financial Pressure

Hanna confronts Jack about extending the graphic designer’s contract when the company is financially strained and not hitting its numbers. She reveals they are six weeks into the quarter and their numbers aren’t improving, jeopardizing future fundraising.

• Jack’s Disregard for Numbers: Jack admits he’s “not really a numbers kind of guy” and focuses on small, non-strategic wins.
• Hanna’s Explosion: Hanna loses her temper, exasperated by Jack’s refusal to grasp basic economics and its impact on their company. She shares a painful family story about her grandparents’ restaurant failing due to not cutting costs in time, underscoring her fear of making the same mistake.
• Jack’s Lack of Commitment: Jack vaguely promises to look at the dashboards, but Hanna doubts his sincerity.
• Erik’s Sabotage Revealed: Jack overhears Erik telling another programmer, Sheryl, that he’s deliberately obfuscating code for job security and to make things difficult for any new CTO, expressing contempt for Hanna’s “MBA bull” and presumed intention to “flip” the company.

Crisis Point: Losing a Key Customer and Investor Pressure

TeaBee loses Jefferson, a major supplier, due to too many wrong orders—a direct consequence of the unresolved website issues and Hanna’s manual data entry burden. This means losing the primary customer for Tenzo Farms’ matcha tea.

• Hanna’s Despair: Hanna tells Jack to deliver the bad news to Tenzo Farms, highlighting his responsibility as “Mr. President”.
• Jim’s Ultimatum: Hanna seeks advice from Jim, who tells her bluntly that she needs to ensure Jack steps into his role or remove him. He warns that if their numbers don’t improve, he’ll consider bringing in a seasoned executive to replace them.
• Hanna’s Isolation: Feeling the weight of Erik’s sabotage and Jack’s continued inaction (he hasn’t called Tenzo), Hanna feels utterly alone.
• Jack’s Awakening: Forced to make the difficult call to Atushi at Tenzo Farms, Jack finally grasps the real-world consequences of their internal failures. He realizes his job is not just about product design but about the entire business ecosystem, including the numbers and the people.

End of Quarter Failure and a New Introduction

Despite a brief improvement in Jack’s engagement after the Tenzo call, the quarter ends disastrously. They review their OKRs and find they’ve made zero progress on any of them.

• Missed Targets: The sales team wasn’t built out, self-serve reorders are at 15% (due to the bulk order system launching only a week prior and limited rollout), the satisfaction survey results are “uneven,” and revenue targets were missed, partly due to losing Jefferson.
• Misplaced Efforts: Jack points to new branding and website improvements for old restaurant customers as accomplishments, but Hanna correctly identifies these were not their agreed-upon OKRs.
• Blaming the System: Jack suggests the OKR system itself failed, an idea Hanna sharply refutes.
• Jim’s Intervention: Jim calls and asks them to meet him and a potential CTO candidate, Raphael, at Starbucks.

Raphael’s Diagnosis and a New Approach to OKRs

Raphael, an experienced tech lead from successful startups and a game company (SOS), immediately identifies flaws in TeaBee’s OKR implementation upon hearing they met none of their five objectives.

• Too Many OKRs: Raphael states, “If you say three things, you say nothing,” quoting Carville. Five objectives are too many for a team to remember and focus on.
• Missing Weekly Check-ins: He emphasizes that goals can’t just be set and forgotten; they require weekly execution and team check-ins, similar to Agile stand-ups.
• The Four-Square Framework: Raphael introduces a four-square napkin diagram for weekly check-ins:
  1. Upper Right (OKRs & Confidence): List the single company Objective and its 3 Key Results, with a 5/10 initial confidence rating for each KR (indicating stretch goals). Confidence is updated weekly.
  3. Lower Right (Health Metrics): List 2-3 critical metrics to protect (e.g., customer satisfaction, team health, code health) while pursuing ambitious OKRs.
  5. Upper Left (Priorities): List 3-5 top P1/P2 tasks for the week that directly impact the OKRs.
  7. Lower Left (Heads Up): Pipeline of important things expected in the next month to keep teams aligned.
• Focus on One Objective: Raphael advocates for one primary company OKR set to ensure focus.
• Raphael as Interim CTO: Hanna and Jack agree to bring Raphael on as interim CTO.

The Executive Team Forms and Takes Action

Raphael, Hanna, and Jack meet as a new executive team. Raphael insists that Hanna and Jack, not him, must fire Erik for insubordination and sabotage, and they must do it immediately.

• Hanna’s Decisive Action: Hanna accepts her CEO responsibility and fires Erik. She also warns Jack that his performance must improve.
• Jack’s Realization and New Role: Jack decides to step down as president and focus on being Head of Product, committing to understanding the whole business. Raphael reassures him that everyone is “making it up” and that OKRs help maintain focus despite uncertainty.
• Rebooting OKRs with the Team: Hanna leads a team meeting, acknowledging past OKR failures and introducing the new, focused approach with only one company OKR, team-level OKRs tied to it, 5/10 confidence levels for KRs, and mandatory weekly check-ins using the four-square model.
• Team Involvement in Setting OKRs: Crucially, Hanna states that the team will now set their Objectives and Key Results together, fostering ownership: “We value the things we make together”.
• Health Metrics Chosen: The team decides on “happiness of the restaurant suppliers” and “team health” (initially yellow due to Erik’s departure but improving) as their health metrics.

One Month Later: Progress and Friday Wins

A month into the new system, Raphael institutes “Demo Day” on Fridays, where engineers demo their work, and other teams share their “wins”. This replaces the old pattern of the week ending with a whimper.

• Visible Progress: Engineering demos supplier support interface progress; Sheryl shows a database rework for an API. Jack and Anya share new designs for supplier information pages.
• Sales and Hiring Wins: Frank (sales) announces closing Tasteco, a significant new client. Hanna shares she hired a part-time customer service lead.
• Jack’s Focused Decision: Jack reveals he ended Anya’s (designer) contract early because her work, while good, was not a P1 and wasn’t directly helping the current OKRs.
• Improved Team Morale: The weekly rhythm of Monday commitments and Friday celebrations (wins sessions) significantly boosts team morale, hope, and motivation, making everyone want to share a win.

Happily Ever After? Continuous Improvement

A quarter later, TeaBee accomplishes all its Key Results. Raphael cautions against “sandbagging” (setting goals too low). Jack embraces this, urging the team to set “proper brutal goals” for the next quarter.

• Sustainable Growth: Six months later, while they only hit two company KRs, they are critical ones. The suppliers are reordering via the site, and TeaBee has its first new business lead through it. Raphael has expanded their sourcing to Argentina for Yerba Mate.
• Challenges and Adaptation: Sheryl (engineer) resigns due to boredom now that the initial hard problems are solved, but the engineering team continues to grow and thrive under Raphael’s leadership and the OKR cadence.
• One Year Later: Success and Stability: Hanna closes the Series A funding round. The team works cohesively, disagreements are easier, and the numbers consistently go up. The weekly goal-sharing and support system is ingrained. Hanna plans to share the funding news at the Friday wins session.

The Executioner’s Tale effectively demonstrates the journey from chaos and misalignment to focused execution and success through the iterative application and refinement of the OKR framework, emphasizing cultural change alongside procedural adoption.

The FRAMEWORK

This section transitions from the narrative to the instructional core of the book, explaining why achieving important goals is difficult and outlining the fundamental principles of the OKR system as a solution.

Why We Can’t Get Things Done

Wodtke identifies five primary reasons why individuals and companies often fail to achieve their most important goals, even when their significance is acknowledged.

• Lack of Prioritization: Having too many competing goals means nothing is truly important. Running a company involves significant daily operational work, and adding numerous goals ensures little beyond necessities gets done.
  • Solution: Setting a single Objective with only three Key Results provides necessary focus.
• Failure to Communicate the Goal: Goals must be reiterated constantly and woven into all aspects of company life, from meetings to project evaluations.
  • Solution: The OKR cadence of Monday commitments, status updates, and Friday celebrations ensures the goal remains top-of-mind.
• No Plan for Achievement: Willpower alone is insufficient for achieving goals, as it’s a finite resource. A process is needed to maintain progress even when motivation wanes.
  • Solution: The OKR system (setting, commitment, celebrations, check-ins) provides this process.
• Not Making Time for What Matters: Urgent tasks, whether important or not, tend to take precedence due to time pressure. Important but non-urgent goals get perpetually deferred.
  • Solution: Committing weekly to work towards the Objective creates accountability and ensures time is dedicated to it.
• Giving Up Instead of Iterating: Initial failure is common when implementing OKRs or pursuing hard goals. Companies might sandbag (set easy goals) or consistently overpromise and underdeliver. Often, they fail to track efforts towards OKRs consistently.
  • Solution: Successful companies iterate, learning from failures and adjusting their approach. Close tracking and learning are key.

A Path to Success

Achieving goals is described as “merely hard,” like losing weight through diet and exercise; it requires discipline and practice.

• Prioritize Ruthlessly: Choose the most important goal instead of trying to do everything at once.
• Clarify the Goal: Define what the goal looks like, when it’s accomplished, and exactly what is desired.
• Communicate Clearly: State the conceptual goal repeatedly until everyone understands and pursues it.
• Plan for Progress: Create a plan that sustains momentum even during difficult times.
• Dedicate Time: Actively allocate time to accomplish the goal rather than hoping for a future “tomorrow”.
• Embrace Iteration: Be prepared for failure, learn from it, and try again.

This section lays the groundwork for the detailed explanation of OKR fundamentals and practices, emphasizing that the system provides a structured way to overcome common obstacles to achieving ambitious goals.

Part One: The Fundamentals of Objectives and Key Results

This part delves into the core concepts of OKRs, explaining their significance, how to craft them effectively, and the prerequisites for their successful adoption.

Why Objectives and Key Results Matter

Wodtke recounts her experience at Zynga, a rapidly growing company that effectively used OKRs to focus its disparate studios on common goals, empower them, and fuel growth through learning.

• Origin of OKRs: The framework evolved from Intel’s implementation of Peter Drucker’s Management by Objective (MBO) system, championed by Andy Grove, and later evangelized by John Doerr to companies like Google and Zynga.
• Benefits for Startups: Wodtke found that startups often suffer from a lack of focus, which OKRs can address by aligning everyone towards a validated vision, crucial when racing against funding depletion.
• Personal Application: OKRs are effective for personal goals as well; Wodtke used them to achieve her own career transformation after leaving Zynga.

What are OKRs?

This subsection provides a concise definition and the basic structure of Objectives and Key Results.

• Definition: OKRs stand for Objectives and Key Results, used to focus a group or individual around a bold goal.
• Structure: The Objective is qualitative, setting a goal for a specific period (usually a quarter). Key Results (typically three) are quantitative and indicate if the Objective has been met.
• Goal Achieving Method: OKRs are not just for setting goals but for achieving them; however, adopting them can be challenging as it requires changing habits and learning about company strengths and weaknesses.
• Terminology: An “OKR set” refers to an Objective with its Key Results. “OKRs” refers to the overall methodology, including setting, weekly progress checks, and end-of-period grading.

How to Write a Good Objective

An Objective should be a single sentence with specific characteristics to effectively motivate and guide a team.

• Qualitative and Inspirational: The Objective must excite people and provide a sense of meaning and progress, using language that resonates with the team. Examples include “Own the direct-to-business coffee retail market in the South Bay” or “Transform Palo Alto’s coupon using habits”.
• Time Bound: Objectives are typically set for a quarter, especially for startups. Larger companies might have annual and quarterly OKRs. It takes practice to size Objectives appropriately for the timeframe.
• Actionable by the Team Independently: The team setting the Objective must be able to achieve it without depending on other teams, avoiding excuses like “Marketing didn’t market it”. Some support teams might use the company’s OKR to prioritize their work instead of having their own.
• Mission for a Shorter Period: An Objective is like a company’s mission statement but for a shorter duration (e.g., three months versus five years). Poor objectives often resemble Key Results (e.g., “Sales numbers up 30%”).

Key Results

Key Results quantify the inspirational language of the Objective and are derived by asking, “How would we know if we met our Objective?”. They define what terms like “awesome” or “kill it” mean in measurable terms.

• Quantity and Basis: Typically three KRs are set, but it can range from one to five. They can be based on measurable aspects like growth, engagement, revenue, performance, or loyalty.
• Balancing Forces: Wisely selected KRs can balance competing forces, such as growth versus performance, or revenue versus quality.
• Example KRs for “Launch an awesome MVP”:
  • 40% of users come back twice in one week.
  • Recommendation score of 8.
  • 15% email newsletter open rate.
• Handling Baselines: If a baseline for a desired metric doesn’t exist, make an educated guess; understanding will improve by the end of the quarter.

Basics of Setting Key Results

This section details the process and considerations for developing effective Key Results.

• Quantifying Objective Language: Identify words in the Objective that can be quantified. For “Our customers love us so much they are our sales team,” “love” could become Net Promoter Score (NPS), and “sales” could become referrals.
• Outcome vs. Output Thinking: OKRs help shift teams from thinking about outputs (tasks completed) to outcomes (results achieved).
• Freelisting Technique: Brainstorm potential KRs by writing many ideas on sticky notes, one per note, to allow for easy manipulation and diverse idea generation.
• Stack Ranking and Pairing Indicators: After freelisting, stack rank the metrics by their effectiveness as progress indicators. Use Andy Grove’s concept of “pairing indicators” to measure both effect and counter-effect, ensuring a balanced approach (e.g., measuring customer service calls alongside revenue to ensure quality isn’t sacrificed for sales).
• Considerations for KRs:
  • Baseline Availability: You might need to measure something for a period before setting a confident KR.
  • Ease of Measurement: Consider if the team will realistically track the metric.
  • Signal Strength: Determine how confident you’ll be in success if the number is met.

Can Project Completion Be a KR?

Wodtke strongly advises against making project completion a Key Result because it locks the team into a specific tactic, even if that tactic proves ineffective.

• Focus on Outcomes, Not Tasks: If KRs are tasks (e.g., “New self-service help area,” “Love-driven marketing with TV commercials”), all can be completed without achieving the desired business outcome (e.g., revenue flat, acquisition down).
• Institutionalized Self-Delusion: Checking off to-do lists instead of monitoring outcome metrics leads to a false sense of progress.

Ask Questions about Tasks to Find the Real Metric that Matters

When teams (especially frontline ones like engineering, design, and product management) propose tasks as KRs, coaching is needed to shift them towards outcome-based thinking.

• Coaching Questions: To uncover the true metric, ask:
  • Why this project? Why is it important?
  • What will it accomplish? What numbers will move if it works?
  • How does that tie into the company’s Objective?
• Example Transformation: A task-based OKR like “O: New self-serve help area; KR: Better search, New FAQ, Forums” can be transformed through questioning into an outcome-based OKR: “O: The company helps our customers succeed when they are struggling; KR: ‘Did this help’ rating rises 15%, ‘Problem resolved’ rating on FAQ improves 30%, Peer-to-peer help forum has DAU of 2K”.
• Flexibility and Empowerment: Outcome-based KRs allow teams to change tactics if initial approaches don’t move the numbers, fostering true empowerment.

KRs Should Be Difficult, Not Impossible

OKRs are inherently stretch goals, designed to push teams beyond their comfort zones but not into despair.

• Confidence Level: Aim for a 5/10 confidence level (a 50/50 shot) of achieving a KR. This signifies an appropriately challenging stretch goal.
• Avoiding Punishment for Failure: A culture that punishes failure will lead to employees setting easy goals (sandbagging) and not attempting ambitious feats.
• The “Yoga” Analogy: Stretch until you feel it, but not so far as to cause pain or injury (burnout).
• Gut Check: Good KRs elicit a feeling that the team will need to bring their “A game”. If they feel “doomed,” the KRs are too hard; if they feel “I can do that with some hard work,” they are too easy.
• Committed vs. Aspirational OKRs: Wodtke advises against distinguishing between “committed” (knowable) and “aspirational” (hopeful) OKRs, as it adds complexity and can dilute the focus on stretch goals.

The Metrics First Approach to Setting OKRs

Sometimes, a team member, particularly from business, product, or sales, might propose a Key Result (a number) first. This is a valid starting point.

• Uncovering the Objective: When a KR is proposed first (e.g., “revenue grow to $500K/month”), ask what that number signifies or what story it tells (e.g., “ready to raise a Series B,” or “visitors are converting at a high rate”). This story becomes the Objective.
• Triangulating Success: Once the Objective is clear, identify other relevant KRs to provide a balanced view of success. For an Objective like “ready to raise the next round,” other KRs might focus on retention, conversion, or engagement to ensure sustainable growth rather than short-term squeezes.

Prerequisites for OKR Success

Wodtke outlines crucial conditions and cultural elements that must be in place for OKRs to be effective, warning that OKRs are not a silver bullet.

• Not for Control: OKRs will not work if the intention is to better control employee activities; they are based on granting freedom to achieve outcomes.
• Requires Healthy Culture: In a toxic culture, OKRs will be perceived as just another tool for pressure. They also require a willingness to focus, not pursue a dozen different things simultaneously.
• Foundation: OKRs thrive when a company has a strong mission, hires great people, and trusts them.

Prerequisite 1: Check Your Mission

A clear company mission is fundamental before implementing OKRs. Startups often resist creating missions, but Wodtke argues most implicitly have one.

• Mission’s Role: A mission guides decision-making and explains why the company exists (beyond just making money, which is statistically unlikely for most startups). Examples: Google’s “To organize the world’s information…” or Philz Coffee’s “better people’s day”.
• Mission Formula: A starting point for a mission: “We [reduce pain/improve life] in [market] by [value proposition]”.
• Mission vs. Objective: A mission has a longer timescale (e.g., 5 years) than an Objective (quarter/year) but shares aspirational and memorable qualities.
• OKRs without Mission: Using OKRs without a mission is “like using jet fuel without a jet”—messy, undirected, and potentially destructive. A mission makes selecting quarterly Objectives straightforward.

Prerequisite 2: You Need a Strategy

OKRs can only be effectively set if there is an underlying strategy; strategy is about knowing what not to do.

• Strategic vs. Reactive Activities: Organizations balance planned efforts to gain market traction (strategic) with responses to external events (reactive). Constant reaction mode is easy to fall into but undermines long-term resilience.
• Strategic Decisions Drive OKRs: When a company reaches a growth decision point (e.g., new geography vs. new product for existing market), the chosen direction informs the OKRs. For example, an annual Objective might be “Bring our world-class product to the world,” with a quarterly Objective of “bring our world-class product to Georgia”.
• Iterative Strategy: The strategy doesn’t have to be perfect initially; OKRs allow for learning and adjustment each quarter. For pre-market fit startups, the OKR is always “get to product-market fit”.

Prerequisite 3: Practice Metrics Thinking

Effective OKR implementation requires the ability to measure critical metrics and understand how to influence them.

• Beyond Basic Metrics: Many companies only track superficial metrics like traffic and clicks without deeply understanding what these numbers truly indicate. For instance, a wedding site might have high daily active users (DAU) but only for a short period.
• Characteristics of a Good Metric (from Lean Analytics):
  • Comparative: Allows comparison over time, to user groups, or competitors (e.g., “Increased conversion from last week” is better than “2% conversion”).
  • Understandable: Must be memorable and discussable to drive cultural change.
  • Ratio or Rate: Ratios help understand fundamental health at a glance.
  • Changes Behavior: The most crucial criterion—it prompts different actions based on its changes.
• Instrumentation: If a company isn’t good at metrics thinking or product instrumentation (adding trackers), it should spend a quarter establishing baselines before trying OKRs.

Prerequisite 4: Make a Safe Place for Learning (Psychological Safety)

Effective teams, and thus effective OKR implementation, require psychological safety, where members feel safe to speak up, make mistakes, and learn socially.

• Personal Connections: Leaders should create opportunities for team members to connect on a human level, fostering better team dynamics (e.g., sharing something awesome seen during the week, or “introduce each other” exercises).
• Empathy and Feedback: A leader models an atmosphere of mutual empathy where caring feedback can be given and received constructively.
• Creating a Team Charter: A formal agreement on how to work together, built by the team itself, can establish clear expectations and reduce conflict. This process involves discussing best/worst team experiences and defining rules of engagement (communication, note-taking, conflict resolution).
• Individual Needs vs. Team Culture: A team charter helps individuals understand the team’s working style in advance, allowing them to adapt or choose to leave if there’s a mismatch, rather than feeling resentful.
• Impact on OKRs: Psychological safety makes OKR meetings more honest and effective, accelerating results.

Why a Project Completion Can’t Be a KR (Revisited with Pipelines)

This section reinforces the idea that KRs must be outcomes, not outputs, and introduces the concept of “Pipelines” as being more suitable for OKRs than traditional “Roadmaps”.

• Roadmaps vs. Pipelines: Roadmaps are defined as plans for a desired future with dates, while Pipelines are collections of project ideas that might lead to the desired future, prioritized by impact/effort/confidence. Pipelines offer flexibility.
• Generating Options: For any given KR, brainstorm at least five potential projects that could move that KR.
• Pipeline Evaluation Table: Use a table to assess projects based on the OKR/Health Metric affected, Impact, Effort, and Confidence/Evidence. This allows leaders to make informed go/no-go decisions or request more research/testing.
• Flexibility is Key: OKRs aim to provide flexibility in how goals are achieved; Pipelines support this, whereas rigid Roadmaps (like a “bug in amber”) hinder it.

What About Everything Else We Have to Do? (Health Metrics)

OKRs are part of a management approach, not the entirety of it. Many operational tasks (“business as usual”) are essential for staying in business but don’t necessarily drive radical improvement and thus don’t always need OKRs.

• Health Metrics Defined: These are key indicators tracked to ensure critical aspects of the business remain stable while the team pursues ambitious OKRs. They act as a “canary in the coal mine”.
• Purpose of Health Metrics: They protect existing accomplishments and alert the team if the pursuit of OKRs is causing burnout, neglecting customers, or degrading systems.
• Examples of Health Metrics: New customer sign-ups, customer satisfaction, code health, team health.
• Promoting to OKR: Occasionally, a declining Health Metric (e.g., customer satisfaction) might be promoted to an OKR for a quarter to actively improve it. Once restored, it can return to being a Health Metric.

What Makes OKRs Work? The Cadence.

The regular rhythm of setting, checking, and celebrating OKRs is more crucial than perfecting the Objective or KRs themselves. This cadence distinguishes OKRs from other goal-setting methods and turns goal setting into goal achieving.

• Modified Cadence for Startups: Wodtke adapted Zynga’s intensive tracking to a simpler two-meeting-per-week cadence for startups: Monday for intentions, Friday for celebrating progress.
• Repetition is Key: The cadence ensures goals are constantly reiterated, keeping them top-of-mind (Jeff Weiner: “When you are tired of saying it, they are starting to hear it”).

Monday Commitments and the Four Square

Each Monday, the team meets to check progress against OKRs and commit to tasks for the week, using a four-square format as a conversation tool.

• Quadrant 1 (Upper Left – Intentions for the week): List the 3-4 most important things to be done this week towards the Objective. Discuss if these priorities will advance the KRs.
• Quadrant 2 (Lower Left – Forecast for the month): What upcoming items should the team be aware of to help or prepare for?
• Quadrant 3 (Upper Right – Status toward OKRs): Update confidence levels (e.g., from an initial 5/10). Discuss reasons for changes.
• Quadrant 4 (Lower Right – Health Metrics): Review 2-5 key Health Metrics (e.g., customer relationships, code stability, team well-being), mark them (e.g., red/yellow/green), and discuss any issues.
• Focus on Conversation: The document is a tool for discussion about priorities, confidence changes, preparedness, and team/system health. Aim for more discussion than presentation. Meetings can end early if all is on track.
• Efficient Review: Use color-coding and skim-able sentences; focus on problems, complications, or areas needing help. Don’t read everything aloud.
• Leader’s Role: Model a helpful tone, e.g., “It looks like our second Key Result is in trouble. Can we brainstorm some ways to get it back on track?”.

Balancing Health Metrics and OKRs

Health Metrics are marked simply (green/yellow/red). A “Code Red” can be called by anyone at any time if a Health Metric is critical.

• Code Red Protocol: Calling a Code Red halts work on OKRs to fix the critical Health Metric and creates a record of the problem for later review during end-of-quarter retrospectives.
• Learning from Crises: Even in years dominated by crises (like 2020), tracking these events helps companies learn and reinvest in strategies to become more crisis-proof.

Fridays Are for Winners

Aiming high means frequent “failures” or near-misses. The Friday wins session is critical for morale, recognizing progress, and fostering a positive team environment.

• Sharing Progress: Teams demo work-in-progress (code, designs). Sales shares closes, customer service shares rescues, etc..
• Benefits:
  1. Fosters a sense of being part of a winning team.
  3. Motivates individuals to seek wins to share.
  5. Increases cross-disciplinary understanding and appreciation.
• CEO’s Role in Small Teams: The CEO should provide refreshments (pizza, beer) as a token of appreciation, even if the budget is tight.
• Logistics: Hold sessions at a reasonable time (e.g., 3 or 4 p.m.), not late when people want to go home. Attendance should not be mandatory.
• Remote Teams: Adapt with video conferencing, bragging channels on chat tools (Slack), or CEO/GM video summaries. It’s less satisfying than in-person but still shows appreciation and makes progress visible.
• Keeping it Fresh: Vary the format occasionally (e.g., different groups present, science-fair style demos) to prevent staleness. Use short, anonymous surveys (“exit tickets”) for feedback on the sessions themselves.

Keep the Cadence and Make It Your Own

The specific “how” of the commitment and celebration rituals is flexible and can be adapted to company culture, time zones, or existing meeting schedules (e.g., Friday/Tuesday instead of Monday/Friday), as long as the core principles of setting intentions and celebrating progress are maintained.

• Core Principle: Commit to the team, to each other, and to the shared future, renewing these vows weekly.

Improve Weekly Status Emails with OKRs

Traditional status emails are often unreadable lists of activities. Wodtke learned at Zynga that status reports, when formatted well with important information, can be valuable communication tools, aiding efficiency and learning. She proposes a simple, effective format.

• 1. Lead with OKRs and Confidence: List the team’s OKRs and confidence level (1-10 scale) for hitting each KR this quarter. Use color-coding (red <3, green >7) for scannability. This reminds everyone of goals and tracks progress.
• 2. Last Week’s Priorities and Achievements: List prioritized tasks from last week and whether they were achieved. Briefly explain any misses to foster organizational learning about obstacles.
• 3. Next Week’s Priorities: List only about three P1s (meaty accomplishments encompassing multiple steps, e.g., “Finalize spec for project Xeno”) and a couple of P2s. Avoid trivial tasks (“Talk to legal”).
• 4. Risks or Blockers: Note anything needing help that can’t be solved internally, or potential obstacles (e.g., a partner hard to schedule, tricky technology). Avoid blaming; bosses dislike surprises.
• 5. Notes: Include brief, timely, useful information that doesn’t fit elsewhere (e.g., “Hired new team member,” “Reminder: team offsite Friday”). Avoid excuses or therapy.
• Coordination Benefits: This format allows managers and their reports to send out their status emails simultaneously (e.g., on Friday), knowing priorities are aligned, rather than waiting for collation. It reinforces commitment and focus, helping avoid “checkbox thinking”.

On Radical Focus

The book is titled “Radical Focus” because focus is the critical differentiator between excelling and mediocrity. OKRs are a framework for creating and ensuring this focus on what truly matters.

• One Company Objective: The key is to commit to one company Objective, not four or ten. This singular focus is essential for achieving great things.
• OKRs for Vision Sharing, Not Control: OKRs are not for controlling employee time but for sharing the vision so employees can make informed judgment calls about priorities.
• The Problem with Multiple OKR Sets: Complexity increases exponentially. If the company has 5 OKR sets (5 Os, 15 KRs = 20 data points), and each product team has 3 (12 more points), plus department and individual OKRs, employees can’t remember or act on such a large group of priorities.
• Memorability is Key: For OKRs to drive decisions, everyone must know and remember them. One company Objective helps immensely.
• Exception for Large, Diverse Companies: Very large corporations with multiple, distinct business models (e.g., Alphabet with self-driving cars and search ads) might need one OKR set per business model per quarter. Otherwise, focus is paramount for growth.

Practical Advice for Maintaining Radical Focus

Wodtke offers four pieces of advice based on common pitfalls.

• 1. Don’t Jam Years of Work into a Single Quarter: Trying to change everything at once leads to fractional effort and minimal progress (the “too little peanut butter over too much toast” analogy from a Yahoo! memo). Prioritize and sequence efforts for maximum impact: do less, better.
• 2. Don’t Make a Company OKR Set for Every Department: Company OKRs should unite the entire company toward a single goal, not be a collection of departmental OKRs (e.g., separate marketing, engineering, product OKRs as “company OKRs”). Find the unifying theme (e.g., getting ready for B-round funding) that allows all teams, including support functions, to contribute. An example of a poor structure includes multiple, unrelated company-level OKRs where some are only relevant to specific departments.
• 3. Not Everyone Will Lead; Some Will Support: In situations like a major product launch, some departments (e.g., legal) play a crucial supporting role for a short period, while others (e.g., engineering) are intensely involved throughout. The company OKR guides their prioritization when needed, but they don’t necessarily need their own departmental OKRs focused on strategic change all the time. Supporting roles are vital and deserve respect and inclusion in celebrations.
• 4. Don’t Let Politics Distract from Clear, Concise OKR Sets: Avoid execs tacking personal projects onto company OKRs or creating multiple OKR sets due to an inability to agree on wording or prioritize metrics. The “rule” of three KRs is a guideline; it’s better to have one Objective with five KRs if they are all crucial and remembered than multiple Objectives. Don’t let indecisiveness or conflict avoidance lead to confusing marching orders. Simplifying OKRs, even if it takes extra effort, is better than losing employee focus with unnecessary complexity (Larry Tesler’s Law of Conservation of Complexity applied to OKRs). Be clear, simple, memorable to achieve Objectives.

This first part establishes the “what” and “why” of OKRs, setting a strong foundation in their core principles, the importance of focus, a learning culture, and the essential cadence that brings them to life.

OKR Coaching Example (by Ben Lamorte)

Ben Lamorte, principal at OKRs.com, provides a real-world coaching excerpt to demonstrate how guiding leaders to create their own OKRs, rather than dictating them, improves their quality and effectiveness. The example focuses on an Engineering VP whose initial objective is to help the sales team achieve their targets.

From Vague Goal to Measurable Contribution

The coach guides the Engineering VP through a series of questions to transform a general desire into specific, measurable Key Results that truly reflect engineering’s impact on sales.

• Initial Ambiguity: The VP’s objective “help our sales team achieve their targets” is vague. The coach asks how success would be known at quarter’s end.
• Identifying Actual Contribution: When asked for a specific customer example where engineering contributed to a sale, the VP clarifies that engineering’s role is more about keeping a prospect “in the mix” rather than directly closing deals.
• First Draft KRs (Task-Oriented): The VP proposes: “Provide sales support for five major prospects in Q2” and “Develop training for sales team by end of Q2”. These are directional but not truly measurable outcomes.
• Refining “Major Prospect”: The coach probes the definition of “major prospect,” leading the VP to quantify it as “prospect with $100K+ year-one revenue potential” and to align this definition with the VP of Sales.
• Focusing on Intended Outcome: The coach asks about the outcome of engineering sales support. The VP states it either continues the sales process or kills the deal.
• Boundary Condition Question: What if all five support calls kill deals? The VP concedes this isn’t success, especially if deals are lost for technical reasons. This leads to a revised KR: “Provide sales support with no more than three $100K+ prospects deciding not to evaluate our product for technical reasons”.
• Positive Framing and New Metric: The coach reframes the negatively worded KR into a positive one: “Obtain a baseline on ‘technical pass rate’” (e.g., if 8 of 10 prospects advance without technical objection, the pass rate is 80%).
• Collaborative Outcome: The Engineering VP agrees to confirm the usefulness of “technical pass rate” with the VP of Sales, ensuring cross-departmental alignment on how engineering’s contribution is measured.

This coaching example effectively shows the Socratic method in action, guiding the individual to discover outcome-oriented, measurable, and aligned Key Results, which is far more effective than simply being told what their OKRs should be.

Part Two: Objectives and Key Results in Practice

This part of the book focuses on the practical application of OKRs, covering initial implementation strategies, specific use cases for product teams, scaling OKRs, managing them within a product portfolio, and alternative OKR approaches for different situations.

Implementing OKRs for the First Time

Successfully introducing OKRs requires careful planning to avoid common pitfalls, as initial failure can lead to team disillusionment. Wodtke suggests three approaches to reduce this risk.

• Pilot Team Approach: Have one healthy, high-performing, independent team adopt OKRs first. Once they refine their approach and succeed (after a cycle or two), their success can be trumpeted, making other teams eager to adopt OKRs. This is the most successful approach.
• Single Company OKR: Start with only one OKR for the entire company. This demonstrates executive commitment and simplifies initial implementation, allowing observation of which groups align naturally and which need coaching. Good for smaller companies needing focus.
• Project-Based OKRs: Apply OKRs to individual projects first to train people on the Objective-Result mindset (“What is the Objective for this project?” and “How will we know if we’ve succeeded?”). This works well for companies new to being data-driven.
• Avoid Full Company Rollout Initially: Do not try to implement OKRs across the entire company at once. Many companies fail by trying to jump into the deep end, leading to slowed productivity and frustration (e.g., company, team, and individual OKRs all at once creates chaos).
• Common Early Struggles:
  • Support Team Alignment: Finance, HR, customer support often focus on “keeping the lights on” and struggle to align with strategic OKRs. Initially, let them focus on Health Metrics.
  • OKR Software Mismatch: Don’t invest in software until OKRs are running smoothly with simpler tools. Find software that supports your established process.
  • Identifying Good KRs: Companies must learn what metrics matter before using OKRs to grow them. Becoming data-informed is a prerequisite, not a result of early OKR use.
  • Process Bloat: OKR-related activities (setting, negotiating, closing) can overshadow actual work if the process becomes too cumbersome. Keep it simple. Format.com simplified from company/team/individual OKRs to high-level goal spreadsheets with aligned team spreadsheets.
• Perfection is the Enemy of Good: Don’t aim for perfect OKRs initially. Start small, learn, and iterate. Culture change is a marathon, not a sprint achieved by buying software.

OKRs for Products (by Angus Edwardson)

Angus Edwardson, product director at GatherContent, shares how his company uses OKRs specifically for product team projects, making it a requirement for initiating new features.

• Integrating OKRs into Product Lifecycle: GatherContent uses Kanban for agile development. When an MVP is pulled from the pipeline into development, its Kanban card must include a clear Objective (phrased as a “Hypothesis”) and Key Results.
  • Hypothesis Approach: Using “Hypothesis” instead of “Objective” encourages an experimental mindset: “We think this will happen,” which is then proved or disproved.
• Benefits of Product OKRs:
  • Clarity Upfront: Forces the team to answer “What are we trying to achieve?” and “How do we measure success/failure?” before building.
  • Prioritizing Work: Allows prioritization of roadmap items based on expected impact and alignment with business goals (e.g., if the business Objective is to increase activation, features impacting that are prioritized).
  • Facilitating Collaboration: Structured discussions around feature rationale (hypothesis) and potential value (KRs) make conversations with stakeholders more efficient and less emotional, fostering constructive collaboration.
  • Measurement and Learning: Tracking KRs of released MVPs in a spreadsheet and reviewing them regularly helps evaluate results and derive learnings. Setting deadlines for OKR measurement ensures timely data gathering and discussion of inconsistencies or unexpected outcomes.
• Overall Impact: Adding OKRs to Kanban cards at GatherContent has led to better prioritization, faster learning, more effective communication, and a developed habit of articulating the “why” behind their work.

How to Hold a Meeting to Set OKRs for the Quarter

Setting quarterly OKRs is a critical process involving introspection and difficult choices about the company’s direction. A structured meeting is essential.

• Preparation:
  • Small Group: Keep the meeting to ten or fewer people, run by the CEO, including the senior executive team. No phones/computers to encourage focus and speed.
  • Employee Input: Solicit Objective suggestions from all employees a few days prior (with a short 24-hour window), reminding them of the mission, strategy, and any annual OKR. Have someone collate the best/most popular ones.
  • Exec Preparation: Each exec should bring one or two Objective ideas.
• Meeting Process (Goal: 4.5 hours max, ideally shorter):
  • Objective Setting:
    • Write employee-generated and exec Objectives on large sticky notes.
    • Place stickies on a wall, combine duplicates, look for patterns, and combine similar Objectives.
    • Stack rank them, then narrow down to three.
    • Discuss, debate, fight, re-stack rank, and finally, pick one company Objective.
  • Key Result Setting:
    • Exec team members freelist as many metrics as possible to measure the chosen Objective (on stickies, 10 mins).
    • Affinity map the metrics: group similar stickies (e.g., DAU, MAU, WAU together).
    • Stack rank and pick three types of metrics. Initially write KRs as “X [metric]” (e.g., “X revenue”) to separate discussion of what to measure from how much.
    • A good rule of thumb is to have a usage, a revenue, and a satisfaction metric for balance, though this varies by Objective.
    • Set the actual values for the KRs, ensuring they are “shoot for the moon” goals (50% confidence). Challenge sandbagging, over-optimism, or playing it safe. Debate this now, not mid-quarter.
• Final Review (5 mins): Discuss the final OKR set. Is the Objective aspirational? Do KRs make sense and are they hard? Can the team live with this for a quarter? Tweak as needed, then commit. A worksheet is available at eleganthack.com/an-okr-worksheet.

The Timing of OKRs

Once a company is ready to roll out OKRs fully after successful pilots, a specific rhythm should be followed for implementation each quarter.

• 1. All Employee Input (Quarter Start – short window): All employees submit their ideas for the company’s next quarterly Objective (24-hour window). This fosters buy-in and provides cultural insights.
• 2. Exec Team Sets Company OKR (Half-day session): Execs discuss proposed Objectives, choose one, and then set the KRs. This can be a 90-minute meeting once proficient, but initially may take longer. Delays or indecision are HR issues to be addressed.
• 3. Departmental OKR Development (Exec homework): Executives introduce the company OKR to their direct reports, who then develop their team OKRs (can be a 2-hour meeting per team using similar freelisting/ranking process).
• 4. CEO Approval (Approx. 1 day + follow-up): CEO reviews departmental OKRs. This should be a focused effort.
• 5. Sub-Team OKR Development: Department heads share company and department OKRs with any sub-teams, who then develop their own.
• 6. All Hands Meeting: CEO discusses the “why” behind the quarterly company OKR, highlights exemplary departmental OKRs, reviews last quarter’s OKRs, and points out key wins, maintaining a positive and determined tone.
• Overall Timeline: This entire process should take less than two weeks. Setting company goals is critical and should be prioritized.

Two Weeks Before the Quarter Ends

If the weekly commitment and celebration cadence is followed, teams should be able to assess OKR achievement (or misses) about two weeks before the quarter officially ends.

• No Last-Minute Miracles: Don’t expect to hit truly hard goals in the final two weeks if progress isn’t already evident.
• Honest Assessment: Admit missed KRs or those set too low. Celebrate partial achievements (e.g., 80% progress) and learnings.
• Continuous Improvement: OKRs are about learning cycles, not just checking boxes. If KRs are missed, analyze why and fix the approach. If all are hit, set harder goals next time. Focus on learning, getting smarter, and celebrating progress.

OKRs for Product Teams (by Marty Cagan)

Marty Cagan discusses the application of OKRs specifically within technology product organizations, emphasizing the role of cross-functional product teams (squads).

• Product Team Structure: A product team typically includes a product manager, product designer, and engineers, sometimes with specialists like data scientists or user researchers. Each team is responsible for a significant part of the product or technology.
• OKRs for Alignment and Coordination: In larger organizations with many product teams, OKRs communicate and track team-specific problems, ensure alignment with company objectives, help teams understand their contribution to the whole, coordinate work, and avoid duplication.
• Common Pitfall: Functional Silo OKRs: A frequent mistake is having each functional department (design, engineering, QA) create its own OKRs, which then cascade to their members within cross-functional product teams. This creates conflict, as the product team has business-related Objectives (e.g., reduce customer acquisition cost), while individuals also have functional Objectives (e.g., engineers on re-platforming, designers on responsive design).
• Solution: Focus OKRs at the Product Team Level: OKRs should primarily be set for the cross-functional product team, focusing individuals on their product team’s Objectives.
• Incorporating Functional Goals: Larger functional objectives (like responsive design or managing technical debt) should be discussed at the leadership level alongside business Objectives and then incorporated into relevant product teams’ OKRs.
• Functional Managers’ OKRs: It’s acceptable for managers of functional areas (who are not typically on product teams) to have individual Objectives related to their organizational strategy (e.g., head of UX developing a responsive design strategy).
• Individual Contributor Growth OKRs: Personal growth OKRs for individual contributors are also acceptable if they don’t interfere with their primary responsibility to their product team’s Objectives.
• Cascading Direction: In a product organization, OKRs should cascade up from the cross-functional product teams to the company or business unit level, ensuring alignment rather than conflicting functional directives.

Cascading OKRs at Scale

Wodtke revisits the idea of cascading OKRs, acknowledging that while it works for small startups, it doesn’t scale well for large companies. A rigid cascade can become a slow, micromanaged waterfall.

• OKRs are Not for Command and Control: They are for directing people toward desired outcomes and trusting them to figure out how. They only work for empowered teams.
• Scaling Solution: Trust Your Teams: For large organizations (after successful pilots and cultural adaptation), trust teams to set their own OKRs based on company strategy and trust them to achieve them.

Enter the Cone of Uncertainty & Half-Built Strategy

To manage long-term planning without over-committing in an unpredictable future, Wodtke introduces the “Cone of Uncertainty” and “Half-Built Strategy”.

• Cone of Uncertainty: Predictions become less accurate further into the future. However, long-term goals are needed for strategic planning.
• Half-Built Strategy Approach:
  • Set a complete OKR set (Objective and KRs) for the immediate next quarter (Q1).
  • For the following three quarters (Q2, Q3, Q4), set draft Objectives only, without KRs.
  • This is because setting KRs is time-consuming, and future needs are hard to predict precisely. It avoids the “Ikea Effect” (overvaluing something you spent a lot of time on), allowing plans to evolve as new data comes in each quarter.
  • This “deliberate building in of strategy absence” promotes flexibility and innovation, preventing organizations from becoming too rigid.
• Example: TinkWorks (Startup raising B-round):
  • Annual Objective: Be ready to raise B-round of investment.
  • Quarterly Theming: CEO themes each quarter: Q1 retention, Q2 conversion, Q3 acquisition, Q4 pitch/roadshow prep. This provides a loose roadmap.
  • Q1 OKR Set: CEO and exec team fully define Q1 Objective and KRs.
  • Q2-Q4 KRs: KRs for subsequent quarters are set just-in-time, after the previous quarter’s retrospective, incorporating learnings.
• Example: TeaBee’s Annual and Quarterly Objectives:
  • Mission: Connect best tea growers with customers who love quirky tea.
  • Annual Objective: America looks forward to discovering new tea after a fine meal, thanks to TeaBee. KRs: Revenue $20M in 5+ geolocations, brand awareness up 10%, 500+ requests for home use teas.
  • Q1 OKR: The west coast loves TeaBee (KRs: $1M revenue in LA/Portland/Seattle, 5 restaurants with “TeaBee served here” stickers, 1 early adopter with year-long delivery booking).
  • Q2-Q4 Draft Objectives: Q2: New York loves TeaBee; Q3: Austin loves TeaBee; Q4: D.C. loves TeaBee. This provides flexibility while signaling the location-based expansion strategy.
• Team OKR Setting: Self-sufficient teams (e.g., product teams with dedicated resources) then set their own OKRs aligned with the company direction. These can be reviewed by managers or peers for feedback and alignment, fostering autonomy.

Have a Short and Iterative Review Process

Once company OKRs are set, the rest of the organization should publish their OKRs within 48 hours. “The best is the enemy of the good” – avoid analysis paralysis.

• Peer Review (24 hours): Allow a short period for anyone to critique anyone else’s OKRs. This collaborative process helps everyone improve and fosters shared ownership.
• Embracing Duplication (Initially): Drawing from Ken Norton’s experience at Google, Wodtke suggests that some duplication of effort in innovation is acceptable initially, as it’s hard to know which approach will succeed. Effectiveness trumps efficiency in innovation.
• OKR Setting Schedule:
  1. Grade OKRs two weeks before quarter end.
  3. Determine next quarter’s Objective approach (move to next, change, or redo).
  5. Execs set Annual OKRs (typically at an offsite).
  7. Execs set Company (Quarterly) OKRs two weeks before EOQ (initially 3×2-hr meetings, eventually 2-hr).
  9. Publish company OKRs one week before EOQ. Teams/departments set their OKRs.
  11. Publish team/department OKRs.
  13. Short review period.
  15. Short revision period.
  17. Hit the ground running on day one of the new quarter.
• Bravery Required: This agile scaling requires hiring well, setting clear outcome-based goals, giving up control of tactics, and trusting teams.

OKRs and the Product Portfolio

In larger companies, it’s important to identify which groups need OKRs. Wodtke uses a modified Boston Consulting Group (BCG) matrix, the “4Es Product Portfolio,” to guide this.

• Question Mark (Exploratory Market): High growth market, few/no current products. Use Exploratory and Hypothesis OKRs.
• Star (Expand Market): Successful products in a growing market. Use traditional OKRs to maximize potential.
• Cash Cow (Exploit Market): Saturated market, still profitable but no growth. Don’t use OKRs if there’s no growth potential; it will be frustrating. Focus on KPIs and efficiency.
• Dog (Exit Market): Fading market, fading product success. Do not use OKRs. Automate as much as possible and defund.
• Dangers of Impossible Goals in Wrong Contexts: Setting impossible OKRs for “Cash Cow” or “Dog” products, especially if tied to compensation, leads to bad results like employee demoralization, cheating, and gaming the system (e.g., Wells Fargo “Going for Gr-Eight” campaign leading to fake accounts; VW emissions scandal). Managers should work with teams to set sensible stretch goals.

Service Departments Will Struggle

Service departments (Engineering, Design, Legal, Customer Service, Marketing, Finance) primarily support product teams.

• Limited Capacity for Own OKRs: They typically have only 5-20% of their time for their own improvement projects.
• When to Set OKRs: Service groups can set OKRs if they have control over resource allocation and enough people to make something happen. They don’t need to wait for product teams to set theirs.
• Time Tracking: If unsure about available capacity, track workload for a quarter before setting service department OKRs.
• Predictable Schedules: Some groups like legal or finance may have more predictable schedules and might not always need OKRs, relying instead on Health Metrics to maintain quality.

Let’s Talk about Individual OKRs

Wodtke’s advice on individual OKRs is blunt: “Just say no”.

• Risks of Individual OKRs: They are too hard to keep from becoming demotivating micromanagement tools that can lead to burnout. People gain value over time through learning and experience, not by being treated as replaceable cogs.
• Alternative for Performance Management: Instead of individual OKRs for performance reviews, Wodtke refers to her book “The Team that Managed Itself” and its simple canvas for hiring, managing, and reviewing individual work.

The Role Canvas for Managing Individuals (Abbreviated from “The Team that Managed Itself”)

This canvas helps define roles, interview, manage, and evaluate individuals without relying on problematic individual OKRs.

• Step 1: Define the Role: A role has four parts:
  • Goals & Responsibilities: What the role does. Responsibilities are steady-state (e.g., budget management for a manager); Goals are short-term achievements aligned with company OKRs (e.g., build out a design team) and must be concrete. One to three goals are best for the canvas. List 3-5 crucial responsibilities.
  • Skills & Market Knowledge: What the role knows. Market knowledge is familiarity with the company’s space (e.g., e-commerce, healthcare). Skills are hard/soft abilities (e.g., Python, collaboration, Photoshop). Freelisting and ranking skills (must-have vs. nice-to-have) is recommended.
  • Canvas Structure: The Role Canvas includes these four attributes plus an area for questions.
  • Diversity and Unexpected Skills: Listing only absolute needs attracts a broader, more diverse candidate pool and leaves room for unexpected valuable skills.
• Step 2: Interview and Hire: Before interviewing, review the canvas and formulate questions based on “How would I know?” if a candidate possesses the needed skills/knowledge or can achieve the goals/responsibilities. Use behavioral questions (“Tell me about a time when…”).
• Step 3: Manage Using the Role Canvas: Review the canvas before weekly one-on-ones. Are they progressing on goals (contributing to OKRs)? Fulfilling responsibilities? Do they have needed skills/knowledge? Pick 1-3 important topics for discussion, reserving 50%+ time for the report’s issues. Consider walking one-on-ones. Document key points afterward.
• Step 4: Evaluate and Give Feedback Using the Role Canvas: Traditional performance reviews can be demotivating. Give feedback quarterly to allow for growth throughout the year.
  • Preparation: Review weekly status reports and one-on-one notes. Look for patterns. Determine what’s important vs. trivial. Example: Interrupting clients is critical to address; music choice disputes can be handled differently.
  • Focus Feedback: Select 1-3 top issues to address formally. Address other issues in one-on-ones or as a team. Praise achievements. If no critique, that’s good. If no praise, consider if the person is adequate.
  • Day of Review: Frame of mind: you are there to help the person be their best, like a coach. Listen more than you talk. Your goal is to help them see problems and co-create solutions. Explicitly state you are there to help, especially initially, to build trust.
  • Reciprocal Feedback: Ask for advice on your feedback style or leadership. Document everything.

OKRs and the Annual Review (by Deidre Paknad)

Deidre Paknad, CEO of Workboard, argues that business goals have often lost their power, becoming tools for compensation rather than drivers of performance, especially in large enterprises. Annual goals written for future compensation reviews tend to be vague with a low achievement bar, becoming disconnected from business reality.

• Restoring Goal Power: Reframe goals from performance assessment devices to tools that inspire and amplify performance. This involves transforming the model, cadence, and presence of goals.
• Five Steps to Restore “Magic Power” of Goals:
  1. Use Goals to Define and Drive Success: Goals should be inspiring, tangible, and a real-time rally point, providing purpose and focus for day-to-day execution. (Only 7% of people truly understand their company’s goals).
  3. Dump Old-School Goal Models for One that Amplifies Results: Techniques like OKRs combine bold aspirations with metrics for awesome outcomes, providing radical clarity and removing the ceiling on achievement, unlike traditional approaches that encourage low ceilings. Disconnect OKRs from performance reviews when maximizing possibilities.
  5. Manage Achievement in Real Time: With short-range goals (like quarterly OKRs), every week matters. Real-time goal transparency allows leaders to help teams stay focused, predict results, and drive accountability, rather than waiting for monthly/quarterly reviews.
  7. Make Goals as Present as Email: Teams should be able to see their goals and progress in seconds. High performers review goals daily to align their time.
  9. Goals Should Flow Top Down and Bottom Up: Pure hierarchies are less effective than teaming and leading across levels. Allow aspirations from all levels to flow, converging on goals rather than rigid top-down cascades to foster innovation and smooth strategy progression.
• Assessing Performance without Direct OKR Link: Use continuous conversations (one-on-ones at least twice a month) to coach and calibrate on engagement, performance, and alignment (using, for example, five levels for each, shared by manager and employee). End-of-year reviews become simpler as facts are shared, there are no surprises, and it’s part of an ongoing series of performance conversations.

Tracking and Evaluating OKRs

Two weeks before quarter-end, it’s time to grade OKRs and plan for the next cycle. Wodtke discusses two common systems: confidence ratings (her preferred approach for startups/smaller teams) and grading.

• Confidence Ratings:
  • Process: When setting KRs, assign a 50% confidence (5/10 rating). In Monday meetings, report changes in confidence levels (this is an art, not a science; gut check is fine). Confidence often swings initially, then settles around two months in. OKRs can usually be “called” (success/failure) two weeks before quarter-end.
  • Advantages: Keeps OKRs top-of-mind due to constant updating; quick and painless, good for habit-forming; prompts key conversations about drops in confidence and needs for help.
  • Grading: Two weeks before EOQ, mark confidence as 10 (achieved) or 0 (missed). Success is often defined as making two of three KRs. This helps focus on achievable goals and abandon impossible ones.
  • Downside: Risk of sandbagging (one impossible, one hard, one easy KR). Manager must watch for this.
• Grading Approach (e.g., Google’s method):
  • Process: At quarter-end, grade KRs with data (e.g., 0.0 for failure, 1.0 for complete success). Most results should be 0.6-0.7.
  • Google’s Sweet Spot: 60-70% achievement. Lower means not achieving enough; higher means aspirational goals aren’t high enough. This tolerance for “failure” can be uncomfortable for new adopters.
  • Defining Scoring Criteria Upfront (Ben Lamorte’s advice): If using standardized scoring, criteria for each grade (e.g., what constitutes a 0.3, 0.7, 1.0 for a KR) MUST be defined when the KR is created. This forces conversations about what’s aspirational vs. realistic.
  • Transparency and Regular Check-ins (Google): Organizational OKRs are shared and graded annually/quarterly in company-wide meetings. OKR owners explain grades. Mid-quarter check-ins are also helpful. Google’s philosophy: hire smart people, give them a goal, leave them alone.
  • Visibility (Ben Lamorte): Progress posters in hallways, updated regularly, can make OKRs transparent and drive accountability.
• OKRs are Not Synonymous with Performance Evaluation (Google ReWork advice): OKRs summarize work and contributions but aren’t a comprehensive individual evaluation tool. Use actual accomplishments for bonuses/raises. Relying on OKR results alone for performance decisions encourages sandbagging and punishes dreamers. Reward what people do.

Score your OKRs; it is worth it. (by Magdalena Pire Schmidt)

Magdalena Pire Schmidt, a management coach, emphasizes the importance of numerically scoring OKRs, even though teams often resist it.

• Scoring Process:
  • Score each Key Result from 0 to 1.
  • The Objective’s score is the average of its Key Results’ scores (assuming equal weighting to avoid complexity).
  • Example Scored OKR: Objective: Get rid of customer service backlogs [0.22]. KR1: Decrease avg response time from 7 to 3 days [0.5] (actual: 5 days). KR2: Maintain weekly CSAT at 85% [0.17] (achieved 2/12 weeks, avg 69%). KR3: Reduce cost per request from $3 to $2.70 [0] (cost increased to $3.10).
• Why Numerical Scoring is Critical:
  • Improves KR Quality: Forces KRs to be measurable and unambiguous. If scoring is hard to explain mid-quarter, the KR was likely not a clear outcome.
  • Forces Reality Check: Numbers highlight reality. Low scores aren’t always bad news (e.g., KR deprioritized, wrong metric tracked, valuable learnings from failed initiatives) but prompt necessary conversations about how to proceed.
  • Mid-Quarter Scoring Recommended: Score numerically mid-quarter for a moment of reckoning, then identify focus/drops for the remaining six weeks. Score again at quarter-end.
• Score Actual Results, Not Confidence or Milestones: Focus on outcomes achieved, not just project completion or confidence levels. This anchors teams on actual results, fostering innovation and experimentation.
  • Scoring Confidence: Assesses if projects are on track (Pros: motivating if results are delayed; Cons: risk of delivering initiatives without results).
  • Scoring Milestones: Updates initiative completion (Pros: shows progress; Cons: risk of becoming project management, not outcome-focused).
  • Scoring Results (Recommended): Updates actual results seen (Pros: clear, transparent, incentivizes metric-driven KRs and early results; Cons: can be demoralizing if effort doesn’t immediately translate to results).
  • Interpretation of score (e.g., 0.5) varies by practice: 50% chance of meeting target (Confidence), 50% work done (Milestones), or 50% of numerical target achieved (Results).
• Overcoming Resistance to Scoring: Teams avoid scoring due to effort and fear of bad news (lack of self-monitoring is a goal saboteur). Management must decouple OKR scores from performance assessments to alleviate fear of repercussions from low scores, especially if teams are used to objective completion driving reviews. Once in habit, teams appreciate the clarity and agency.
• Assessing Scores at Quarter-End: Final scoring is crucial for reflection and incorporating learnings into the next cycle.
  • Score Interpretation Guide: 0.7-1.0 = Achieved/Green; 0.31-0.69 = Partially Achieved/Yellow; 0-0.3 = Not Achieved/Red. This incentivizes ambitious OKRs.
  • Committed vs. Stretch OKRs: For “committed” OKRs (agreed feasible and priority), only 1.0 is achievement. (Wodtke notes her preference against distinguishing types of OKRs if no financial incentives are tied, advocating all OKRs be stretch goals).
  • Consistently High Scores ( >0.7): May indicate sandbagging; teams might need to be pushed to be more ambitious.
• Numbers Guide the Narrative: Scores are a guide, not the final assessment. Subjectivity exists; a 0.1 on an ambitious KR might be more significant than a 1.0 on a superficial one. In the example, the 0.22 Objective score still showed good impact (reduced response time significantly) with clear areas for next focus.
• Holistic Reflection: Consider OKR scores alongside business-as-usual, KPIs, team events, and new challenges/opportunities. At Google, Pire Schmidt kept a quarterly document with Highlights, Groundwork (effort without results yet), and Lowlights (no progress/new challenges), without mentioning OKR scores directly. The conversation should be about impact and future direction.

Beyond the Usual OKR Approach

Wodtke introduces alternative “flavors” of OKRs co-created with clients to address specific challenges like exploring unknown possibilities, validating strategic directions, or managing long development horizons, while keeping them outcome-oriented.

• Exploratory OKRs: For very early-stage startups, R&D/innovation teams, or when you have no idea what you are doing but need to find a path.
  • Personal Example: Wodtke’s own OKR: “O: Be financially stable, preserve health, do work I like. KRs: Earn $30K/3mo doing work I’d do unpaid; Manageable budget; Zero acid reflux/back pain.” She ran experiments (consulting, speaking, teaching) to achieve this state.
  • Business Example (New Tech Seeking Market): Inventor of a tool for drawing in emails. “O: Market can’t live without our tool. KRs: Preorders at X; 3 B2B deals signed; X beta users”. Numbers can be guesses; the OKR acts as a North Star to prevent wandering.
  • Game Development Example: “O: Target market finds our game fun. KRs: Play testers eagerly recommend 3 friends; 80% players complete game in playtests; 30% players buy at pre-release price”. Reminds team of audience/business goals beyond just features.
  • TeaBee Example (Exploring Direct-to-Consumer): Jack wants retail shops; Hanna wants subscriptions. Raphael helps them define a shared goal: “O: Find a way to have a direct relationship with tea drinkers. KRs: Aided brand recognition 7/10; Preorders $5K; Email open rate 12%.” This allows them to experiment with various tactics (pop-up, subscription sign-ups) in a Lean Startup way.
• Hypothesis OKRs: Used after Exploratory OKRs yield a strong hypothesis, to get data to prove product-market fit or the need to pivot before full commitment.
  • Structure: Objective is the value proposition including target market (e.g., “Bookkeepers are delighted by our auto-categorization system”). KRs are how the market would react if true (e.g., sales, conversions from competitors, willingness to recommend, prepayment for vaporware). Avoid “weak indicators” like NPS or email signups; “people don’t lie with their wallets”.
  • Market Sizing and Benchmarking: Use market research (e.g., SOM) to make credible KR guesses. Start benchmarking early to understand impactful metrics and develop market intuition.
  • Example (Brand X Pivoting B2C to B2C): “O: Customers embrace our product. KRs: X units sold (high); X returns (low); X number of 4-5 star reviews on sales site Y”.
  • “Failing” is Learning: Failing to make these OKRs indicates the market isn’t viable or the product promise was overhyped, informing decisions to pivot or kill the product.
  • TeaBee Example (Teahouse Validation): Subscription experiment showed little interest. Teahouse pop-up numbers were surprisingly good. Hypothesis OKR for further validation: “O: Create a compelling independent teashop experience. KRs: Capacity at 100% during rush times; $40k in takeout sales; Yelp review 4.” This tests a short-lease, single store before larger investment.
• Milestone OKRs (MORKS): For big initiatives lasting multiple quarters (common in slow-moving industries like R&D, biotech, finance) to provide outcome-based checkpoints and reduce risk. The Objective is often stable (“Get to shipping this new thing”); KRs are metrics to hit or reconsider the effort.
  • Concept: Inspired by a restaurant owner expanding internationally, needing milestones for location finding, permits, hiring. Instead of “find location” (task), the Milestone OKR became “Be prepared to have a successful pre-opening test run,” with KRs about location quality, hire quality, etc..
  • Focus on “Where We’ll Be,” Not “What We’ll Do”:
    • Traditional Milestone: “Get new CPAP lightweight mask prototype built.”
    • Milestone KR (MORK): “New CPAP lightweight mask prototype produces better sleep for 8 of 10 testers”.
    • Traditional Milestone: “Strategy for 2021 draft finished.”
    • Milestone KR (MORK): “Strategy for 2021 draft approved by C-suite”.
  • TeaBee Example (4Os and KRs for Q1 for Annual Goal):
    • Annual Objective: Wow TeaBee fans with in-store tea consumption experience.
    • Q1 OKR: “O: Research indicates strong market position. KRs: Market size of 20M/annual identified; 3% restaurant customers preorder gift certificates; Margins of servings viable (2%+).” Pipeline includes market research tasks.
    • Q2 Draft Objective: Pilot “Pop-up” is loved.
    • Q3 Draft Objective: Store is set up for a successful opening.
    • Q4 Draft Objective: First store opened.
  • Outcome, Not Output: To define MORKs, ask: “What would happen if we did this Milestone to the best of our ability? What external signs would indicate we’d done well?”.
• OKRs Are Always About Outcomes: Regardless of the stage or approach, OKRs help achieve impact by focusing on desired outcomes and measuring progress, enabling informed decisions to pivot, quit, or double down based on real-world feedback.

Using OKRs to Increase Organizational Learning

The Radical Focus OKR approach is designed for faster organizational learning, drawing on John Dewey’s learning theory: instruction, action, and reflection.

• Instruction: The weakest approach; someone talking at you (talks, lectures, books).
• Action (Learning by Doing): More powerful; creates personal relationship with knowledge and practical skills (projects, essays, supervised practice like surgery/piloting).
• Reflection (Most Important, Least Practiced): To learn from experience, reflect on what happened and what it means (essays, Q&A, discussion in education; hypothesis testing and iteration in Lean Startup).
• OKRs and Reflection:
  • Quarterly OKRs set a goal; weekly priorities/tasks are hypotheses to test.
  • Friday check-ins: reflect on actions, learn, course correct. This focuses practical learning through action, improving hypotheses and goal achievement.
  • End-of-Quarter Reflection: Codify learnings from the past three months, grade efforts. Grading’s value is in the honest conversations (“Why did/didn’t we make this? What did we learn? Where are we sandbagging/growing?”).
• Social Learning on an Organizational Scale:
  • Individuals are on multiple teams (exec, functional, project). Learnings cross-pollinate as people share experiences.
  • Healthy organizations evangelize learnings. Formal cross-team events like lunch-and-learns (sharing successes, insights, tips) can spread knowledge when Friday bragging sessions become too large.
  • Weekly status emails also build cross-team learning: short, public emails are read; bosses can identify useful insights from reports and nudge sharing. Learning becomes a collective company activity.
• OKRs Are Built for Organizational Learning (Example): Jack notices differing sign-up rates between two similar restaurant suppliers. Team discusses, Hanna hypothesizes one serves low-end restaurants wanting tea bags. This insight sparks new company direction (studying loose-leaf vs. tea bag customers, new product lines, tailored marketing). Each observation leads to a hypothesis, validation, sharing (company lore), and application by other teams.
• Learning How to Learn: Teams also learn how to work together more effectively. The OKR cadence fosters insights through awareness, experimentation, conversation, and reflection.
• Adapting to Change in a Changing Market: Speed of learning is a key competitive asset. The OKR cadence builds this learning capability, allowing companies to adapt.
• Focus and Cadence vs. Just Metrics: OKRs without focus and a learning cadence become a mere numbers game, leading to “hacks” to hit targets rather than genuine improvement. Emphasizing learning means being willing to fail publicly and discuss it to grow.

A Note on OKR Software

Many good OKR tools exist, but buying software should be the last step, not the first, akin to buying expensive exercise equipment before committing to exercise.

• Start Lightweight: Adopt OKRs using simple tools first, experiment, and find a system that yields results.
  • Recommended Starting Tools: Whiteboard (Objectives), sticky notes (KRs), PowerPoint (tracking confidence/efforts), Email (statuses), Excel (formal grading if chosen). Google also offers a grading tool on ReWork.
• Shop for Software After Mastery: Only consider buying OKR software after feeling your organization has truly mastered the OKR process for a quarter.

Simple but Hard

OKRs are simple in concept but hard in execution, much like “eat less and exercise”. Success requires focus, saying no often, team check-ins, accountability, and honestly admitting when tactics aren’t working.

• The “Not Yet” Mindset (Carol Dweck): If struggling with OKRs (or any hard endeavor), adopt a growth mindset. Instead of feeling like a failure, see it as “Not Yet.” This implies being on a learning curve with a path to future success.
• Continuous Improvement: It’s okay to not write a perfect Objective or to have a task as a KR initially. Stay with it, experiment, learn, and improve. Tell yourself, “Not Yet. But soon”.

This concludes the core instructional parts of the book, emphasizing that OKRs are a journey of continuous learning and adaptation, requiring discipline and a focus on outcomes.

Credit Where Credit Is Due

Wodtke acknowledges influences and contributors.

• Rick Klau (Google Ventures): His work on Google’s OKR implementation is noted as different but worth exploring. Wodtke’s approach is presented as effective for startups to larger enterprises, but iteration is encouraged.
• “Measure What Matters”: Acknowledges John Doerr’s book and potential contradictions with her tactics, advising readers to revert to Radical Focus if they struggle.
• Cathy Yardley: Thanked for help with fiction writing.
• Beta Readers: A long list of individuals thanked for their advice and insights.
• Call for Feedback: Readers are encouraged to share their learnings to improve future versions.

About the Author

Christina Wodtke is an established Silicon Valley thought leader with experience at LinkedIn, MySpace, Zynga, Yahoo!, and others. She founded startups, Boxes and Arrows (an online design magazine), and co-founded the Information Architecture Institute. She is a Lecturer at Stanford in Computer Science (HCI group) and teaches worldwide on human innovation and high-performing teams.

• Author’s Style: Her work is personable, insightful, knowledgeable, and engaging, often using storytelling.
• Other Books: “Information Architecture: Blueprints for the Web,” “Pencil Me In,” and “The Team That Managed Itself”. “Radical Focus” is a bestseller, tackling OKRs through the fable of Hanna and Jack’s tea startup.
• Contact: cwodtke.com or eleganthack.com for more information.

Big-Picture Wrap-Up

“Radical Focus (2nd Edition)” by Christina Wodtke provides a compelling and practical methodology for achieving ambitious goals using Objectives and Key Results. Through a blend of engaging storytelling and clear instructional frameworks, the book demonstrates that true success with OKRs stems not just from the mechanics of goal setting, but from fostering a culture of empowerment, relentless focus, continuous learning, and honest accountability. Wodtke emphasizes that OKRs are a system for achieving goals, requiring discipline and adaptation, moving teams from mere activity to impactful outcomes.

• Core Lesson: Sustainable achievement hinges on radical focus, and OKRs, when implemented with their supporting cadence and cultural underpinnings, are a powerful tool to instill and maintain that focus.
• Next Action: For organizations new to OKRs, start by identifying the single most important company Objective for the next quarter. Implement the Monday commitment and Friday wins cadence with one pilot team, focusing on learning and adapting the process before wider rollout.
• Reflective Question: What is the one outcome that, if achieved next quarter, would most significantly propel our mission forward, and how will we unambiguously measure our progress and success towards it?
• Key to Success: Remember that OKRs are not a rigid dogma but a flexible framework; the principles of outcome-orientation, regular check-ins, psychological safety, and iterative learning are more important than adhering to a specific template if it doesn’t serve your context.
• Final Thought: The journey with OKRs is one of continuous improvement. Embrace the “simple but hard” nature of the process, learn from both successes and failures, and consistently ask, “What truly matters, and how do we achieve it?”