How is product discovery done?

# How is product discovery done? Product discovery is the process of figuring out what to build, for whom, and why - before investing heavily in building it. The goal is to make sure a product solves a real customer problem, creates meaningful value, and can work for the business. Instead of immediately jumping into features and development, product teams investigate customer needs, test assumptions, and validate potential solutions. Product discovery is usually an ongoing activity, not a one-time phase that ends when development begins. ## The product discovery process ### 1. Identify the problem Define the customer segment, the problem they experience, and why it matters. - Review customer feedback, support tickets, product analytics, and business goals. - Identify pain points and unmet needs. - Write a clear problem statement. Example: Small-business owners struggle to understand their monthly cash flow. ### 2. Understand customers Research how people currently handle the problem and what they actually need. - Conduct customer interviews and contextual observations. - Analyze user behavior and existing solutions. - Look for recurring patterns rather than relying on isolated opinions. Key question: What are customers trying to accomplish, and what is stopping them? ### 3. Generate and prioritize opportunities Turn customer problems into opportunities for improvement. - Identify possible solutions or unmet needs. - Estimate customer value, business impact, and strategic alignment. - Prioritize opportunities based on evidence, not just stakeholder opinions. Key question: Which problem is most worth solving? ### 4. Form hypotheses and test solutions Develop possible solutions and test the riskiest assumptions before committing to full development. - Sketch concepts or create prototypes. - Run usability tests with target users. - Test demand with landing pages, experiments, or concierge MVPs where appropriate. Key question: Will customers find this useful, usable, and valuable enough? ### 5. Decide what to build Use the evidence to decide whether to proceed, refine the idea, or stop. - Define the intended outcome and success metrics. - Agree on the smallest useful solution. - Document requirements and collaborate with design and engineering. Output: A validated problem, a tested solution direction, and a clear next step. ### 6. Learn from real-world usage After launch, evaluate whether the solution delivers the intended outcome. - Track adoption, engagement, retention, conversion, or task completion. - Gather customer feedback. - Feed new insights into the next discovery cycle. ## Example: Product discovery for a food delivery app Suppose customers complain that food delivery is too expensive. Problem discovery Interview customers to understand why they abandon orders. Research reveals that unexpected delivery fees are a major frustration. Opportunity identification Customers want to know the full cost before checkout and find affordable delivery options. Solution testing Test an upfront total-price display and a low-cost delivery filter using a prototype. Evidence-based decision Observe whether customers understand pricing more easily and whether checkout completion improves. Refine the solution based on the results. Notice that the team didn't immediately build a discount feature. It first investigated the underlying problem and then tested potential solutions. ## What techniques do product managers use? | Technique | What it helps discover | | --- | --- | | Customer interviews | Customer needs, motivations, and pain points | | Surveys | Patterns across a larger customer group | | Product analytics | Where users drop off or struggle | | Competitor research | Existing alternatives and market gaps | | Usability testing | Whether people can use a proposed solution | | Prototypes | Whether a solution concept makes sense | | A/B testing | Which of two live alternatives performs better | | Opportunity solution trees | How customer opportunities connect to possible solutions and experiments | These techniques are selected based on the question the team needs to answer; not every discovery effort needs all of them. [Product discovery](https://www.atlassian.com/agile/product-management/discovery)[3 Best Practices for Adopting Continuous Product Discovery](https://www.producttalk.org/adopting-continuous-product-discovery/) ## How do you know whether discovery is successful? Product discovery should help a team answer four essential questions: - Desirability: Do customers actually want or need this? - Usability: Can they understand and use it? - Feasibility: Can the team build and maintain it? - Viability: Does it make business sense and support the product strategy? These are the four dimensions commonly used to evaluate a product idea before committing to it. [Product discovery](https://www.atlassian.com/agile/product-management/discovery) ## Who is involved? Product discovery is a collaborative effort: - Product manager: Frames the problem, prioritizes opportunities, and makes product decisions. - Product designer / UX researcher: Conducts research, explores concepts, and tests usability. - Engineers: Assess technical feasibility and help explore solution options. - Data analysts: Analyze user behavior and measure experiments. - Customers and stakeholders: Provide evidence, context, and feedback. The team should collaborate throughout discovery rather than having the product manager investigate everything alone. [Product discovery](https://www.atlassian.com/agile/product-management/discovery)[How to use Jira Product Discovery | Official guide](https://www.atlassian.com/software/jira/product-discovery/guides/getting-started/introduction) ## Product discovery vs. product delivery | Product discovery | Product delivery | | --- | --- | | Decide what is worth building | Build and ship the solution | | Understand problems and opportunities | Implement requirements | | Test assumptions and prototypes | Develop, test, and release software | | Reduce the risk of building the wrong thing | Ensure the solution works reliably | The two activities overlap in practice. Product discovery continues as the team builds, launches, and learns from customers. [3 Best Practices for Adopting Continuous Product Discovery](https://www.producttalk.org/adopting-continuous-product-discovery/)[How Can Product Leaders Support Continuous Discovery?](https://www.producttalk.org/how-leaders-support-continuous-discovery/) The key takeaway: Product discovery is about reducing uncertainty before making significant product investments. Great teams don't just ask, "Can we build this feature?" They ask, "Is this the right problem to solve, and what evidence tells us our solution will work?"

