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 #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...