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 #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...
Product Practice #400 Get your North Star Metric Reviewed by me PUBLISHED Mar 19, 2026 READ ON HERBIG.CO Dear Reader, To celebrate the 400th edition of this newsletter (🥳), I thought, why not try something different: Share your current North Star Metric and some high-level context with me through the form below, and I'll send you a personalized review video - for FREE and without AI processing. Just me, in front of a camera, sharing my thoughts on your North Star Metric. There's no hook,...