How to predict the future of your OKRs (and why it matters)​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 futureOne 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" testLet’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. 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​ What did you think of this week's newsletter?
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. |
1 tip & 3 resources per week to improve your Strategy, OKRs, and Discovery practices in less than 5 minutes. Explore my new book on realprogressbook.com
Product Practice #427 Your Strategy names one audience; weak evidence describes another PUBLISHED Sep 24, 2026 READ ON HERBIG.CO Dear Reader, One of the most common questions that came up in my recent Strategy to Execution workshop at the ProductLab conference revolved around intentional strategic audiences vs. reactive chasing of new business. Many teams either operate where the company focuses on all customers of a given market (i.e., "all lawyers") or throw a wishful-thinking segment out...
Product Practice #426 You don’t need toinvestigate every problem PUBLISHED Sep 18, 2026 READ ON HERBIG.CO Dear Reader, Discovery without direction leads to endless exploration. Teams can feel overwhelmed, believing they must investigate every problem. Your strategic audience choices determine which customer feedback deserves priority investigation, while discovery insights reveal whether your strategic assumptions about customer problems and competitive positioning hold up in practice. This...
Product Practice #425 What Part of YouIs Making the Decision? PUBLISHED Sep 11, 2026 READ ON HERBIG.CO Dear Reader, For much of my career, I’ve helped product teams work through uncertainty. Chilling with my buddy King Arthur at Tintagel Castle I challenged assumptions, introduced frameworks, and helped people make better decisions when there was no obvious answer. While I still love doing that work, I’ve become increasingly interested in a deeper question over the past six years: From where...