Building an Opportunity Solution Tree

Set the outcome root

Begin with one product outcome, not a company slogan or delivery target. It should name a changed behavior for a defined group and have a baseline. A subscription team might seek to increase the share of new editors who publish a first project within three days. This root provides a common test for whether an opportunity belongs on the tree.

Check influence and value before proceeding. If the team cannot explain how product decisions might affect the measure, select a closer outcome. Add guardrails beside the root even though they are not branches. Faster publishing should not come from accidental public sharing, hidden quality loss, or pressured users.

Capture customer opportunities

Derive opportunities from specific customer stories, observations, support records, and behavior data. Phrase them as needs, pain points, or desires: 'I cannot tell which template fits my project' rather than 'add a template recommender.' Preserve the situation and actor. Broad labels such as onboarding or usability are too vague to guide solution comparison.

Group opportunities by parent-child relationships where solving a child contributes to the parent. Avoid forcing a perfect hierarchy. The tree is useful when it reveals choices and gaps, not when every note has an elegant location. Keep evidence links and mark thin branches so visual prominence does not masquerade as confidence.

Select an opportunity deliberately

Compare opportunities using importance to the outcome, frequency, customer consequence, strategic fit, existing satisfaction, reach, and evidence strength. Discuss dimensions instead of collapsing uncertain judgments into a falsely precise score. A smaller frequent obstacle may be more tractable than a dramatic problem the product is poorly positioned to address.

Choose one branch for focused discovery and record why other branches wait. Selection is a decision, not proof that the chosen opportunity is objectively best. Revisit it as interviews, analytics, or market conditions change. Keeping unselected branches visible reduces the tendency to rediscover the same ideas every quarter.

Explore solutions and assumptions

Generate several meaningfully different ways to address the selected opportunity. Include workflow, content, service, policy, and removal options, not only interface additions. Link each solution to the opportunity it serves. If an idea cannot explain that connection, place it outside the current tree rather than bending the structure around it.

List assumptions about desirability, usability, feasibility, viability, and ethics. Identify the assumption that is both uncertain and capable of sinking the idea. Design the smallest credible test for that assumption. Update the tree with results, retaining rejected branches and reasons so learning survives personnel and planning changes.

Map first-week accounting activation

New small-business customers connect a bank account but many never categorize their first set of transactions.

1. Set the outcome as increasing connected customers who accurately categorize ten transactions within seven days.
2. Synthesize stories into opportunities such as unfamiliar accounting labels, uncertainty about rules, and fear of making irreversible mistakes.
3. Compare evidence and choose fear of irreversible changes because it is frequent, consequential, and closely tied to the outcome.
4. Generate reversible preview, guided review, and accountant-confirmation solutions rather than committing to one interface.
5. Test whether customers understand and trust a reversible preview before building the complete workflow.

Opportunity solution tree record

Store the evidence and decisions behind the visual tree with these fields.

• Outcome root: actor, behavior, baseline, target direction, period, value, and guardrails.
• Opportunity node: customer wording, situation, evidence links, frequency, consequence, and confidence.
• Selection note: comparison dimensions, chosen branch, deferred alternatives, owner, and review trigger.
• Solution branch: distinct approach, intended mechanism, dependencies, and opportunity connection.
• Assumption test: riskiest belief, test method, decision threshold, observed result, and tree update.

Common mistakes

• Putting requested features in the opportunity layer and losing the underlying customer need.
• Building a large decorative tree without evidence links, selection decisions, or active tests.
• Generating only variations of the first solution and treating them as a broad option set.

Try one

Sources

• Product Talk opportunity solution treesPrimary Product Talk explanation of mapping outcomes, opportunities, solutions, and assumption tests.
• Product Talk continuous discovery habitsPrimary Product Talk guidance on continuous customer discovery by product teams.