**Product discovery is the structured process of figuring out **_**what to build and why**_** before committing engineering resources. It reduces the risk of building the wrong thing by validating user needs, testing assumptions, and aligning solutions with business goals.** ## 🔑 Core Principles of Product Discovery * **Ask “Should we build this?” before “How do we build this?”** * **Talk to real users** through interviews, surveys, and contextual inquiry. * **Test assumptions cheaply** with prototypes, experiments, or A/B tests. * **Measure behavior, not opinions** - focus on evidence, not guesses. * **Run discovery continuously**, not as a one-time phase.[Product Discovery Guide: Methods & Frameworks (2026)](https://www.ideaplan.io/guides/product-discovery-guide)[Complete Guide to Product Discovery: Methods, Frameworks,](https://www.ideaplan.io/guides/the-complete-guide-to-product-discovery) ## 🛠️ Typical Product Discovery Process Step| What Happens| Why It Matters ---|---|--- 1\. Frame the Discovery| Define scope, goals, and desired outcomes| Prevents vague exploration 2\. Understand Users| Interviews, surveys, journey mapping| Reveals real problems 3\. Define the Problem| Clarify pain points and opportunities| Ensures focus on value 4\. Map Assumptions| Identify risks and uncertainties| Surfaces what could invalidate the idea 5\. Explore Solutions| Brainstorm multiple options| Avoids tunnel vision 6\. Prototype & Test| Build lightweight prototypes| Validates riskiest assumptions quickly 7\. Assess Feasibility| Check technical and business viability| Ensures sustainability 8\. Decide & Prepare| Proceed, pivot, or stop| Saves time and money[Product Discovery Process: 8 Steps, Frameworks & Deliverables](https://www.zfort.com/blog/product-discovery-guide)[Product Discovery Techniques: Methods, Frameworks, and Tools](https://heymarvin.com/resources/product-discovery-techniques) ## 📊 Methods & Techniques * **Qualitative methods**: user interviews, contextual inquiry, usability testing. * **Quantitative methods**: surveys, analytics, A/B testing. * **Frameworks** : * _Opportunity Solution Trees_ (map problems to solutions) * _Assumption Mapping_ (identify and test risky beliefs) * _Continuous Discovery Habits_ (weekly cadence of learning)[Product Discovery Methods: Types, Benefits & How to Use Them](https://staragile.com/blog/product-discovery-methods)[Product Discovery Techniques: Methods, Frameworks, and Tools](https://heymarvin.com/resources/product-discovery-techniques) ## ⚠️ Risks & Challenges * **Skipping discovery** → features with low adoption. * **Treating discovery as a one-off phase** → stale assumptions. * **Relying only on opinions** → solutions misaligned with actual user behavior. * **Over-investing in unvalidated ideas** → wasted engineering time and budget.[Product Discovery Guide: Methods & Frameworks (2026)](https://www.ideaplan.io/guides/product-discovery-guide)[Complete Guide to Product Discovery: Methods, Frameworks,](https://www.ideaplan.io/guides/the-complete-guide-to-product-discovery) ## ✅ Key Takeaways * Product discovery is not optional - it’s a _continuous habit_ that saves money and increases adoption. * The goal is to **reduce uncertainty** and **make informed bets** rather than gamble on untested ideas. * Teams that do discovery well ship fewer features but achieve **higher impact**. Would you like me to break down **real-world examples of companies that succeeded (or failed) based on their product discovery practices**? That could make the process even more concrete.

