Product Discovery Workflow Templates for Product Managers
Product discovery is the ongoing work of understanding which problems are worth solving before committing engineering capacity to build solutions. PMs use these workflows to maintain a continuous cadence of customer insight that feeds directly into the product backlog.
Customer Interview Script
Run a 45-minute structured customer interview that surfaces real problems without leading the interviewee toward your solution.
Steps
- 1Send a one-sentence context email 24 hours before: "We're talking to customers about [job/outcome] — no product feedback session, just learning."
- 2Open 5 minutes: introduce the trio (PM, designer, engineer), explain the format and that there are no wrong answers.
- 3Warm-up 5 minutes: ask about their role, the team they work in, and how they currently handle [problem area].
- 4Core 25 minutes: use the five key questions — (1) Walk me through the last time you did X. (2) What was the hardest part? (3) What did you try? (4) What happened? (5) How did that affect you?
- 5Probe for specifics: "Can you show me?" and "What did you do next?" are your best follow-up prompts.
- 6Opportunity mapping 5 minutes: "If you could wave a magic wand and change one thing about [process], what would it be?"
- 7Close: thank them, confirm follow-up consent, and add insights to the opportunity solution tree within 24 hours.
Opportunity Solution Tree Build
Translate a quarter's worth of customer interview insights into a structured opportunity solution tree to guide discovery priorities.
Steps
- 1Start with the desired outcome at the top — one measurable metric the team is trying to move this quarter.
- 2List all unique customer problems and desires surfaced in interviews over the past 4–6 weeks as opportunity nodes.
- 3Group related opportunities under parent opportunities; aim for no more than 3 levels deep.
- 4For the top 3–5 opportunities by vote or frequency, generate 3+ candidate solutions per opportunity.
- 5For each candidate solution, write down the riskiest assumption underlying it.
- 6Design the cheapest test that would validate the riskiest assumption before any sprint work begins.
- 7Review the OST with the product trio weekly; add new opportunities from each interview session.
Problem Framing Workshop
Align a cross-functional team on the correct problem statement before anyone jumps to solutions.
Steps
- 1Distribute 3 customer interview highlights to all attendees 48 hours before the workshop.
- 2Open with a 10-minute "how might we fail?" exercise — ask the group to list every reason the problem might not be real or not be worth solving.
- 3Present the problem hypothesis: "We believe [user segment] struggles with [problem] because [root cause], which results in [impact]."
- 4Spend 20 minutes generating evidence for and against the hypothesis in two columns.
- 5Vote on confidence level: how confident is the group that the problem is real, frequent, and worth solving?
- 6If confidence is below 70%, identify the single most important assumption to validate first before the next workshop.
- 7Close with a one-sentence agreed problem statement that will anchor the next discovery sprint.
Assumption Testing Sprint
Run a focused 1-week assumption test to validate or invalidate the riskiest hypothesis before committing to a full build.
Steps
- 1Write the assumption clearly: "We believe [user] will [do X] when [condition Y] is present."
- 2Define success: what result would cause you to proceed with confidence? What result would cause you to pivot?
- 3Choose the cheapest test method: fake door button, concierge MVP, landing page, or 5 prototype interviews.
- 4Build the test artefact — time-box the build to no more than 2 days of engineering or design effort.
- 5Run the test with a minimum of 20 users (quantitative) or 5 interviews (qualitative).
- 6Record raw results without interpretation first; then analyse with the product trio.
- 7Document the outcome in the assumption log and update the OST to reflect what you learned.
Weekly Discovery Sync
Run a 30-minute weekly product trio sync to review interview insights, update the opportunity tree, and align on next week's discovery priorities.
Steps
- 1Each trio member shares the top 2 insights from customer contact in the past week (interviews, support tickets, sales calls).
- 2PM updates the opportunity solution tree with new or updated opportunities based on the insights.
- 3Trio votes on the top 3 opportunities to focus on this week.
- 4Assign the next customer interview — confirm who will run it, who will observe, and who will take notes.
- 5Review any open assumption tests — what results have come in? What decisions do they unlock?
- 6Check alignment with the quarterly desired outcome — are we still working toward the right metric?
Jobs-to-Be-Done Interview Template
Uncover the functional, social, and emotional jobs customers hire your product to do, using the switch interview technique.
Steps
- 1Recruit a participant who recently adopted your product or switched from a competitor.
- 2Open with the switch moment: "Walk me through the day you decided to [buy / switch to] [product]. Where were you? What happened that day?"
- 3Explore the first thought: "What made you start thinking you needed a solution?"
- 4Explore the passive and active looking stages: "How did you look for options? What did you consider?"
- 5Identify the job: "What were you ultimately trying to get done that made you pull the trigger?"
- 6Explore struggling moments: "What was going on in your work or life that made this feel urgent?"
- 7Identify the functional, emotional, and social dimensions of the job using the three lenses of JTBD.
Which tool should you use for product discovery?
Here are three tools that work well for these workflows, and what makes each one a good fit.
Best for maintaining a centralised discovery repository: interview notes, OST, assumption logs, and research databases in one place.
Visual workspace for OSTs, affinity mapping, and collaborative problem framing workshops. Excellent for remote discovery teams.
Purpose-built idea and discovery management with idea boards, feedback capture, and direct links from discoveries to roadmap items.
Frequently Asked Questions
Teresa Torres recommends at least one interview per week with the full product trio. In practice, two per week is better for teams with low existing customer contact. The frequency matters more than the volume — a steady weekly cadence beats a burst of 20 interviews once a quarter because insights stay current.
User research is typically a project-based activity run by a research specialist, producing a deliverable (report, insight deck). Product discovery is a continuous team practice — the PM, designer, and engineer maintain direct customer contact as a habit, not an event. Discovery informs daily prioritisation decisions; research informs major strategic ones.
Use open-ended, past-behaviour questions rather than hypothetical or opinion questions. "Walk me through the last time you..." surfaces real experiences. "Would you use a feature that..." invites people to say what they think you want to hear. Record sessions and review them as a trio so different people catch different signals. Never start an interview by describing your solution.