The ultimate guide to OKRs | Christina Wodtke (Stanford)

Mar 16, 2023 Episode Page ↗
Overview

Christina Woodke, author and Stanford lecturer, discusses how to leverage OKRs to drive focus, alignment, and a learning cycle within companies. She shares tactical advice on implementing, troubleshooting, and optimizing OKR processes, emphasizing simplicity, psychological safety, and the importance of storytelling and business acumen for product leaders.

At a Glance
39 Insights
1h 13m Duration
18 Topics
7 Concepts

Deep Dive Analysis

Christina Wodtke's Background and Approach to OKRs

The Core Purpose and Benefits of OKRs

The Atomic Unit of an OKR

Integrating Mission, Vision, Strategy, and OKRs

Crafting Effective Objectives and Key Results

Measuring Customer Satisfaction and Delight

Common Mistakes in OKR Implementation

Diagnosing and Fixing Broken OKR Processes

Strategic Rollout of OKRs with High-Performing Teams

The Power of Storytelling and Visual Communication

Developing Better Storytelling Skills

The Cadence and Rituals of a Healthy OKR Process

Streamlining the OKR Approval Process

Prioritizing Learning Over Precise Grading in OKRs

The Value of Setting Ambitious Goals

Advice for Starting with OKRs

The Importance of Business Acumen for Product Managers

Career Advice for Aspiring Product Managers

OKRs as a Vitamin, Not Medicine

OKRs supercharge strong, well-aligned companies with psychological safety and clear strategy, but they will only reveal existing problems in struggling companies, not fix them.

Atomic Unit of OKR

The fundamental essence of an OKR process is the ability to answer the question, 'What am I doing this week to get closer to our strategic goals?'

Strategy as a Hypothesis

A company's strategy should be viewed as a strongly held hypothesis about how to win in the market and fulfill its vision, guiding decisions on product type, service model, and market approach.

Half-Built Strategy

A strategic approach where only the current quarter's OKRs have defined Key Results, while future quarters only have objectives, allowing flexibility to react to new information and learning.

Retrieval Practice

A learning theory concept applied to OKRs, where regularly recalling and discussing OKRs helps embed them in long-term memory, enabling faster, more informed decision-making.

Product Trio

A framework (by Teresa Torres) emphasizing the balance of business, user experience, and technology, where the product manager's primary role is to serve the business aspect.

Product Sense

Not an innate talent, but rather intuition developed from 'compressed experience,' meaning it's a learned skill that comes from accumulating and reflecting on a wide range of past experiences.

?
What are the primary benefits of implementing OKRs in a company?

OKRs provide focus, align teams, create a consistent cadence for progress, and establish a valuable learning cycle by regularly reviewing what worked and what didn't.

?
How should a company approach defining its mission and strategy in relation to OKRs?

A mission can be a 5-year goal, not necessarily forever, and strategy should be a clear hypothesis for winning in the market. This strategy then informs quarterly objectives, with Key Results defined only for the current quarter to maintain flexibility.

?
What are common pitfalls to avoid when writing Objectives and Key Results?

Objectives should be motivating and inspiring, not too vague or merely a task. Key Results must be actual outcomes, not just a list of tasks, and should triangulate different aspects of success (e.g., numbers, quality, financial impact).

?
What are the signs that a company's OKR process is failing or 'busted'?

A key sign is if OKR review meetings are boring, indicating that the focus is on low-level tasks rather than strategic outcomes, or if leaders are too involved in individual contributor tasks.

?
How can a company effectively roll out OKRs for the first time?

Start by piloting OKRs with your best, multidisciplinary team, as they are capable of adapting the framework to your company's culture and identifying what works, rather than trying to fix a struggling team with OKRs.

?
Why is storytelling an important skill for product leaders?

Storytelling taps into a fundamental human way of processing information, leading to better attention, comprehension, and retention of messages, especially when conveying facts within a narrative.

?
What is the recommended cadence for a healthy OKR process?

