🛠️ How to predict the future of your OKRs (and why it matters)


How to predict the future of your OKRs (and why it matters)

READ ON

​HERBIG.CO​

PUBLISHED

Oct 25, 2024

READING TIME

3 min & 32 sec

​Dear Reader,​

Ever sat in an OKR review meeting feeling like you're just going through the motions or reporting without meaning? You're not alone. As a Head of Product, I've been there too. But what if I told you there's a way to make your OKRs truly useful for decision-making? Let's dive in.

The power of predicting the future

One of my favorite ways of helping teams pressure-test their OKRs is by trying to predict the future. I want them to think about the answer to “Imagine a check-in 4 weeks down the road. With whom will you look at these OKRs and discussion emerges from looking at the changed values and confidence?”

This is similar to a premortem exercise. By predicting the future, teams can anticipate how useful their OKRs are for making decisions.

Why typical OKRs fail the "check-in-ability" test

Let’s use one of the first (documented) KRs I wrote as a Head of Product 6+ years (don’t judge me):

KR1: Understand 'feature' map of product status quo and compare with user expectations.

KR2: Develop design guiding principles for product simplification.

Imagine a check-in four weeks down the road:

A: “How are we doing on KR1?”

B: “I think we better understood the feature map.”

A: “Ok, by how much?”

B: “I think would put the confidence at 80%".”

A: “But…why?”

B: “Because it still feels on track.”

A: “And KR2?”

B. “We have scheduled a first meeting to discuss the design guiding principles. So, I estimate the progress to be about 20%.”

A: “Will you do anything differently based on the progress of these KRs?“

B: “No, I think everything works according to plan.”

A:

How would you rate the check-in-ability of these KRs? Spoiler: NOT GREAT. They can neither demonstrate real progress nor guide a conversation about priorities.

But fixing KRs like these by just adding numbers would be too short-sighted. After all, how check-in-able is a KR with a number, if you can’t influence it, if it’s too lagging, or if it’s a generic KPI?

Predicting the future of your OKRs isn't about being psychic. It's about understanding what they will help you do differently later, so they can be more useful now.

HOW TO PUT THIS THEORY INTO PRACTICE

  • Be clear on what OKRs should do for you. Articulate what change OKRs should create for whom? Is this primarily a reporting exercise or an actual prioritization tool for the team?
  • Role-play a check-in. How would the conversations of a check-in for this OKR go? Would there be meaningful conversations or just nodding in agreement as you blaze through the numbers?
  • Change the attributes. Which attribute is missing from your OKRs to make them more check-in-able? Do you need more precise numbers? Do the KRs need to be more leading? Do you need a more influenceable metric?

Did you enjoy this one or have feedback? Do reply. It's motivating. I'm not a robot; I read and respond to every subscriber email I get (just ask around). If this newsletter isn't for you anymore, you can unsubscribe here.

Thank you for Practicing Product,

​Tim​

Content I found Practical This Week

How to Set Effective Quarterly Goals and OKRs for Platform Engineering Teams: A Practical Guide

Once OKRs are agreed on, the initial problems they relate to, and the groupings, will lead to some high-level features or initiatives. Each initiative can then be refined further with the teams to identify the work that needs to be done, and how it might be broken down into small increments to develop and ship (in the example, you can see how it would link to a sprint planning priority and sprint goal).

The #1 Reason Why Most OKRs Suck!

video preview​

How to track slow-moving OKRs

But if your lagging indicators are moving slowly (ex: you close 1 or 2 customers per quarter), then you should opt for leading indicators instead. You’ll need to find the best metrics that can help you not only assess your confidence, but also help you understand how to adjust your strategy. Using lagging metrics can sometimes feel like more art than science, but the key is to have something that can be observed on a weekly basis.

What did you think of this week's newsletter?

Who is Tim Herbig?

As a Product Management Coach, I guide Product Teams to measure the real progress of their evidence-informed decisions.

I focus on better practices to connect the dots of Product Strategy, Product OKRs, and Product Discovery.

Enjoy the newsletter? Please forward it. It only takes 2 clicks. Coming up with this one took 2 hours.

Product Practice Newsletter

1 tip & 3 resources per week to improve your Strategy, OKRs, and Discovery practices in less than 5 minutes.

Read more from Product Practice Newsletter

Product Practice #375 Bringing Discovery to EngineersWho 'Just Want to Build' READ ON HERBIG.CO PUBLISHED Sep 12, 2025 READING TIME 5 min & 47 sec Dear Reader, I've coached product teams where engineering managers push back on discovery work, convinced that buildins is always faster than validating. They might see testing and validating ideas as obstacles between them and shipping cooler and shinier features. And, should you always extend your Discovery to a quarter because "that's how long...

Product Practice #374 How to Go From Customer Problems to Outcome OKRs READ ON HERBIG.CO PUBLISHED Sep 5, 2025 READING TIME 5 min & 18 sec Dear Reader, Most teams skip the hardest part of creating OKRs: translating validated customer problems into meaningful metrics. You've done the discovery work. Your interviews revealed that drivers on your ridesharing platform struggle with shift planning—they can't predict which areas will be busy, leading to wasted time and lower earnings. But instead...

Product Practice #373 Discovery Collaborationis about Skills, not Titles READ ON HERBIG.CO PUBLISHED Aug 29, 2025 READING TIME 3 min & 15 sec Dear Reader, Too many people get fixated on “we have to hire these roles to set up a Product Trio” when, in reality, they can get going from wherever they are. Having one representative from each domain of expertise is ideal, but it’s rarely the reality for product teams. So, instead of waiting until everything’s “in place,” here’s how to get going even...