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 #394 Can an AI Interviewer doYour Concept Testing? PUBLISHED Feb 6, 2026 READ ON HERBIG.CO Dear Reader, What happens when you let an AI do the concept testing of design variations? I used Reforge's AI Concept testing* to find that out. As a prototype, I chose an app idea that lets you document taste notes from brewing specialty coffee. And I need your help exploring how AI-led interviews feel for participants (and improving the app design โ๏ธ). I mostly went with their...
Product Practice #393 How much Money willthis Feature make? PUBLISHED Jan 30, 2026 READ ON HERBIG.CO I'm hosting my first free live webinar in 2026: Go From "We Need a Strategy" to "Here's Exactly What We're Doing and Why" โ In 60 Minutes on Feb 11 at 5:00 PM CET (11:00 AM EST | 8:00 AM PT). Bring all your questions, and I will work through them on the spot. Note that there will be no recording - this is about hands-on interaction, not just information transmission. CLAIM YOUR FREE SPOT Dear...
Product Practice #392 From Product Jargonto Plain English READ ON HERBIG.CO PUBLISHED Jan 23, 2026 READING TIME 3 min & 29 sec Dear Reader,I often feel that, somewhere along the way, we, as an industry, started optimizing for sounding like product people instead of speaking like humans in plain English (or any other language). What would happen if we dropped the product lingo and used plain English to describe what's needed? I find it increasingly liberating for product teams to describe...