How a Product Vision Board saved my StrategyDear Reader, I once led a newly formed product team that aimed to develop a product to increase the monetization of a specific user segment. I co-led a long Discovery effort that validated and scoped this product. At one point during our Delivery journey, my boss approached the team while I was on leave and asked them what they were trying to accomplish. Because the strategic clarity for our efforts only existed in my head, they couldn't articulate it clearly. Which led to my boss, rightfully so, demanding that I get this sorted so that the team could connect to the choices behind our tactical priorities. It didn't take me long to synthesize existing work into a simple Product Vision board format. This created much more clarity for the team to get behind and engage more in our product decisions, which makes it embarrassing that I didn't create this clarity in the first place, because everything was so clear in my head. Please think of any Strategy template as a distribution channel you need to reach the audience that should get value from your Strategy. For example, Roman Pichler’s Product Vision Board is one of the simplest canvases that has been around for a while. It was my format of choice back in the days when I had to step up my ability to communicate a Product Strategy to the team mentioned in this essay's introduction.
I know that the seeming simplicity of synthesizing Strategy through canvases or statements can be deceiving. Remember that simplicity stands on the shoulders of the messy work you did before, choosing decisive components that form a coherent picture and exist within the boundaries of your company strategy. Let this be a reminder that your Strategy can be perfectly thought out and based on well-researched insights, co-created by Individual Contributors and Leadership, and contain sustainable advantages over alternatives. But if nobody understands it and you can't integrate it into the decision-making processes of teams, the value of a useful Product Strategy will remain locked. 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: I finally got to making the first Cold Brew of the season. Here's my go-to recipe for it. Let's Meet in Munich!At PendomoniumX Munich on July 8, I’ll be sharing a pragmatic guide to finally connect the dots between strategy, OKRs, and discovery—so your product teams worry less about correctness and focus on context and progress. Save 50% using my discount code TIMHERBIG50.
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...