A healthy cadence involves committing to weekly actions on Mondays, celebrating achievements on Fridays, and using short weekly status updates (e.g., confidence level, last week's accomplishments, next week's plans) to track progress and identify blockers.

?
How should companies approach the approval process for OKRs to ensure efficiency?

Instead of hierarchical approval, teams can write their OKRs and have three relevant teams (e.g., from tech, strategy, sales) review them within a 24-hour turnaround, providing feedback without formal top-down approval.

?
When reviewing OKRs, what should be prioritized over precise numerical grading?

The focus should be on the learning derived from the outcome, specifically through retrospectives that explore why a certain grade was achieved, rather than getting bogged down in creating overly precise or artificial measurement systems.

?
Why is it beneficial to set ambitious goals, even if they might not be fully achieved?

Ambitious goals (e.g., aiming for 70-80% success) push individuals and teams to discover their full capabilities and are highly motivating, provided they don't feel completely unattainable or doomed from the start.

?
What is a contrarian perspective on product management education and career entry?

Product management education often overemphasizes UX, but PMs primarily serve the business and need strong business acumen (models, markets, trends). Aspiring PMs should ideally start in engineering or design roles to gain foundational experience before moving into product.

1. Pilot OKRs with Best Team

To successfully roll out OKRs, start by piloting the process with your best multidisciplinary team. They are capable of figuring out how to make it work within your culture and can provide a template for wider adoption, rather than trying to fix a struggling team with OKRs.

2. Establish Weekly OKR Cadence

Implement a weekly rhythm where teams commit to actions on Monday to advance their OKRs and celebrate accomplishments on Friday. This cadence helps maintain focus and progress throughout the quarter.

3. Prioritize Friday Celebrations

Dedicate time every Friday for teams to gather and share ’the most awesome thing that happened’ in their work or department that week. This simple act makes people feel part of something special and drives positive change.

4. Streamline OKR Approval Process

Instead of hierarchical approval, have teams write their OKRs and get feedback from three relevant teams (e.g., tech, strategy, sales) within 24 hours. This fast, peer-based review prevents bottlenecks and keeps the process agile.

5. Prioritize Retrospectives Over Grading

When reviewing OKRs at the end of a quarter, focus less on precise numerical grading and more on the ‘why’ behind the outcome. The most valuable part is the retrospective—learning what went wrong and what went right to inform future actions.

6. Keep OKRs Simple

Avoid overly complicated OKR methodologies, as they often lead to teams getting caught up in rules rather than focusing on actual goals. Simple structures provide more flexibility and clarity.

7. Focus KRs on Outcomes, Not Tasks

Ensure Key Results (KRs) describe desired outcomes, not just tasks or activities. This provides flexibility in how problems are attacked and ensures the team is focused on impact rather than just completion.

8. Inspiring & Concrete Objectives

Craft Objectives that are both motivating and concrete, clearly stating what you want to see happen. An effective objective should inspire the team and make them feel like they are working on something significant.

9. “How Do We Know?” for KRs

When defining Key Results, ask the question, ‘How do we know we succeeded?’ This helps to identify measurable indicators that truly reflect the achievement of the objective.

10. Limit to Three Key Results

Aim for approximately three Key Results per Objective, using them to triangulate success. Include a hardcore number, a ‘squishier’ quality metric, and often a financial indicator, tailored to the specific objective.

11. Brainstorm KR Measurements

Dedicate at least 10 minutes to brainstorming every possible way to measure an outcome for your Key Results. This helps move past obvious ideas to discover more insightful and creative metrics.

12. Delay Future KRs

When planning for the year, set objectives for all quarters but only define Key Results for the upcoming quarter. This allows flexibility to react to new information and adapt the strategy based on learnings from previous quarters.

13. Set Ambitious but Achievable Goals

Set goals that make you feel somewhat uncomfortable but not doomed, aiming for around 70-80% success. Ambitious goals motivate teams to push boundaries and discover their full capabilities.

