Frame Outcomes Before Features
Rewrite a feature request as a measurable customer or business outcome before evaluating solutions.
The move: pause the feature debate until the outcome and opportunity are named. Why the tree works An opportunity-solution tree reduces premature convergence. The top outcome defines what success means. The opportunity layer names customer needs, pain points, and desires that explain why the outcome is not happening yet. The solution layer lists possible interventions. The experiment layer checks whether a solution actually moves the branch. What changes in the room Instead of asking "Should we build SSO or bulk refunds?" the PM can ask, "Which opportunity most blocks activation or retention, and what evidence says so?" That question changes…
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in