Principles of Product Management: OKRs (Objective & Key Results) – Setting, Cascading, Leading vs Lagging Indicators

OKRs (Objective & Key Results) – Setting, Cascading, Leading vs Lagging Indicators

OKRs (Objectives & Key Results) – Setting, Cascading, Leading vs. Lagging Indicators

What This Is

OKRs (Objectives and Key Results) are a goal-setting framework used to align teams, measure progress, and drive outcomes—not just output. An Objective is a qualitative, ambitious, and inspirational goal (e.g., "Become the most trusted payment app for freelancers"). Key Results (KRs) are 3–5 quantitative, measurable outcomes that track progress toward the Objective (e.g., "Increase freelancer retention from 60% to 80% MoM," "Reduce payment failure rate from 5% to 1%").

Why it matters: OKRs force clarity, focus, and accountability. Without them, teams risk building features that don’t move the needle (e.g., a fintech app adding a "dark mode" when the real problem is high payment failures). Real-world example: Stripe used OKRs to scale its fraud detection system—Objective: "Make Stripe the safest place to transact online" with KRs like "Reduce fraudulent chargebacks by 30% YoY" and "Increase merchant fraud detection accuracy to 95%."

Key Terms & Frameworks

• Objective (O): A qualitative, time-bound, ambitious goal (e.g., "Improve new user onboarding to reduce time-to-first-value").
• Good: Inspiring, outcome-focused, aligned with company mission.

• Bad: Vague ("Make users happy"), output-focused ("Launch onboarding tutorial").

• Key Results (KRs): Quantitative, measurable outcomes (not tasks) that track progress toward the Objective. Should be binary (achieved or not) and ambitious (70% success = "stretch goal").

• Formula: KR = Metric + Target + Timeframe (e.g., "Increase activation rate from 40% to 70% by Q3").

• Leading vs. Lagging Indicators:

• Leading: Predictive metrics (e.g., "% of users who complete onboarding tutorial") that influence future outcomes.
• Lagging: Outcome metrics (e.g., "30-day retention rate") that reflect past performance.

• Why it matters: Leading indicators help you course-correct early; lagging indicators tell you if you succeeded.

• Cascading OKRs: Aligning OKRs top-down (company → team → individual) to ensure cohesion.

• Example:

  
  
  • Company Objective: "Become the #1 e-commerce platform for small businesses."
  • Product Team KR: "Increase seller GMV by 20% YoY."
  • Growth Team KR: "Improve seller onboarding completion rate from 50% to 80%."

• OKR Scoring: Typically scored on a 0–1 scale (0 = no progress, 1 = full achievement). 0.7 is the "sweet spot"—if you hit 1.0, your KRs weren’t ambitious enough.

• Formula: Score = (Actual Result - Baseline) / (Target - Baseline)

• North Star Metric (NSM): The single metric that best captures the value your product delivers (e.g., Airbnb’s "Nights Booked", Slack’s "Messages Sent").

• Why it matters: OKRs should ladder up to the NSM.

• Input vs. Output Metrics:

• Output: What you build (e.g., "Launch a referral program").
• Input: What drives outcomes (e.g., "Increase referral conversion rate from 5% to 15%").

• Rule: OKRs should focus on input metrics (controllable) over output metrics (unpredictable).

• Health Metrics: Guardrail metrics that ensure you’re not achieving KRs at the expense of other goals (e.g., "Maintain NPS > 50 while increasing engagement").

• OKR Cycle: Typically quarterly, with:

• Planning (2–4 weeks before quarter starts).
• Execution (weekly/biweekly check-ins).

• Scoring & Retrospective (end of quarter).

• Moonshots vs. Roofshots:

• Moonshot: 10x improvement (e.g., "Increase DAU from 10K to 100K").
• Roofshot: 2x improvement (e.g., "Increase DAU from 10K to 20K").

• When to use: Moonshots for innovation, roofshots for incremental growth.

