Why did I write a
|
โDear Reader,โ
I decided to send this newsletter one day earlier than usual this week because of current events. You guessed right:
After more than two years of work, I'm proud and excited to share with you that the paperback version of my book, Real Progress: How to Connect the Dots of Product Strategy, OKRs, and Discovery, is now live on Amazon. You can find all the local buying links below.
๐ฉ๐ช Amazon Germany, Austria, and Switzerlandโ
๐ฌ๐ง Amazon UKโ
๐บ๐ธ Amazon USโ
๐ซ๐ท Amazon Franceโ
๐ณ๐ฑ Amazon Netherlandsโ
๐จ๐ฆ Amazon Canadaโ
๐ฆ๐บ Amazon Australiaโ
๐ฎ๐น Amazon Italyโ
๐ต๐ฑ Amazon Polandโ
๐ฎ๐ณ Amazon Indiaโ
๐ง๐ท Amazon Brazilโ
Let me share the essence of what this book is about to get you excited:
In this book, I focus on three key domains for building products and what Real Progress looks like for each.
Product Strategy needs to help you say no.
Product OKRs need to help you measure progress.
Product Discovery needs to help you reduce uncertainty.
To ensure teams can create value in their context, they need to measure their influence on solving the right customer problems. And the right problems are those that help drive strategic choices and business goals. Alibi Progress would mean to complete activities like writing OKRs or talking to customers, only to tick them off.
To make Real Progress, teams need to understand and practice two core ideas:
The book is designed to be both a sequential read and a practical reference that you can access based on your most pressing needs:
No matter where you begin, you'll find references to the other domains throughout each chapter, helping you connect the dots and avoid the trap of isolated practices.
Of course, in reality, the sequencing across these three domains is much less linear. You might start with explorative Discovery, using insights to set your Strategy, derive OKRs to guide your Deliver, while engaging in more evaluative Discovery to test solutions.
But, for the purpose of your and my sanity, I decided on a more distinct approach by arranging them in a particular order. That doesnโt mean itโs the right order you have to follow and that applies to all circumstances. I will present the aspects of each of the three practices in a way so you can choose your own adventure of where to start and how to make your practices more valuable in your context.
I hope you enjoy reading the book as much as I enjoyed writing it for practitioners like you. Thank you for your support, and let me know how the book helps your work.
Thank you for Practicing Product,
โTimโ
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 #397 3 Things to Put into YourNext Strategy Document PUBLISHED Feb 27, 2026 READ ON HERBIG.CO Dear Reader, The most effective strategy document I've seen doesn't worry about the looks or format. Whether it's a scrappy Google Doc or a fancy Miro template, what matters is the quality and cohesiveness of the information it contains. Make sure what you cover aligns with your company's expected standards to ensure stakeholder understanding and, consequently, buy-in. But make sure...
Hallo liebe:r Leser:in, English Translation below for internal forwarding to your German colleagues Du lieferst Features aus und wirst nach KPIs gefragt โ ohne Verbindung zu Erfolg fรผr Nutzer:innen und Geschรคft. Die Strategie deines Unternehmens ist entweder zu vage oder fehlt ganz. Das Ergebnis: Alibi Progress statt echter Wirkung.In meinem Workshop "Strategische Umsetzung statt KPIs abarbeiten โ Entwicklung & Messung von Produktstrategie am 4. Mai im Rahmen der Product Owner Days 2026...
Product Practice #396 MECE: Double the Usefulnessof Your Metrics Trees PUBLISHED Feb 19, 2026 READ ON HERBIG.CO Dear Reader, Many resources say your metrics trees need to be "MECE." But how do you do it? MECE stands for: Mutually Exclusive Collectively Exhaustive In the context of metrics trees, this means mapping the individual drivers of an overarching goal in a way that allows us to identify and improve domain-specific levers through selective focus, while creating holistic...