As product managers, we are responsible for building features that meet real customer needs. However, designing effective features requires a deep understanding of the customer’s problem—an understanding that we gain through a process known as customer discovery. The customer discovery process enables product teams to validate ideas, explore customer needs, and create features that deliver genuine value. Here is a step-by-step process for identifying when and how to conduct customer discovery for a new set of features.

Step 1: Recognizing the Need for Customer Discovery

Before embarking on a customer discovery process, we need to identify when and why it’s necessary. Customer discovery is most relevant when:

• New Feature Ideation: The product team is considering a new set of features but lacks concrete data on customer needs.
• Customer Complaints or Requests: There’s a noticeable trend in customer feedback indicating dissatisfaction, which suggests an opportunity for improvement.
• Market Shifts: Industry changes or competitor releases signal the need for new capabilities or enhancements to maintain competitiveness.

By recognizing the need for customer discovery, we set the stage for understanding which features will resonate most with our users. For instance, if feedback shows that users are struggling with onboarding, conducting discovery focused on onboarding enhancements could add value by reducing friction in their experience.

Step 2: Define Hypotheses and Assumptions

In the early stages, it’s critical to clarify what we believe about the problem and our customers’ needs. This helps set the foundation for our discovery process and ensures we approach customers with specific areas to validate.

1. Identify Assumptions: List out what you think you know about the customer’s needs, pain points, and preferences. For example, “Users find the reporting dashboard challenging to customize.”
2. Formulate Hypotheses: Turn these assumptions into testable hypotheses. For example, “If we make the reporting dashboard customizable with saved templates, users will complete tasks 30% faster.”
3. Prioritize Hypotheses: Select hypotheses that address high-impact customer issues or core product goals, helping to maintain focus during discovery.

These hypotheses guide the questions we’ll ask during customer interactions and help determine whether our assumptions are correct.

Step 3: Identify and Segment Target Customers

Not all customers are equally relevant to every feature set. To gather meaningful insights, it’s important to identify which customer segments would benefit most from the proposed features.

1. Define Target Personas: Identify key user personas that might interact with or benefit from the new feature set. For instance, if developing advanced reporting tools, focus on power users and business analysts.
2. Segment Users by Behavior and Needs: Use data to further refine these segments based on behavior patterns, such as frequency of use, engagement level, or specific tasks they perform within your product.
3. Select Key Customer Groups: Narrow down to 1-2 high-impact groups to prioritize for your initial discovery, ensuring you’re targeting customers most likely to use the new features.

By focusing on specific user groups, you ensure that feedback is relevant and reflects the actual needs of those who will engage with the feature.

Step 4: Choose Research Methods and Plan Customer Interviews

Once target segments are clear, it’s time to plan how to gather insights from them. The most effective customer discovery process uses a combination of qualitative and quantitative methods.

Qualitative Methods:

• Customer Interviews: Conduct 10-15 in-depth interviews with users to understand their daily routines, pain points, and thoughts around existing tools or processes.
  • Prepare open-ended questions that encourage detailed responses, such as “Can you walk me through how you currently handle X?”
  • Probe deeper on specific tasks they struggle with or workarounds they’ve created.
• Surveys: Use surveys with open-ended questions to gather broader insights from a larger audience. For example, “What additional features would make the reporting dashboard more useful to you?”

Quantitative Methods:

• Usage Analytics: Analyze current user behavior within the product to identify trends. For example, data showing high exit rates on a particular feature page could indicate usability issues.
• A/B Testing (if applicable): If there’s a possibility to test small changes, create A/B tests to see how users respond. This can be especially valuable for feature updates in an existing interface.

Planning a mix of qualitative and quantitative research methods ensures a comprehensive view of both what users are doing and why they’re doing it.

Step 5: Conduct and Document Customer Interviews

Conducting interviews is one of the richest sources of insight in customer discovery, but effective interviews require careful listening and documentation.

1. Conduct Interviews Thoughtfully: Focus on listening rather than pitching ideas. Allow customers to guide the conversation to understand their genuine needs and thoughts.
2. Ask “Why” and “How” Questions: Dig deeper by asking questions like “Why do you find this process difficult?” or “How do you currently manage this task?” to reveal underlying motivations and frustrations.
3. Document Findings: Record interviews (with permission) or take detailed notes, capturing both direct quotes and observations about their behavior or responses.

After interviews, consolidate your notes in a central location to easily analyze themes and trends.

Step 6: Analyze Insights and Identify Patterns

Once you’ve collected customer insights, it’s time to analyze them and draw conclusions about what the new feature set should accomplish.

1. Identify Common Themes: Review your interview notes and survey data to identify recurring themes, pain points, and requests. For instance, if many users mention that they need more flexibility in exporting data, that’s a signal for customization options.
2. Align Insights with Hypotheses: Evaluate whether your hypotheses were confirmed or disproven based on customer feedback. This will help determine if your original assumptions were accurate.
3. Prioritize Problems to Solve: Rank the identified customer needs based on frequency, urgency, and the value they would bring to the customer experience. Focusing on high-impact areas ensures you are solving the most pressing issues.

By analyzing patterns in feedback, you’ll be able to design feature solutions that address widespread customer needs.

Step 7: Develop Feature Ideas and Validate Prototypes

With your research insights in hand, start brainstorming possible solutions and creating prototypes.

1. Design & Develop Low-Fidelity Prototypes: Begin with simple sketches or wireframes to map out possible feature designs. Use these to gather initial reactions before investing too heavily in development.
2. User Testing and Feedback Loops: Conduct usability tests to validate whether the prototype addresses the customer’s needs. For example, test the prototype with a small group of target users, asking them to complete relevant tasks.
3. Iterate Based on Feedback: Use feedback to improve the prototype, focusing on areas where users encounter confusion or barriers.

Continuous testing with users ensures the feature evolves in a way that aligns with their needs, reducing the likelihood of misaligned development.

Step 8: Share Findings with Stakeholders

Communicate your findings with internal stakeholders, ensuring alignment across product, design, and development teams.

1. Create a Customer Discovery Report: Summarize key findings, validated hypotheses, and feature recommendations in a clear and concise format. Highlight customer quotes or data points to support each finding.
2. Align with the Product Roadmap: Work with stakeholders to determine how the new feature set aligns with broader business objectives and determine timelines for development.
3. Set Success Metrics: Define metrics to track after the feature launch, such as usage rate, completion time for key tasks, or customer satisfaction.

Engaging stakeholders early and often ensures support for development and that the new features align with company goals.

The customer discovery process is a powerful tool for ensuring that new features solve real customer problems. By following this structured approach—recognizing the need for discovery, defining hypotheses, segmenting customers, conducting research, analyzing insights, and validating prototypes—product managers can increase the likelihood of success with each feature release. This approach not only enhances the product’s value but also strengthens the relationship with users by showing them that their needs and feedback are truly valued in the development process.

Thank you for reading,
Boris Godin

* AI helped write and generate images for this post

If you enjoyed this post, please share the love and subscribe to the Product Management Mastery newsletter for more content like this.

Let’s Build a Better World.

Whenever you are ready:

Here are a few ways I can help you:

1. Generate leads & customers by getting your product or business in front of 1,800+ subscribers of the Product Management Mastery Newsletter here.
2. Hire me as your fractional Senior Product Manager / Head Of Product to unlock fresh perspectives on how you can add more value for your customers here.
3. Have an idea💡 for a product you want to build? I can help you with product strategy, design, development, & launch. Click here to submit a request for a free consultation.