How is product discovery done?

# How is product discovery done? Product discovery is the process of understanding customers' problems, identifying opportunities, and validating which solutions are worth building before investing significant time and money in development. The goal is to build the right product, for the right users, solving the right problem. Product discovery is an ongoing process, not a one-time activity. It usually happens before and alongside product development. ## 1. The product discovery process Step 1: Understand the customer Research your target users and understand: - Who are they? - What problems do they face? - What are their needs and frustrations? - How do they currently solve these problems? Step 2: Identify problems and opportunities Analyze research findings to identify: - Common customer pain points. - Unmet needs. - Market gaps. - Opportunities to improve existing experiences. Step 3: Generate and prioritize ideas Brainstorm potential solutions and prioritize them based on: - Customer value. - Business impact. - Technical feasibility. - Strategic alignment. Step 4: Create prototypes Build low-cost representations of possible solutions, such as: - Wireframes. - Clickable prototypes. - Mockups. - Landing pages. Step 5: Test and validate Put prototypes in front of customers and evaluate: - Do users understand the solution? - Does it solve their problem? - Would they use it? - Would they pay for it, if relevant? Step 6: Make a decision Decide whether to: - Build the solution. - Improve and test it again. - Explore another solution. - Stop pursuing the idea. ## 2. Techniques used in product discovery | Technique | Purpose | | --- | --- | | Customer interviews | Understand customer problems | | Surveys | Collect feedback from many users | | Competitor analysis | Understand market offerings and gaps | | User observation | See how customers behave | | Data analytics | Identify usage patterns and friction | | Personas | Understand target customer segments | | Journey mapping | Identify pain points across experiences | | Prototyping | Explore possible solutions | | Usability testing | Validate ease of use | | A/B testing | Compare alternative experiences | ## 3. Example: Product discovery for a food delivery app Imagine you're a Product Manager at a food delivery company. Business objective: Increase customer retention. Here's how discovery works: | Stage | Example | | --- | --- | | Research | Interview customers who stopped ordering | | Problem identified | Delivery takes too long | | Opportunity | Customers want more predictable delivery | | Ideas | Live tracking, accurate ETA, delivery notifications | | Prototype | Create a clickable live-tracking screen | | Validation | Test with 10–15 customers | | Decision | Improve ETA accuracy and test again | | Delivery | Build and release the validated solution | | Measurement | Track repeat orders and retention | The important thing is that you don't immediately start building live tracking just because someone suggested it. First, you investigate whether it actually addresses the customer problem. ## 4. Who is involved in product discovery? A typical product discovery team includes: - Product Manager: Defines business outcomes and prioritizes opportunities. - UX/UI Designer: Understands user needs and designs prototypes. - Engineering Lead: Evaluates technical feasibility. - User Researcher: Conducts research and synthesizes findings. - Business Stakeholders: Provide business strategy and context. - Customers: Share their needs, experiences and feedback. A common approach is the Product Trio: Product Manager, Designer and Engineer working together on discovery. [In The Loop Conversations: Making Better Product Decisions with Teresa Torres](https://maze.co/blog/making-better-product-decisions-with-teresa-torres/)[Getting to a team-based approach to continuous discovery by Teresa Torres](https://www.mindtheproduct.com/getting-to-a-team-based-approach-to-continuous-discovery-by-teresa-torres/) ## 5. Product discovery vs. product delivery This is an important distinction in product management interviews. | Product Discovery | Product Delivery | | --- | --- | | What should we build? | How do we build it? | | Understand customer problems | Develop the solution | | Validate ideas | Implement features | | Test prototypes | Test production software | | Reduce product risk | Ensure quality and reliability | | Focus on outcomes | Focus on execution | ## 6. A popular product discovery framework One widely used framework is the Opportunity Solution Tree (OST) by Teresa Torres. It connects four elements: 1. Outcome: What business or customer result do we want? 2. Opportunities: What customer needs or pain points can help achieve it? 3. Solutions: What potential solutions address those opportunities? 4. Experiments: How can we test our assumptions before building? Teams can use this framework alongside continuous customer interviews and experiments. [In The Loop Conversations: Making Better Product Decisions with Teresa Torres](https://maze.co/blog/making-better-product-decisions-with-teresa-torres/)[Creating value with continuous discovery - a discussion with Teresa Torres (Part 1)](https://www.productboard.com/blog/creating-value-with-continuous-discovery-a-discussion-with-teresa-torres-part-1/) ## 7. How to explain product discovery in a Product Manager interview A good interview answer would be: "Product discovery is an ongoing process of understanding customer needs, identifying problems, exploring potential solutions, and validating assumptions before committing engineering resources. As a Product Manager, I start by understanding the business objectives and customer segments. I conduct customer interviews, analyze product data, and identify pain points. I then prioritize opportunities, collaborate with design and engineering to explore solutions, create prototypes, and conduct usability tests or experiments. Based on the findings, I decide whether to proceed with development, iterate on the solution, or explore another opportunity. The ultimate goal is to reduce product risk and ensure that we're building something customers actually need and that delivers business value." My recommendation: Understand product discovery as three fundamental questions: - Are we solving the right problem? - Are we building the right solution? - Will the solution create value for customers and the business? If you understand these three questions, you understand the foundation of product discovery.

