Write opportunities as needs, not disguised feature ideas
Distinguish a customer opportunity from a proposed solution when shaping discovery work.
The move: keep the branch at the level of need. An opportunity on an Opportunity Solution Tree is not a clever idea. It is a customer need, pain point, or desire that matters to the outcome your team owns. The practical test is simple: if the branch can be satisfied by many different solutions, it is probably an opportunity. If it already points to one interface or feature, it is probably a solution in disguise. This matters because opportunity framing protects exploration. Teams discover better products when they can compare several possible ways to help customers make progress. Jobs to…
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in