A useful product discovery workshop doesn't end with a wall of feature ideas. It helps product managers, designers, researchers, and engineers agree on the customer problem worth exploring, separate evidence from assumptions, and choose a concrete next research step.
You don't need a card deck to run this workshop. The exercises below are available in Learning Loop's public play library. If you regularly facilitate discovery sessions, the Discovery Patterns card deck combines product-discovery methods with tailored workshop exercises in a reusable format.
Take the workshop template into your next session
Use the printable worksheet to capture the desired outcome, customer evidence, opportunity map, prioritized assumptions, and a named next learning action. Print it or save it as a PDF. It complements the agendas and seven exercises below.
Open the free product discovery worksheet →What is a product discovery workshop, and when should you run one?
A product discovery workshop is a facilitated working session in which a product team makes sense of what it knows about customers, frames opportunities, surfaces uncertainty, and agrees how to learn next. It's not a substitute for interviews, usability tests or experimentation. The raw material should be observations from those activities, not only internal opinions.
Use a workshop when multiple people need a shared understanding to make a meaningful discovery decision: choosing which customer opportunity to investigate, resolving contradictory interpretations of research, identifying assumptions behind an initiative, or agreeing on a learning plan. If the team already agrees on the problem and a quick customer conversation could resolve the uncertainty, skip the workshop and speak with customers.
A discovery workshop is useful when…
- The team is jumping to feature ideas without understanding the problem.
- Customer evidence is scattered across functions.
- A desired outcome is clear, but opportunities are not.
- Stakeholders disagree because they are working from different assumptions.
- The team needs to commit to a focused next learning step.
Don't use a workshop to…
- Declare an untested product concept validated.
- Vote customer problems into existence.
- Replace conversations with the people affected.
- Get sign-off for a decision already made.
- Produce an impressive-looking map with no owner or follow-up.
In the continuous discovery tradition described by Teresa Torres, three principles matter more than any particular canvas: collaborative product-team decisions, externalized thinking, and a meaningful outcome. An opportunity solution tree is one useful tool for making these visible; it is not a compulsory ritual. Read the original Product Talk discussion.
What should a product discovery workshop produce?
A discovery workshop should turn research into useful decisions about what to learn next, not pressure the team into prematurely picking a solution. A good outcome includes:
- A target outcome: The user or product result the team hopes to improve, expressed in observable terms.
- Evidence-backed opportunities: Customer problems, needs or struggles supported by interviews, behavioral observations, support messages or other signals.
- Uncertainties: What the team believes but hasn't yet verified, especially important assumptions.
- A learning plan: Who will investigate which question, how, and by when.
The workshop won't establish product–market fit, validate a concept, or replace conversations with customers. It is a way to make existing evidence usable and to decide where discovery should go next.
One tree connects business outcomes, discovery and validation
Teresa Torres's Opportunity Solution Tree connects four levels: desired outcome → customer opportunities → possible solutions → assumption tests. The desired outcome expresses the business result the team seeks while creating customer value. Discovery investigates the customer needs, pains and desires that could help achieve that outcome; validation tests risky assumptions behind proposed solutions.
- Desired outcome — business perspective: choose an observable result, such as more newly registered customers successfully completing setup, rather than a feature to ship.
- Opportunities — discovery: identify and investigate what makes setup difficult for customers; do not mistake internal opinions for research evidence.
- Solutions: consider several possible ways to address a chosen opportunity, such as clearer permission explanations or a guided connection flow.
- Assumption tests — validation: evaluate the risky assumptions behind those options through appropriately chosen experiments before building broadly.
Illustrative example, not measured customer findings. Source: Teresa Torres, Product Talk — Opportunity Solution Trees. For facilitation, see Learning Loop's Opportunity Solution Tree Mapping play.
In this workshop, focus on the desired outcome and opportunity space. A clear business outcome helps focus research, but customer opportunities must be grounded in real observations. You can record provisional solutions or tests on the tree without treating them as validated. For the lower branches, continue with the validation workshop guide.
The thinking behind this approach
This guide reflects three complementary influences on Learning Loop's approach to product discovery: Teresa Torres and Continuous Discovery Habits emphasize frequent customer contact and connecting outcomes to opportunities; Marty Cagan and Inspired emphasize empowered cross-functional teams addressing customer and business problems; and Melissa Perri and Escaping the Build Trap emphasize outcomes over simply delivering features.
The agenda below is Learning Loop's practical synthesis of these ideas, not an official workshop format from any of those authors. A workshop is a checkpoint in a continuous learning process, not a substitute for regular discovery.
Choose the right format: 90 minutes, half a day, or a series
Choose the length based on the evidence available and the discovery decision. If you do not yet understand the customer problem, prioritize research before mapping.
| Format | Best when | Expected output |
|---|---|---|
| 90-minute synthesis | Customer research already exists and the decision is focused. | Candidate opportunities, a selected problem and a next learning step. |
| Half-day workshop | Multiple sources of evidence need synthesis and prioritization. | A more developed opportunity map and an agreed research plan. |
| Series of sessions | Evidence is sparse or opportunities need investigation over time. | New customer findings between sessions and an evolving opportunity map. |
No workshop replaces direct customer contact. Adapt or skip exercises when a short research activity will resolve the uncertainty faster.
Before the workshop: a practical preparation checklist
Good facilitation starts before people enter the room. The facilitator should be able to answer three questions: What decision are we trying to improve? What evidence do we have? What will happen differently after the session?
One week before
- Name one outcome. Choose an observable customer or business result, for example, “more newly activated accounts complete their first useful task”, rather than “ship a guided onboarding flow.” Confirm the scope and constraints with whoever is accountable for the product.
- Invite the smallest useful decision-making group. A product manager, designer and technical partner can form the core trio; involve research and relevant customer-facing expertise. Ask stakeholders to contribute context without making every participant a veto holder.
- Collect recent evidence. Assemble direct customer quotes with context, research findings, task observations, relevant product analytics, support patterns and existing experiments. Record dates, sources and limitations. Avoid turning a single anecdote into a trend.
- Pick one decision. Examples: Which opportunity deserves investigation? Which belief has the greatest risk? Which users should we talk with next? The narrower the decision, the more useful a short workshop becomes.
One or two days before
- Send a pre-read that fits on a page. Share the outcome, decision, existing evidence, open questions, agenda, participant roles and where to find the raw sources. Separate evidence, interpretation and proposals.
- Prepare the board. Create columns labeled Outcome, Observed evidence, Customer opportunities, Possible solutions, Assumptions and Next research. You won't necessarily use every column; it helps keep concepts distinct.
- Arrange facilitation. Designate one facilitator, one note-taker, a timekeeper if useful, and a decision owner. Test the whiteboard, accessibility and remote participation setup. For remote sessions, agree how quieter participants will contribute.
Copyable workshop brief
Outcome: [Observable result we want to influence]
Customer group: [Who experiences the problem]
Decision we need: [What we will choose today]
Known evidence: [Links to 3–5 useful observations]
Most important unknown: [The question we cannot yet answer]
Participants and roles: [Product, design, tech, facilitator, contributors]
Expected artifact: [Map, prioritized question, research plan]
Owner and review date: [Who follows through, when]
This is a Learning Loop facilitation template. Adapt it to the decision; don't fill in sections just because a template has space.
Who should participate and what to bring
Invite a cross-functional group that can interpret customer evidence and act on what the team learns: typically a product manager, a designer, a researcher where available, and an engineer. Include someone close to customer interactions, such as support or sales, when appropriate. A working group of roughly four to eight people is manageable, though exercise requirements vary.
Bring raw evidence, not just conclusions. Gather recent customer interview excerpts, observed behaviors, support themes, analytics and prior experiments. Separate direct observations from explanations or assumptions. An analytics drop-off may show where a problem occurs without establishing why.
Frame a narrow outcome. “Improve the product” is too broad. “Help new accounts complete their first meaningful task” is specific enough to explore but doesn't predetermine the feature to build.
Prepare a shared space. Use a whiteboard or virtual canvas with areas for the outcome, customer opportunities, possible solutions, evidence and unknowns. Assign a facilitator and a person to record decisions.
How to facilitate the workshop, step by step
Here's the reasoning behind the compact 90-minute agenda below. The goal is not to finish every play; it's to help a team choose a meaningful customer opportunity and make one better discovery decision.
The five steps below are a lightweight agenda, not a requirement to complete five full-length plays. Follow the linked exercises in the Workshop Patterns playbook when you need their full facilitation instructions.
Step 1: Frame the outcome and review evidence (25 min)
Agree on the desired customer outcome. Separate observations from interpretations and identify what is still unknown.
Step 2: Collect assumptions to uncover potential customer problems (15 min)
Use a short Assumptions Collection exercise to surface beliefs about customer needs, struggles and unmet goals. Treat them as candidate opportunities that need evidence, not prioritized risks about a solution. The linked play credits Giff Constable and David Bland (Precoil), with references to their approaches.
Step 3: Map customer opportunities (20 min)
Connect candidate needs and problems to the desired outcome, marking which are supported by research and which need customer conversations. Use Opportunity Solution Tree Mapping and, where useful, Journey Mapping.
Step 4: Prioritize the customer problem to focus on (15 min)
Compare the mapped problems and select one opportunity to investigate further. Opportunity Scoring prioritizes problems rather than appealing features. Use a brief comparison here and the full exercise when more depth is needed.
Step 5: Plan the next learning action (15 min)
Turn a key unknown about the chosen opportunity into a research question. Assign a customer interview, observation or other appropriate inquiry, with an owner and review date.
Example 90-minute product discovery workshop agenda
This is a time-boxed synthesis of several methods, not the complete version of each workshop exercise. The full linked plays require more time.
| Time | Activity | Output |
|---|---|---|
| 0 to 25 min | Define the outcome and review existing customer evidence. | Shared evidence notes and gaps. |
| 25 to 40 min | Use Assumptions Collection to uncover possible customer needs and problems. | Candidate opportunities labeled as hypotheses. |
| 40 to 60 min | Sketch a provisional opportunity map. | Customer opportunities with supporting evidence. |
| 60 to 75 min | Use a brief Opportunity Scoring comparison to choose a problem worth pursuing. | One selected opportunity and its rationale. |
| 75 to 90 min | Decide the next research action, owner, and review date. | Concrete learning plan. |
Alternative agenda: a half-day deep dive
Use this when the team has a substantial body of customer evidence but needs enough shared time to synthesize it. A half-day session gives more room for mapping; it still cannot replace the customer research that supplies the evidence.
| Time | Working session | Deliverable |
|---|---|---|
| 0–20 min | Outcome, scope, team roles, working agreements | Shared decision frame |
| 20–55 min | Evidence gallery: customer quotes, observations, analytics and disagreements | Evidence clustered by customer struggle |
| 55–75 min | Collect assumptions to surface potential customer needs and problems | Candidate opportunities and questions |
| 75–110 min | Map needs and opportunities against evidence | Provisional opportunity map |
| 110–125 min | Break | , |
| 125–170 min | Compare and prioritize mapped customer opportunities, then deepen the most promising problem | Chosen focus opportunity with rationale and evidence gaps |
| 170–205 min | Identify open research questions about the chosen opportunity | Opportunity-specific assumptions and research questions |
| 205–235 min | Research planning, owners, recruitment, review date | Next learning plan |
| 235–240 min | Readback and commitments | Agreed next steps |
Don't stack full-length exercises on top of one another without accounting for their real durations. If the team needs a complete journey map and a complete opportunity solution tree, split them across sessions with customer research between them.
Choose the discovery exercise that fits your challenge
Product discovery is ongoing. You don't have to run every exercise in one workshop. Choose the smallest activity that helps your team make sense of customer evidence, find an opportunity or decide what to learn next. These seven plays come from the Workshop Patterns playbook. Collect assumptions about possible customer problems first, then map the opportunities and choose which one to investigate. Open each play for its complete instructions. You can skip steps when you already have the evidence you need.
Assumptions Collection
Surface possible customer needs and problems at the start of discovery. Inspired by Giff Constable and David Bland (Precoil).
Full play: 45–60 min
Journey Mapping
Map the customer experience and locate moments of friction or unmet needs.
Full play: 1–4 hours
Opportunity Solution Tree Mapping
Connect a desired outcome to research-backed customer opportunities and possible solutions.
Full play: 60–90 min
Opportunity Scoring
Compare customer problems on the opportunity map and decide which opportunity deserves focused discovery next, rather than prioritizing solutions.
Full play: 1–2 hours
Assumptions Mapping
Prioritize important assumptions according to how much supporting evidence exists.
Full play: 45 min
Value Proposition Mapping
Explore the value customers might gain and the needs a proposed solution should address.
Full play: 60–90 min
User Story Mapping
Visualize the end-to-end experience and align on potential solution scope once the opportunity is understood.
Full play: 60–90 min
Keep problem discovery and solution planning distinct. Assumptions Collection first surfaces candidate customer problems. Journey Mapping and Opportunity Solution Tree Mapping organize and examine them in light of customer evidence. Opportunity Scoring helps the team choose which problem to investigate next. Assumptions Mapping is an optional later exercise for working through important uncertainties. Value Proposition Mapping and User Story Mapping become especially helpful when exploring and aligning on possible solutions; neither should be treated as evidence that a solution is right.
Time-boxing matters: Several complete plays run 45–90 minutes or longer on their own. The 90-minute agenda above uses lightweight excerpts of opportunity mapping, opportunity selection and assumptions work, not all seven complete exercises. For detailed mapping, allow a dedicated follow-up session.
What to leave with: examples of workshop artifacts
At the end, the team should have visible artifacts that somebody can use tomorrow. They don't need to be beautiful; they need to distinguish what is known from what is believed.
1. A provisional opportunity map
Outcome: More new users complete their first useful project.
Opportunity A: People are unclear about the next step.
Opportunity B: People lack information needed to proceed.
Attach source notes or mark each opportunity “needs more evidence.” These examples are fictional.
2. An evidence / assumption log
Observed: Users hesitate at the setup screen in recorded usability sessions.
Assumed: Shortening setup would increase meaningful task completion.
Unknown: Whether hesitation is caused by comprehension, missing information or lack of motivation.
3. One focused research question
“At what point do first-time users lose confidence about their next action, and what information do they expect to see?”
Better than “Do users like our proposed onboarding wizard?” because it doesn't presuppose the answer.
4. A next-action record
Method: Observe first-time users completing a realistic setup task.
Owner: Product trio assigns a lead.
Next review: After the scheduled sessions.
Specify participant criteria, date and evidence needed in the real plan.
Worked example: discover why onboarding stalls
Starting question: “Why do new users stop before completing their first project?” The team suspects onboarding has too many steps, but has not confirmed the cause.
- Define the outcome. Help a greater share of new users complete their first meaningful project, without forcing completion through misleading prompts.
- Review evidence. Analytics identifies the step where many people leave. Interview notes show that some users are unsure what to do next; others lack the information required to proceed.
- Map opportunities. The team separates “understand the next action” from “have the required information.” These are distinct customer struggles even though both appear as drop-off.
- Identify assumptions. The team realizes it doesn't know which struggle is most common or most consequential.
- Choose the next action. Observe several first-time users attempting the flow and gather evidence about what blocks progress before redesigning it.
Illustrative scenario only. The observations and outcome are examples, not results from a named Learning Loop customer.
This is where Discovery Patterns can be helpful: it gives the team a shared reference for selecting research approaches and practical workshop exercises such as opportunity mapping. If the team later needs to compare experimental ways of checking a solution assumption, Validation Patterns is the more relevant deck.
Common failure modes, and what to do instead
| What goes wrong | Better facilitator response |
|---|---|
| Everyone starts proposing features. | Ask what customer need each feature addresses; move premature proposals to a separate parking area. |
| The loudest stakeholder defines the problem. | Use silent writing first and annotate each claim with customer evidence, interpretation or unknown. |
| The team spends the session debating the perfect tree. | Make a rough working map, pick one promising branch, and improve it with new evidence. |
| Analytics are presented as an explanation. | Clarify that behavioral data identifies patterns, not necessarily underlying motives; choose a follow-up method. |
| People vote on opportunities without evidence. | Separate the importance of an opportunity from confidence that it actually exists. |
| The workshop ends without action. | Reserve time for a named owner, research question, method, deadline and review. |
| A workshop is mistaken for continuous discovery. | Schedule a recurring evidence review and direct customer contact, not another ceremonial kickoff. |
Adapt the agenda when new evidence changes the question. As Boldare's workshop guidance also emphasizes, the appropriate techniques depend on the purpose and the agenda can change as teams learn. A facilitator should protect the outcome, not rigidly enforce an exercise sequence.
After the workshop: turn maps into ongoing learning
An opportunity map is a provisional interpretation of current evidence, not proof that a need exists. The workshop matters when it changes what the team investigates and how it decides.
- Within 24 hours: Share the draft opportunity map, source evidence, open assumptions, decision log, and owner of the next research activity.
- Within the next week: Interview or observe customers to challenge the highest-priority unknown. Establish a customer-contact cadence the team can sustain.
- At the next product-trio check-in: Compare observations with assumptions, revise the map, and decide whether to investigate the opportunity further or explore possible solutions.
- When a solution is proposed: Move to validation workshop planning to identify the riskiest solution assumption and choose an appropriate test.
Three traps to avoid: presenting stakeholder opinions as customer facts, choosing a feature before clarifying the opportunity, and describing an untested opportunity map as “validated.” Teresa Torres's SuperAwesome case study and Doodle case study show how organizations can adapt continuous discovery practices; they are examples, not a prescribed workshop recipe.
Frequently asked questions
Who should attend a product discovery workshop?
Bring the people responsible for understanding customers and making product decisions: often product, design, research, and engineering, plus a customer-facing colleague where useful. A small cross-functional group is usually easier to facilitate than a very large one.
What is the difference between a discovery workshop and a brainstorming workshop?
Discovery starts from the customer problem and available evidence. Brainstorming primarily generates ideas. Product discovery can include ideation, but ideas should connect to observable opportunities and assumptions to test.
Can we finish Opportunity Solution Tree Mapping in 90 minutes?
A full mapping session may take 60–90 minutes by itself. Use the short agenda for an initial sketch, or dedicate a longer session to building and reviewing a research-grounded tree.
Do we need Discovery Patterns cards?
No. You can follow the publicly available plays with sticky notes or a digital board. The cards are a reusable toolkit for teams that want a collection of relevant methods and purpose-built exercises close at hand.
Recommended reading and influences
Learning Loop's facilitation approach synthesizes principles from several sources; the agenda and examples on this page are our own teaching interpretation, not a workshop prescribed or endorsed by these authors.
- Teresa Torres and Hope Gurion: Why There’s No Single “Right” Way to Do Discovery, collaborative decision-making, externalized thinking and outcomes.
- Product Talk: Opportunity Solution Trees at SuperAwesome, adoption and adaptation in a real organization.
- Product Talk: Moving from a Feature Factory to Continuous Discovery at Doodle, organizational practice and the move toward outcomes.
- Inspired, Marty Cagan, empowered cross-functional product teams.
- Escaping the Build Trap, Melissa Perri, product value and outcomes rather than feature output.
- airfocus: How to Run a Product Discovery Workshop, another useful perspective on agenda and preparation.
- Maze: Continuous Product Discovery, routines for ongoing customer learning.
Next step: Once discovery produces a plausible solution, use the validation workshop guide to design a test of its riskiest assumption.