**Product discovery is the structured process of identifying, validating, and refining product ideas to ensure they solve real customer problems, are feasible to build, and align with business goals.** It’s essentially about answering the question: *“Should we build this at all?”* before investing heavily in development.([Product discovery | Atlassian][1])([Product Discovery: Definition, Process, and Techniques (2025) - Shopify][2])([Product Discovery Process: Steps, Costs and Deliverables][3])([Product Discovery Guide: Methods & Frameworks (2026)][4]) --- ## 🔑 Key Steps in Product Discovery 1. **Define the Problem & Vision** - Start with a clear product vision and articulate the customer problem. - Example: Write a one-paragraph statement describing the user pain point.([Product Discovery Process: Steps, Costs and Deliverables][3]) 2. **Research & Understand Customers** - Use **user interviews, surveys, and behavioral data** to uncover needs. - Apply frameworks like *Jobs-to-be-Done (JTBD)* or *opportunity solution trees*.([Product Discovery Guide: Methods & Frameworks (2026)][4]) 3. **Generate & Prioritize Ideas** - Brainstorm solutions, then filter them using criteria: - **Value** (Will customers buy/use it?) - **Usability** (Can they figure it out?) - **Feasibility** (Can the team build it?) - **Strategic fit** (Does it align with business goals?)([Product discovery | Atlassian][1]) 4. **Prototype & Test** - Build low-fidelity prototypes or mockups. - Run usability tests and gather feedback before committing resources.([Product Discovery Guide: Methods & Frameworks (2026)][4]) 5. **Validate Assumptions** - Map assumptions (about customer behavior, technical feasibility, market demand). - Conduct lean experiments to confirm or reject them.([Product Discovery Process: Steps, Costs and Deliverables][3]) 6. **Synthesize & Align** - Share findings across teams (PMs, designers, engineers). - Update product roadmap based on validated insights.([Product Discovery: Definition, Process, and Techniques (2025) - Shopify][2]) --- ## ⚙️ Common Frameworks | Framework | Focus | Best For | |-----------|-------|----------| | **Double Diamond** | Diverge → Converge on problems & solutions | Broad innovation projects([Product Discovery Process: Steps, Costs and Deliverables][3]) | | **Lean UX Canvas** | Hypothesis-driven design | Digital products with fast iteration([Product Discovery Process: Steps, Costs and Deliverables][3]) | | **Opportunity Solution Tree** | Mapping customer problems to solutions | Continuous discovery([Product Discovery Guide: Methods & Frameworks (2026)][4]) | | **JTBD (Jobs-to-be-Done)** | Understanding customer motivations | Products solving functional/emotional needs([Product Discovery Guide: Methods & Frameworks (2026)][4]) | --- ## 🚨 Challenges & Risks - **Skipping discovery** → Building the wrong product beautifully but uselessly. - **Internal bias** → Teams rely on assumptions instead of validated customer needs. - **Treating discovery as a one-time phase** → Leads to stale insights; modern teams practice *continuous discovery* alongside delivery.([Product Discovery Guide: Methods & Frameworks (2026)][4]) --- ## 📌 Takeaway Product discovery is not just research - it’s a **continuous habit** that reduces wasted effort, sharpens value propositions, and ensures alignment between customer needs and business strategy. Teams that invest in discovery consistently ship fewer but more successful features.([Product Discovery Guide: Methods & Frameworks (2026)][4]) Would you like me to break this down into a **practical checklist** you could apply directly in your own projects? [1]: https://www.atlassian.com/agile/product-management/discovery "Product discovery | Atlassian" [2]: https://www.shopify.com/blog/product-discovery "Product Discovery: Definition, Process, and Techniques (2025) - Shopify" [3]: https://lanpdt.com/product-discovery-process/ "Product Discovery Process: Steps, Costs and Deliverables" [4]: https://www.ideaplan.io/guides/product-discovery-guide "Product Discovery Guide: Methods & Frameworks (2026)"