14. Iterate on Measurement Methods

For ‘fuzzy’ Key Results (like quality or delight), experiment with different measurement approaches (e.g., NPS, surveys, qualitative research). This iterative process helps you learn what methods are most accurate and meaningful for your company.

15. Invest in Meaningful Measurement

While easy metrics are convenient, dedicate effort to finding and implementing meaningful ways to measure complex aspects like customer delight and retention. This deeper understanding provides super value and can drive significant company growth.

16. Keep OKR Meetings Focused

To prevent OKR review meetings from becoming boring task lists, limit discussion to the top 2-5 most important initiatives. Trust your team to handle other tasks and focus on strategic conversations about progress and challenges.

17. Make OKRs Transparent

Make all company OKRs and weekly updates accessible on an intranet or shared platform. This transparency allows everyone to understand what’s happening, identify connections, and quickly see who to collaborate with.

18. Implement Weekly Status Updates

Encourage teams to send short weekly status updates (e.g., via email or Slack) including their confidence level on KRs, what they did last week, and what they plan to do next week. This practice fosters accountability and highlights obstacles for learning.

19. Use OKRs as Diagnostic Tool

View OKRs as a diagnostic tool that reveals deeper issues within your company if they are going ‘sideways.’ If OKRs are failing, look for root causes in strategy, psychological safety, or leadership clarity.

20. Define 5-Year Mission

Establish a mission that is specific enough to guide action for the next five years, rather than an overly vague, ‘forever’ mission. This provides a clear, actionable direction for the company.

21. Derive Strategy from Mission

Translate your 5-year mission into a clear strategy that outlines how you plan to win in the market and fulfill your vision. This strategy then informs your quarterly OKRs.

22. Leverage Temporal Landmarks

Piggyback on existing temporal landmarks like quarters, Mondays, or New Year’s to establish natural points for reflection and planning. Use these moments to pause, assess, and define what needs to be done next.

23. Focus on Big Rocks

Use OKRs to identify and prioritize the ‘big rocks’—the most important things that must happen each quarter. This prevents teams from spreading themselves too thin by trying to do everything at once.

24. Practice Estimating

Recognize that estimating is a learned skill, not an innate talent. Practice estimating regularly to improve accuracy, which is an incredibly valuable business skill.

25. Foster Psychological Safety

Cultivate an environment where teams feel safe to admit when something isn’t working or to propose alternative approaches. A lack of psychological safety can prevent crucial feedback and learning.

26. Leader Clarity & Approachability

As a leader, ensure your strategy is clear and that you are approachable. If your team is constantly confused or brings you every small problem, it indicates a need for greater clarity or a less intimidating leadership style.

27. Avoid Illusion of OKR Knowledge

Don’t assume you fully understand OKRs just from a quick read; delve deeper into how they truly work. Many companies fail because they implement OKRs superficially without grasping their underlying principles.

28. Co-locate Teams for Innovation

Encourage product trios (product, design, engineering) to sit together, ideally in a ‘war room’ with walls for visual aids. This physical co-location fosters shared vision, collaboration, and collective memory, which is crucial for innovation.

29. Draw Badly for Shared Vision

Use whiteboards and simple, even bad, drawings to quickly establish a shared vision with your team. This informal visual communication is more effective than polished wireframes for early-stage alignment.

30. Seek Storytelling Feedback

To improve your storytelling skills, ask trusted listeners for feedback on how you could have made your story better. This helps identify areas like blathering or insufficient detail.

31. Use Basic Story Structure

When telling a story, follow a basic beginning-middle-end structure: hook the audience with intrigue (mystery, secret, surprise), deliver your message in the middle, and conclude with success or celebration to ensure attention, comprehension, and retention.

32. PMs Must Serve Business

Product Managers should prioritize serving the business by understanding business models, target markets, and growth strategies. While user-centricity is important, PMs are responsible for the company’s survival and financial health.

33. Develop Strong Interpersonal Skills

