Build an Opportunity Solution Tree from Research Notes
Separate outcomes, opportunities, solutions, and experiments in UX research synthesis.
After discovery, the Miro board has 73 notes: complaints about import speed, requests for templates, confusion about permissions, and praise for bulk edit. The PM asks, "So what should we build?" A list of notes is not a product strategy. Opportunity Solution Tree: outcome at top, opportunities as customer needs, solutions as bets, experiments as tests. Treating feature requests as opportunities collapses discovery into backlog grooming. Step 1 Put the desired outcome at the top: increase first-week team activation from 31% to 45%. The outcome anchors the tree so opportunities do not become a random backlog. Step 2 Cluster research…
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in