Product discovery is the critical first phase of product development where a team figures out **what to build** and **whether it's worth building**. Instead of jumping straight into writing code or designing features, product discovery focuses on deeply understanding user problems, validating assumptions, and ensuring the team solves the right problem for the right people. ## 1\. The Core Mindset of Product Discovery Coined largely by product leaders like Marty Cagan, product discovery runs parallel to _product delivery_ (building and shipping the product). While delivery answers _“How do we build this?”_ , discovery answers: * **Value:** Will customers actually want or buy this? * **Usability:** Can users figure out how to use it? * **Feasibility:** Can our engineering team actually build this with existing technology and timeframes? * **Viability:** Does this make business sense for our company? ## 2\. The Key Stages of Product Discovery ## 3\. Common Product Discovery Methods and Tools * **Customer Interviews:** 30-minute conversational chats with users to understand how they currently solve a problem and where their friction lies. * **Opportunity Solution Trees:** A visual framework (popularized by Teresa Torres) that maps out a desired outcome, the customer opportunities (needs/pain points) to address, the solutions to test, and the experiments to run. * **Fake Door Tests:** Adding a button or link for a feature that hasn't been built yet to gauge user interest based on how many people click it. * **Prototype Testing:** Watching users try to complete a task using a clickable mockup to spot confusion points.

**Product discovery** is the critical phase in product management where teams figure out _what_ to build by deeply understanding customer needs and validating ideas before writing code or committing heavy engineering resources. The goal is to minimize risks regarding value, usability, feasibility, and business viability. [Product discovery | Atlassian](https://www.atlassian.com/agile/product-management/discovery)[The Definitive Guide to Product Discovery and Frameworks](https://productschool.com/blog/product-fundamentals/what-is-product-discovery)[Guide: Product Discovery Process & Techniques | Productboard](https://www.productboard.com/blog/step-by-step-framework-for-better-product-discovery/) A standard, effective product discovery process generally follows a structured path - often mapped through frameworks like the [Double Diamond Process](https://www.productboard.com/blog/step-by-step-framework-for-better-product-discovery/) or continuous [Opportunity Solution Trees](https://productschool.com/blog/product-fundamentals/what-is-product-discovery) - broken down into these core phases: * * Understanding the Problem Space * **Customer Research** : Conduct qualitative research (customer interviews, user observation, empathy mapping) and quantitative research (data analytics, surveys) to uncover real pain points. * **Contextualizing Needs** : Utilize frameworks like Jobs To Be Done (JTBD) to identify the underlying tasks customers are trying to accomplish. [Productboard +1] * Defining and Prioritizing * **Problem Definition** : Narrow down the gathered insights into a concise, well-defined problem statement. * **Prioritization** : Use frameworks like RICE or Value vs. Complexity matrices to decide which problems are worth solving first based on impact and effort. [Productboard] * Ideation and Solution Design * **Brainstorming & Mapping**: Collaborate cross-functionally (product, design, engineering) to map out potential solutions to the prioritized problems. * **Prototyping** : Build low-to-high fidelity prototypes, wireframes, or Minimum Viable Products (MVPs) that represent the concept without fully engineering it. [Product School +1] * Testing and Validation * **User Testing** : Put prototypes in front of real users to measure usability and gauge genuine demand. * **Risk Mitigation** : Continuously answer four key questions: _Do they want it? (Value)_ , _Can they use it? (Usability)_ , _Can we build it? (Feasibility)_ , and _Does it align with business goals? (Viability)_. [Atlassian +1] * If you're interested, we can dive deeper into: * Popular frameworks like **Continuous Discovery Habits** or **Design Sprints** * How to balance **Dual-Track Agile** (discovery running alongside delivery) * Tips for conducting effective **customer interviews** Check out discussions on the **r/ProductManagement** community on Reddit to see how practitioners debate continuous vs. milestone-based discovery in the wild. Let me know how you'd like to proceed!

Product discovery is a continuous process for figuring out which customer problems are worth solving and which solutions are likely to work. Teams research users and the market, define a clear problem, generate ideas, prototype and test assumptions, then refine their approach based on feedback before investing in full development.([miro.com][1])([scrum.org][2])([usersnap.com][3]) [1]: https://miro.com/product-development/what-is-product-discovery/ "What Is Product Discovery? | Miro" [2]: https://www.scrum.org/resources/blog/what-product-discovery "What Is Product Discovery? | Scrum.org" [3]: https://usersnap.com/blog/product-discovery-process/ "Product Discovery Process: Aligning Insights with the PDLC"