Four Pragmatic Ways to Improve Opportunity Solution Trees in PracticeDear Reader, Opportunity Solution Trees (OSTs) are a widely popular visual aid for connecting solution space work to business goals through problem space elements (similar to Impact Mapping). From seeing the way product teams adopt them in practice, here are four ways I've seen improve their impact for your work: Remember that OSTs are only a Visual SummaryI encourage teams to treat trees as the synthesis at the center (i.e., on Miro) and connect the work at the individual levels to the messy workspaces (interviews, ideation, alignment), etc., so one knows where the Outcome originated. Never treat OSTs as an Artifact of their ownTrees have to connect to execution-guiding artifacts like goals. To make sure that there's some link/documentation to the success metrics of an Output, Experiment, or if the Outcome has been moved. Worth linking to OKR tools or visual aids like Vistaly. The Outcome at the top should link to your company's or team's long-term strategic business goals. Your leading team-level goals should be driven by the solutions you decide to test and build. OSTs need to Facilitate Decision-Making where Value is createdTeams should have the hygiene to choose tools that integrate well with each other or put in the work to do it manually. I believe you can turn Miro artifacts into JIRA issues and link them. Or embed Miro Boards into Notion tasks. It's more about the team's discipline than the tooling. Use Plain Language over JargonAt the core, OSTs are a visual way to connect your business context to the problem and solution space. Instead of torturing teams to arrive at the exact "right" type of artifact per level, work with questions in plain English:
Thank you for Practicing Product, Tim
SPECIAL LAST-MINUTE DISCOUNTS:
|
| 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 #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...