The OKR Parallel
|
Dear Reader,
Welcome back! I for sure started to miss writing these weekly essays about halfway through my summer break. Between speaking appearances and nudging my book closer to completion, I also enjoyed some time off. I hope you had (or still have) a fantastic summer full of nourishing experiences and some time to recharge. And now, onto this week's essay.
Here's an interesting cycle: Company Strategy is written (and maybe communicated). Company OKRs are written based on KPIs and some strategic topics. Teams model their OKRs after the company OKRs. The company insists that other things are "also important." So when teams share their roadmap items connected to the OKRs, but get pushback on where the work on these "other important things" is happening.
I call this the OKR Parallel Universe Syndrome. You may not have heard of it, but I'm sure you've experienced it.
When failing to address the hard questions that make OKRs effective, your Key Results may represent what the company wishes to work on. Still, they undermine making progress on those priorities by communicating an additional range of priorities that are deemed more important.
It's tempting to keep a backdoor of priorities open next to your OKRs, to have more wiggle room and be less committed to what you defined at the beginning of the quarter. But that's a lose-lose situation.
The company stays stuck with incremental KPI improvements instead of strategic progress.
Nobody works on these actual priorities because they're not measurable.
The value, and therefore the buy-in, for measuring progress through a method like OKRs gets undermined, further reducing the team's commitment.
To circumvent that, I recommend creating a shared understanding around these fundamental principles before writing your OKRs:
No facilitation technique can save your OKR drafting if there's no agreement on the aspects above. However, when these are in place, you can encourage people to move beyond vanity metrics, such as Key Results (KRs), and start using actionable metrics to communicate priorities.
There's always a good reason to adjust priorities. But to ensure teams act on them, use the possibility to change the OKRs, instead of adding another PowerPoint slide to the next all-hands.
Did you enjoy the newsletter? Please forward it. It only takes two clicks. Creating this one took two hours.
Thank you for Practicing Product,
Tim
PS.: Coffee Kintsugi spotted at elbgold Hamburg.
I'm excited to bring my beloved in-person workshops back to Berlin in January 2026. You can choose between 1-day workshops on Product Strategy, Product OKRs, or Product Discovery, or opt for the full 3-day experience for you or your team.
| LEARN MORE |
(reach out for custom team quotes)
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 #403 Linked Better Practices over Stacked Best Practices PUBLISHED Apr 9, 2026 READ ON HERBIG.CO Dear Reader, During my last webinar on Connect Strategy, Goals, and Discovery with Progress Wheel, I asked people which part of their work is most prone to Alibi Progress. Almost everyone who chimed in named OKRs. And that's because many OKR cycles start the same way for teams: Someone opens a spreadsheet, fills in three to five semi-random metrics, and picks a value that isn't...
Product Practice #402 Product Discovery forInternal Enabler Teams PUBLISHED Apr 2, 2026 READ ON HERBIG.CO Dear Reader, Because the customers of your product just sit three desks away, you might think you can just "talk to them." And that's precisely what often leads to the low adoption of better product practices among product teams working on internal products (also sometimes called Enabler Teams). And why, when a user has a company email address, it is likely nobody's doing discovery on...
Product Practice #401 How to Close Your Confidence Loop PUBLISHED Mar 26, 2026 READ ON HERBIG.CO Dear Reader, Most teams can tell you what they're building. Far fewer can tell you why it matters and how they will know it has worked. And I mean in a connected, defensible way that traces from their next release or discovery back to a company goal. That gap is where confidence lives (or doesn't). The confidence loop describes the critical questions you need to be able to answer and connect to...