Product discovery is the critical phase in product management and design where teams figure out **what** they should build and **why**. Before writing a single line of code, product discovery bridges the gap between user needs and business goals to ensure teams are building the _right_ thing. Industry frameworks (popularized by leaders like Teresa Torres) break product discovery down into a continuous, structured loop. Here is how it is typically done in practice: ### 1\. Define Outcomes (The Business Goal) Product discovery never starts with a feature idea; it starts with a desired business or customer outcome. * **Example Outcome:** "Reduce user churn during onboarding by 15% this quarter" or "Increase the frequency of daily active users." * **Why it matters:** It gives the team a clear north star, allowing flexibility in _how_ they achieve the goal rather than prescribing a pre-determined solution. ### 2\. Map Customer Needs & Pain Points To understand how to reach the outcome, teams explore the lives, behaviors, and frustrations of their target users. This is where qualitative and quantitative research happen: * **User Interviews & Observation:** Talking directly to users, watching them interact with current products, and uncovering hidden workarounds. * **Data & Analytics:** Looking at drop-off points, funnel analytics, and feature adoption rates to see where friction lies. * **Customer Feedback:** Reviewing support tickets, sales calls, and app store reviews. ### 3\. Build an Opportunity Solution Tree (OST) A popular framework in modern product discovery is Teresa Torres's **Opportunity Solution Tree**. It visually connects: * **Desired Outcome** at the top. * **Opportunities** (user needs, pain points, or desires) branching out below. * **Solutions** (ways to address those opportunities) branching further down. * **Experiments** (tests to validate solutions) at the bottom. This keeps teams from jumping straight to their first idea and ensures every solution is tied to a real user need. ### 4\. Ideation and Brainstorming Once high-priority customer pain points (opportunities) are identified, cross-functional teams (Product Managers, Designers, and Engineers) brainstorm multiple potential solutions. The goal here is divergence - generating a variety of approaches, from low-effort quick wins to innovative redesigns. ### 5\. Prototyping and Experimentation Instead of building fully coded features, teams test assumptions quickly and cheaply using prototypes and experiments: * **Low-Fidelity Prototypes:** Wireframes, sketches, or clickable Figma mockups shown to users during testing sessions. * **Concierge or Wizard of Oz Tests:** Manually performing the service behind the scenes to see if users value the concept before automating it. * **Smoke Tests:** Landing pages, fake door buttons, or feature teasers to gauge true user interest or demand. ### 6\. Continuous Evaluation & Decision Making Discovery isn't a one-time event done at the beginning of a year; it runs continuously alongside delivery (building). Throughout testing, teams evaluate: * **Value Risk:** Do customers actually want this? Will they use it? * **Usability Risk:** Can users figure out how to use it? * **Feasibility Risk:** Can our engineering team build it within reasonable constraints? * **Viability Risk:** Does this align with our business model and legal/ethical standards? Once a solution passes these validation gates, it moves into **product delivery** (coding, QA, and release), while the discovery loop immediately pivots to the next opportunity.

Product discovery is the ongoing process of figuring out **what to build** and **whether it should be built** by deeply understanding customer needs and business goals before committing to heavy development. Here is how product discovery is typically structured and executed: * Continuous Process: It isn't a single phase or a kickoff meeting that ends; it runs parallel to delivery, constantly feeding validated ideas into the development pipeline. * Core Objective: De-risk product decisions by minimizing the gap between what you _think_ users want and what they _actually_ need or will pay for. 1\. The Core Framework of Discovery A popular mental model for product discovery (popularized by product coach Teresa Torres) involves mapping out opportunities and solutions visually: * Outcome: Defining the specific business metric or user behavior you want to move (e.g., increasing onboarding completion by 15%). * Opportunity Space: Discovering the user needs, pain points, or desires that block or drive that outcome, usually gathered through user research. * Solution Space: Brainstorming multiple ways to address those top opportunities rather than falling in love with the first idea. 2\. Key Steps in the Discovery Process * **Empathize & Research:** Talk directly to users. Conduct user interviews, observe behaviors, analyze support tickets, and review usage data to uncover hidden friction points. * **Define the Problem:** Frame the specific pain point clearly from the user’s perspective. A well-defined problem statement ensures the team doesn't build solutions in search of a problem. * **Ideate Solutions:** Brainstorm a wide range of potential approaches. At this stage, quantity and creativity matter more than immediate technical feasibility. * **Test & Validate (De-risk):** Run fast, low-cost experiments before writing code. This includes: * Prototype testing (clickable wireframes via tools like [Figma](https://www.figma.com)). * Concept testing or smoke tests (landing page sign-ups, fake-door tests). * Data analysis of existing behavioral metrics. * **Iterate or Kill:** Based on validation results, refine the solution, pivot to a different approach, or drop the idea entirely if it fails to show user value or business viability. 3\. Key Cross-Functional Roles Involved * Product Manager (PM): Facilitates the process, aligns stakeholders, and ensures business viability. * Product Designer (UX/UI): Translates user insights into intuitive concepts and prototypes. * Software Engineers / Tech Leads: Brought in early to assess technical feasibility and cost, ensuring ideas are realistically buildable. * User Research / Data Analytics: Helps gather and interpret quantitative and qualitative feedback. Would you like to dive deeper into a specific part of this, such as: How to conduct **user interviews** Methods for **rapid prototyping and testing** Balancing **discovery vs. delivery** in agile sprints

Product discovery is a continuous process for finding the right customer problem to solve and testing whether a solution is valuable before investing in building it. A typical flow is to set a desired outcome, research users and identify their needs, prioritize the most important opportunity, generate possible solutions, then test assumptions with prototypes or experiments and refine based on feedback.([usersnap.com][1])([scrum.org][2]) [1]: https://usersnap.com/glossary/product-discovery "What Is Product Discovery? Stages, Methods and Frameworks" [2]: https://www.scrum.org/resources/blog/what-product-discovery "What Is Product Discovery? | Scrum.org"