Product Managers need strong interpersonal skills, including the ability to address difficult conversations, resolve conflicts, and engage with people. If you’re not willing to step into the ‘mess’ of human dynamics, PM might not be the right role.

34. Prioritize Qualitative Research

Invest in qualitative research and consider hiring a qualitative researcher for your team. This is the best way to gain deep insights into user psychology, understand retention signals, and inform strategic decisions.

35. Start PM Career in Eng/Design

Consider starting your career in engineering or design before moving into product management. These roles provide valuable foundational knowledge and experience with business operations.

36. Work at Small Companies to Learn

To gain broad experience and learn from various functions, seek opportunities at smaller companies. Their environment allows you to ‘poke into the corners’ and understand different aspects of the business.

37. Personal OKRs for Focus

Apply OKR principles to your personal life to maintain focus and achieve individual goals. Regularly review your personal OKRs (e.g., every Monday) to ensure your attention is directed towards what truly matters.

38. Weekly Outcome Question

Ask yourself every week, ‘What am I doing this week to get to the outcome I really want?’ This simple question helps maintain focus on desired results and drives consistent action.

39. Slow Down to Speed Up

In times of panic or urgency, resist the urge to rush. Instead, take deep breaths, read up on best practices, and thoughtfully consider the best way forward. This deliberate approach often leads to faster and more effective progress.

OKRs are more of a vitamin. They're not a medicine. So if you take OKRs and you're like, oh, this will fix everything that's wrong with you. No, that's not going to happen. It's just going to reveal everything that's wrong with your company.

Christina Wodtke

My motto is make new mistakes.

Christina Wodtke

People do not value celebrations enough.

Christina Wodtke

If during the day you meet one asshole, he's probably an asshole. But if all day long you meet nobody but assholes, you might be the asshole.

Christina Wodtke

Product sense is intuition. Intuition is compressed experience. Compressed experience comes from having lots of experience.

Christina Wodtke

I think we treat scale like it's a virtue when it's merely a tactic and it might be a bad tactic as well.

Christina Wodtke

OKR Cadence and Rituals

Christina Wodtke
  1. Every Monday, look at your week and commit to what actions you will take to move the ball forward on your OKRs. This can be an email to your boss, accountability group, or team, or a stand-up.
  2. Send a short status email or Slack update including your confidence level on key results, what you did last week, and what you're doing next week.
  3. Get together on Fridays to celebrate achievements, asking 'What was the most awesome thing that happened to you/your team this week?'
  4. Grade your current quarter's OKRs (e.g., in the second to last week) and set the OKRs for the next quarter in the very last week, aiming to complete the planning in about four days total.
  5. Instead of hierarchical approval, write your OKRs and have three teams that work closely with you review them within a 24-hour turnaround for feedback.

Storytelling Improvement

Christina Wodtke
  1. After telling a story, ask someone you trust, 'What's something I could have done to make the story better?'
  2. Plan your story with a clear beginning (hook, mystery, or surprise), a middle (where you deliver your message or product), and an end (focused on success and celebration).
five years
Recommended duration for a company's mission Before re-evaluation, allowing for flexibility rather than being 'forever'.
three
Recommended number of Key Results per Objective For triangulation, often including hardcore numbers, a squishier quality metric, and a financial aspect.
10 minutes
Recommended time to brainstorm Key Results To move past obvious ideas and uncover more insightful, 'weird' ones.
10 minutes
Target duration for weekly OKR check-in meetings After initial setup, focusing on key initiatives and blockers rather than every task.
four days total
Ideal maximum time to spend on setting OKRs for the next quarter To minimize planning time and maximize shipping time.
24 hour turnaround
Recommended timeframe for peer teams to review OKRs In an efficient, non-hierarchical approval process.
70%
Target success rate for an ambitious OKR A good goal makes you feel uncomfortable but not doomed, pushing for achievement.
250 people
Approximate company size for strong product cultures Often observed in smaller companies with a shared purpose, where scale is not seen as the primary virtue.