• OKR vs. KPI:

• OKR: Ambitious, time-bound, outcome-focused (e.g., "Increase retention by 30% this quarter").
• KPI: Ongoing, operational metric (e.g., "Weekly active users").
• Key difference: OKRs are aspirational; KPIs are business-as-usual.

Step-by-Step / Process Flow

1. Define the Objective (O)

• Action: Start with the "Why"—what’s the most important outcome for your team this quarter?
• Example: "Make our mobile app the primary tool for freelancers to manage finances."
• How to validate:
• Align with company OKRs and North Star Metric.
• Ask: "If we achieve this, will it move the needle for the business?"
• Avoid output-focused objectives (e.g., "Launch a budgeting feature" → instead, "Help freelancers save 10% more by Q3").

2. Draft Key Results (KRs)

• Action: Brainstorm 3–5 measurable outcomes that prove the Objective is achieved.
• Template: Increase/Decrease [Metric] from [Baseline] to [Target] by [Timeframe].
• Example KRs for the freelancer Objective:
  1. "Increase % of freelancers using the app for invoicing from 30% to 60%."
  2. "Reduce time to create an invoice from 5 mins to 2 mins."
  3. "Increase freelancer retention (30-day) from 40% to 70%."
• How to validate:
• Are they leading indicators (predictive) or lagging indicators (outcome)?
• Are they controllable (input metrics) or uncontrollable (output metrics)?
• Do they pass the "So what?" test? (e.g., "Increase DAU" → "So what?" → "Higher DAU → more revenue").

3. Align & Cascade OKRs

• Action: Ensure OKRs ladder up to company goals and align across teams.
• Example:
  • Company Objective: "Become the #1 freelancer financial platform."
  • Product Team KR: "Increase freelancer retention by 30%."
  • Engineering Team KR: "Reduce app crash rate from 2% to 0.5%."
  • Marketing Team KR: "Increase freelancer sign-ups from 10K to 25K/month."
• How to validate:
• Ask: "If every team hits their KRs, will the company Objective be achieved?"
• Avoid conflicting OKRs (e.g., Marketing wants "More sign-ups" while Product wants "Higher-quality users").

4. Set Health Metrics

• Action: Identify guardrail metrics to ensure KRs aren’t achieved at the expense of other goals.
• Example: If your KR is "Increase engagement (sessions/user)", a health metric could be "Maintain NPS > 50."
• How to validate:
• Ask: "What could go wrong if we hyper-focus on this KR?"
• Common health metrics: NPS, churn rate, support tickets, fraud rate.

5. Execute & Track Progress

• Action: Set up weekly/biweekly check-ins to review progress.
• Tools: Google Sheets, Gtmhub, Asana, or Notion.
• Template for tracking:
  | KR | Baseline | Target | Current | % Complete | Confidence (1–10) |
  |----|----------|--------|---------|------------|-------------------|
  | Increase retention from 40% to 70% | 40% | 70% | 55% | 50% | 7 |
• How to validate:
• Are we on track? If not, pivot or double down.
• Are the KRs still relevant? (e.g., market shift, new competitor).

6. Score & Retrospective

• Action: At the end of the quarter, score each KR (0–1) and conduct a retrospective.
• Scoring example:
  • KR: "Increase retention from 40% to 70%" → Actual: 60% → Score: (60 - 40) / (70 - 40) = 0.67.
• Retrospective questions:
  • What worked? What didn’t?
  • Were the KRs too easy/hard?
  • Did we focus on the right things?

Common Mistakes

PM Interview / Practical Insights

1. "How would you set OKRs for [X product]?"

• What they’re testing: Can you translate business goals into measurable outcomes?
• How to answer:
• Start with the North Star Metric (e.g., "For a food delivery app, it’s 'Orders Delivered'").
• Identify leading indicators (e.g., "% of users who add items to cart").
• Draft 3–5 KRs (e.g., "Increase cart completion rate from 30% to 50%").
• Mention health metrics (e.g., "Maintain delivery time < 30 mins").

