How to Run an Opportunity Discovery Workshop
A practical, step-by-step playbook for facilitating a product discovery workshop that maps the opportunity space, picks a target worth pursuing, and leaves your team with a living Opportunity Solution Tree instead of a photo of sticky notes.
What is an opportunity discovery workshop?
An opportunity discovery workshop is a focused, facilitated session where a product team maps the opportunities — the customer needs, pain points, and desires — that could move a specific outcome, and then decides which one to pursue first.
It deliberately keeps the team in the problem space. Instead of asking "what should we build?", it asks "which customer problem is most worth solving to reach our outcome?" The output is the opportunity layer of an Opportunity Solution Tree: a clear, prioritized map you can keep working long after the room empties.
Run one when you are starting on a new outcome, when your backlog has drifted into a pile of disconnected features, or whenever the team can't articulate why the next thing on the roadmap matters to customers.
Before the workshop
Most of a great workshop happens before anyone walks in. Four things to prepare:
A workshop without a focus produces a mess. Anchor the session to a single measurable outcome (e.g. "increase weekly active teams"), not a feature or a vague theme.
Pull together recent interviews, support tickets, surveys, and analytics. Opportunities should come from customer signal, not opinion. Share it before the room opens.
The product trio (PM, designer, engineer) plus a couple of people close to customers. Big enough for diverse views, small enough to actually converge.
Whether on a wall or a shared canvas, prepare three zones: the outcome at the top, space for opportunities below it, and a parking lot for solutions (so they stop hijacking the conversation).
The agenda: a two-hour run of show
A repeatable structure for a single-outcome session. Timebox every step — the constraint is what forces decisions.
Frame the outcome
15 minWrite the target outcome at the top of the tree and make sure everyone agrees on what it means and how it is measured. This is the root everything hangs from.
Share the evidence
20 minWalk through the customer signal you gathered: quotes, pain points, behaviors, metrics. The goal is a shared, grounded picture of the customer before anyone proposes ideas.
Diverge: map opportunities
20 minSilent, individual ideation. Everyone captures the customer needs, pain points, and desires they see in the evidence — one opportunity per sticky. No solutions yet, and no debate.
Cluster and de-duplicate
20 minGroup similar opportunities, merge duplicates, and name each cluster in the customer’s words. You are shaping the opportunity space, not the solution space.
Structure the tree
25 minArrange the clusters into a hierarchy under the outcome: broad opportunities branching into more specific sub-opportunities. This is your draft Opportunity Solution Tree.
Pick a target — or decide how to pick it
15 minChoose the opportunity with the best mix of customer importance, business impact, and evidence behind it. You don’t need the perfect choice — a good-enough opportunity you can move on and test beats a perfect one you never commit to. But if the top candidates rest on opinion rather than evidence, don’t force it: agree what evidence would settle it and make gathering that the next step.
Commit to next steps
10 minCapture owners and the next discovery action — usually an assumption to test or an interview to run — so the energy in the room turns into momentum on Monday.
Who should be in the room
Small and cross-functional beats big and representative.
Common pitfalls to avoid
The four ways discovery workshops most often go sideways.
The most common failure. The moment "we should build X" appears, the opportunity space collapses. Park solutions and stay in the problem space until you have chosen a target.
A workshop fueled by opinion just amplifies the loudest voice. Without customer signal, you are mapping assumptions, not opportunities.
Twelve people cannot converge. Keep the core group small and share the output widely afterward instead of inviting everyone into the room.
The classic ending: a photo of sticky notes that never gets touched again. The tree needs a living home where the team can keep working it, or the workshop was theater.
Choose on evidence, not conviction
The hardest part of selection is separating what you know from what you believe. In Outcomify you attach evidence to each opportunity — an interview quote, a metric, a support ticket — rated by strength and whether it supports, refutes, or complicates it. Each opportunity gets a confidence score, so the line between signal and opinion is visible to the whole room.
An opportunity propped up on opinion can’t hide: with no evidence — or only a “gut” tag — it reads as exactly that. And because you log evidence that refutes, not just confirms, the tree resists confirmation bias instead of rewarding the loudest voice.
Where the evidence is thin, that is your signal to decide how to decide. The missing evidence is precisely what to go learn — turn each gap into an interview or a test before you commit a quarter to it.
Evidence de-risks the bet; it does not remove risk. Back the best-supported good-enough opportunity and move — a decision the team can act on takes the product forward, where a hunt for the perfect choice just stalls it.
Turn the output into a living tree, not a dead board
You leave the room with dozens of candidate opportunities. The hard part isn't generating them — it's curating them and keeping them alive. In Outcomify, you don't dump everything into the tree and hope. You capture workshop output as drafts.
- Propose, don't pollute. Every candidate opportunity lands as a proposed draft in a review queue — visible, but not yet part of the official tree.
- Let Canopy do the typing. Paste your raw notes and Canopy, the in-product assistant, drafts structured opportunities for you — phrased as customer needs and placed under the right outcome. It proposes; it never writes to the tree on its own.
- Review and commit together. The team reviews the drafts, merges duplicates, edits the wording, and commits the ones that earn a place. Nothing lands automatically — humans decide.
- Keep working it. The result is a shared Opportunity Solution Tree the whole team can keep evolving every week — the start of continuous discovery, not the end of a workshop.
Proposals beat silent writes: drafts wait for a human to approve them before they become part of the tree.
Frequently Asked Questions
Common questions about running opportunity discovery workshops
Keep exploring
What is an Opportunity Solution Tree?
The visual framework your workshop output lives in — outcomes to opportunities to solutions.
Building Outcome-Driven Teams
How to build and lead teams that own problems instead of feature lists.
Outcomes vs Outputs
Why shipping features is not the goal, and how to focus discovery on real impact.
The Outcome-Driven Backlog
Turn your backlog and sprint planning into a pull system fed by discovery.
Give your workshop a living home
Outcomify turns workshop sticky notes into a shared Opportunity Solution Tree your team keeps working — with drafts, review, and an AI assistant that proposes, never overwrites.