What is product discovery?
Product discovery is the process of figuring out exactly what people need so you can build a product they love. It involves identifying a worthwhile problem to solve, determining the best solution, and adjusting to meet the evolving needs of customers and the business — making it some of the most exciting and dynamic product work out there.
Companies often invest in product discovery before building a new product or major new functionality or when prioritizing features for an existing offering. Entrepreneurs and product builders usually guide the product discovery process, working alongside the broader cross-functional product team. Some common product discovery activities include creating customer personas, analyzing customer feedback, and user story mapping. The goal of these exercises is to help the product team empathize with customers and determine which features to build next in order to create a more lovable user experience.
Although some organizations focus on product discovery only at the beginning of the product development cycle, it really requires your attention during the entire product development process — from strategizing and ideating to launching and beyond. As markets and customers evolve, you should constantly iterate on your product so you can continue delivering value long after releasing your initial offering.
Build lovable products with Aha! software — sign up for a free trial.
Whether you are starting a business or working as a product manager, doing product discovery right requires the relevant knowledge, skills, and desire to build the greatest offering you possibly can. If you are eager to learn more about product discovery or are simply looking for ideas to improve your existing process, this guide will cover everything you need to know — from the perspective of a product builder. Find out what the process entails, why it is essential, and tips for refining your own product discovery process.
Why is product discovery important?
Product discovery is challenging and complex work. You aim to understand what potential customers need and how to build a solution. This takes a boundless empathy for your customers and a deep grasp of what they are struggling with. As a successful product builder, you must move beyond a surface understanding of who users are — internalizing their problems and anticipating their needs as if they were your own.
A robust product discovery process gives the product team a structured way to approach product development — bringing much-needed clarity and focus to what you are trying to achieve. Product discovery can help you move past initial assumptions about what current users or prospects need. By using data and adopting a customer-centric approach to product building, you can validate your assumptions and confirm that a problem actually exists before building a solution for it. The goal is to gain a holistic understanding of what customers need and how your product delivers value, so you can maximize the impact of your work.
Whether your company calls it "product discovery" or something else, deeply understanding customers' needs and how to solve them is vital for any product team. Broadly speaking, product discovery can help teams:
Empathize — identify with users and adopt a customer-centric mindset towards product development.
Innovate — come up with new ideas for delivering more lovable products.
Prioritize — determine and invest in the features that will lead to the greatest customer happiness.
Reduce risk — invest in building the right products that customers truly need and minimize wasted team effort.
What does the product discovery process entail?
Some companies have a defined product discovery framework and others take a more flexible approach. You might experiment with different techniques or activities to stimulate thinking, gather relevant data, or increase empathy for the people who will be using your product.
The exact stages of product discovery will vary at different organizations, but the process typically entails gaining an understanding of what customers need and then validating that understanding. Keep in mind that the phases are not meant to be linear. For example, after evaluating an idea for a potential feature, you might find that your assumptions were incorrect, so you return to the research and ideate stages to refine. Here is an overview of what the process might look like:
No matter what product discovery looks like at your company, close collaboration between product management, product marketing, designers, and developers is key to building and delivering a product that resonates with customers. Everyone in the organization has valuable insights to share about customer needs, product performance, and areas for improvement. Of course, this includes customers themselves. When you speak directly to customers and engage them with meaningful questions, you can move beyond a shallow understanding of personas to really know and internalize peoples' struggles.
Here are some of the ways that teams rely on during product discovery to research user needs, validate and refine ideas, and figure out the best way to solve customers' problems:
Product discovery method
Collect and analyze feedback from customers, colleagues, and partners.
Some teams use idea management software that includes ideas portals, in-app community feedback, and virtual focus groups or empathy sessions.
Validate a business idea and decide whether or not to pursue a product opportunity.
Some startups use a lean canvas model to capture the problem, solution, unique value proposition, and other key information such as customer segments and revenue streams.
User story mapping
Visualize the experience that customers have with your product at every touchpoint.
Product and development teams rely on user story mapping to design and build new functionality that helps customers achieve their goals.
Represent the product roadmap as a tree in order to better prioritize features across a portfolio of products.
Some product teams at large organizations with multiple offerings choose to do a product tree exercise on a virtual whiteboard — using branches, roots, and leaves to depict products, technical requirements, and new ideas for features, respectively.
Product value score
Rank and prioritize work across each stage of the product development cycle.
Teams that use the Aha! product value score consider metrics including population, need, strategy, effort, and confidence.
Keep in mind that this is not an exhaustive list. Depending on your needs and organizational maturity, you might also use a variety of other product discovery methods. You can use customer personas, design thinking, the jobs-to-be-done framework, the MoSCoW method, A/B testing, and usability testing. You will likely want to read about and experiment to see which methods work the best for your team.
Establishing a robust product discovery process is vital for building lovable products. When you are able to zoom in on exactly what people need and how you will deliver it, you can begin bringing greater value to customers and the business.
Create and prioritize product features with ease. Get started with a 30-day free trial of Aha! Roadmaps.
- What is a business model?
- What is customer experience?
- What is the Complete Product Experience (CPE)?
- What is a customer journey map?
- What is product-led growth?
- What are the types of business transformation?
- What is enterprise transformation?
- What is digital transformation?
- What is the role of product management in enterprise transformation?
- What is a Minimum Viable Product (MVP)?
- What is a Minimum Lovable Product (MLP)?
- What is product vision?
- How to set product strategy
- What is product-market fit?
- What is product differentiation?
- How to position your product
- How to price your product
- What are product goals and initiatives?
- How to set product goals
- How to set product initiatives
- What is product value?
- What is value-based product development?
- 10Ps marketing matrix
- 2x2 prioritization matrix
- 5 Whys
- Business model
- Customer journey map
- Decision tree
- Lean canvas
- Marketing strategy
- Porter's 5 forces
- Product positioning
- Product vision
- Segment profile
- Strategic roadmap
- SWOT analysis
- Collections: Business model
- Collections: SWOT
- Collections: Objectives and key results (OKR)
- Collections: Product positioning
- Collections: Market positioning
- Collections: Marketing strategy
- Collections: Marketing messaging
- 2023 monthly calendar
- 2x2 prioritization matrix
- Kanban board
- Market requirements document
- Program board
- Product requirements document
- Pros and cons
- Release roadmap
- ROAM board
- Timeline diagram
- User story
- User story map
- Collections: Product development process
- Collections: MRD
- Collections: PRD
- Collections: Gantt chart
- Collections: User story
- Collections: User story mapping
- Collections: Feature definition checklist
- Collections: Feature prioritization templates
- Collections: Marketing plan templates
- Collections: Marketing calendar templates
- Common product development methodologies
- Common agile development methodologies
- What is agile product management?
- What is agile software development?
- What is waterfall product management?
- What is agile transformation?
- Agile vs. lean
- Agile vs. waterfall
- What is an agile roadmap?
- What is an agile retrospective?
- Best practices of agile development teams
- What is a burndown chart?
- What is issue tracking?
- Introduction to agile metrics
- Agile glossary
- What is scrum?
- What are scrum roles?
- What is a scrum master?
- What is the role of a product manager in scrum?
- What is a sprint?
- What is a sprint planning meeting?
- What is a daily standup?
- What is a sprint review?
- Product release vs. sprint in scrum
- Themes, epics, stories, and tasks
- How to implement scrum
- How to choose a scrum certification
- What is a product?
- What is product development?
- What is product management?
- What is portfolio product management?
- What is product operations?
- What are the stages of product development?
- What is the product lifecycle?
- What is a product management maturity model?
- What is product development software?
- Why product teams need virtual whiteboarding software
- Introduction to marketing
- What are some marketing job titles?
- What is the role of a marketing manager?
- What is the role of a product marketing manager?
- How are marketing teams organized?
- Which tools do marketers use?
- Interview questions for marketing managers
- Typical salary for marketing managers
- How to make a career switch into marketing
- How to structure your product development team
- Best practices for managing a product development team
- How to structure your product team meeting
- 15 tips for running effective product team meetings
- Which tools do product managers use?
- Tips for effective collaboration between product managers and engineers
- How do product managers work with other teams?
- Brainstorming meeting
- Brainstorming session
- Creative brief
- Daily note
- Daily standup meeting
- Marketing calendar
- Meeting agenda
- Meeting notes
- Mind map
- Organizational chart
- Presentation slides
- Process improvement
- Pros and cons
- Sprint planning meeting
- Sprint retrospective
- Sprint retrospective meeting
- Sticky note pack
- Timeline diagram
- Workflow diagram
- Collections: Product management meeting
- Collections: Diagrams, flowcharts for product teams
- Collections: Whiteboarding
- Collections: Templates to run product meetings