2. "How do you handle conflicting OKRs between teams?"

• What they’re testing: Can you align stakeholders and prioritize trade-offs?
• How to answer:
• Example: Marketing wants "More sign-ups" while Product wants "Higher-quality users."
• Solution:
  1. Align on the North Star Metric (e.g., "Revenue per user").
  2. Compromise (e.g., "Marketing focuses on high-LTV users").
  3. Set shared KRs (e.g., "Increase % of high-LTV users from 20% to 40%").

3. "Leading vs. Lagging Indicators – How do you choose?"

• What they’re testing: Do you understand predictive vs. outcome metrics?
• How to answer:
• Leading indicators = Early signals (e.g., "% of users who complete onboarding").
• Lagging indicators = Final outcomes (e.g., "30-day retention").
• Rule: Use leading indicators for KRs (to course-correct) and lagging indicators for Objectives (to measure success).

4. "How do you cascade OKRs from company to team level?"

• What they’re testing: Can you align strategy with execution?
• How to answer:
• Example:
  • Company Objective: "Become the #1 SaaS tool for remote teams."
  • Product Team KR: "Increase team collaboration feature usage by 40%."
  • Engineering Team KR: "Reduce latency in real-time collaboration from 500ms to 200ms."
• Key: Each team’s KR should directly contribute to the company Objective.

Quick Check Questions

1. Your team’s OKR is to "Increase user engagement by 50%." The engineering team wants to add a gamification feature (badges, leaderboards), but user research shows this could annoy power users. How do you decide?

• Answer: Prioritize the input metric over the output. Instead of "Launch gamification," set a KR like "Increase % of users who complete 3+ sessions/week from 20% to 40%" and test gamification as one of several experiments (A/B test, measure impact on retention).
• Why: OKRs should focus on outcomes, not outputs.

2. Your company’s North Star Metric is "Monthly Active Users (MAU)." Your team’s OKR is to "Increase MAU by 30%." After Q1, MAU is up 25%, but NPS dropped from 60 to 45. What do you do?

• Answer: Pause and investigate. The KR was achieved, but health metrics (NPS) suffered. Possible actions:
• Adjust the KR (e.g., "Increase MAU by 30% while maintaining NPS > 50").
• Dig into why NPS dropped (e.g., spammy notifications, poor UX).
• Add a health metric (e.g., "Maintain NPS > 50").
• Why: OKRs should not harm other business goals.

3. A stakeholder insists on adding "Launch a dark mode" as a KR. How do you respond?

• Answer: Push back—this is an output, not an outcome. Instead, ask:
• "What problem does dark mode solve?" (e.g., "Reduce eye strain for night users").
• "How will we measure success?" (e.g., "Increase nighttime session duration by 20%").
• Reframe as: "Improve nighttime user experience to increase session duration by 20%."
• Why: OKRs should measure impact, not deliverables.

Last-Minute Cram Sheet

1. OKR = Objective (qualitative) + Key Results (quantitative, 3–5 max).
2. KRs should be binary (achieved or not) and ambitious (70% success = stretch goal).
3. Leading indicators = predictive (e.g., onboarding completion); Lagging = outcome (e.g., retention).
4. Cascading OKRs: Company → Team → Individual (must align top-down).
5. Score OKRs on 0–1 scale (0.7 = sweet spot).
6. Health metrics = guardrails (e.g., NPS, churn) to prevent trade-offs.
7. Input metrics (controllable) > Output metrics (unpredictable).
8. Moonshot (10x) vs. Roofshot (2x) – use moonshots for innovation.
9. ⚠️ Avoid output-focused KRs (e.g., "Launch X") – focus on outcomes.
10. ⚠️ Too many KRs = diluted focus (stick to 3–5).