Customer Research to Validate Hypotheses

This week, we’re exploring how to validate product hypotheses using various customer research techniques.

We'll cover empathy interviews, surveys, in-app polls, and customer support insights.

Along the way, I’ll share practical tips to conduct effective customer interviews and design surveys that yield actionable feedback.

This is the third portion of our end-to-end Product discovery series. If you missed the last two issues, check out my library here.

Validating the hypotheses you’ve formed from market research with customer feedback is essential to building products that truly meet user needs.

Without structured validation, assumptions remain untested, which increases the risk of building features or products that fail in the market. By validating your hypotheses in real customer insights, you can fine-tune product ideas and avoid spending a lot of money on a failed idea.

Let’s also talk briefly about the failed ideas. It’s just as important to weed out the ideas that are destined to fail as it is to find the successful ones.

Too many product people fear having an idea fail or not delivering something. So they push forward with ideas they shouldn’t or just never validate anything before it gets built. Neither is good.

Without careful preparation and thoughtful questioning, your research won’t yield the depth or accuracy needed for reliable insights.

Many product managers overlook the importance of validation. It’s not their fault. It’s most likely the culture in the company they work for, either not understanding or just not caring about the strategic side of Product Management.

But here’s where the problem compounds. One day, your company decides they want Product to drive strategy and conduct real discovery. Because the product people they have working there have never been real product managers before, they never developed the skills needed to actually go out and do effective customer research.

Without careful preparation and thoughtful questioning, your research won’t yield the depth or accuracy needed for reliable insights. So let’s fix that today. We will discuss the most common methods of customer research when you should use each, and some tips on how to conduct them effectively.

Takeaway 1: Use Empathy Interviews to Deepen Your Understanding

Empathy interviews are best for exploring customer needs, motivations, and pain points. These interviews allow you to probe deeply, helping to uncover insights that more structured surveys might miss.

Tips for Effective Interviews:

1. Prepare a Structured Guide: Outline key areas to cover, but stay flexible. A structured guide keeps the conversation focused while allowing room for new insights to emerge.
2. Ask Open-Ended Questions: Questions like “Can you describe a time when…” invite detailed responses and encourage customers to share stories, which can reveal nuanced perspectives.
3. Create a Comfortable Environment: Start with light, conversational questions to put participants at ease. When customers feel relaxed, they’re more likely to open up and provide candid feedback.
4. Use Probing Questions: Follow up on interesting responses with prompts like, “Can you tell me more about that?” or “Why is that?”

Probing questions can lead to unexpected insights that enrich your understanding of the user experience.

Empathy interviews provide qualitative data, offering context and emotional depth that’s hard to capture with other methods. Use these insights to refine your hypotheses and ensure they align with real user experiences.

Takeaway 2: Gather Quick Insights with In-App/On-Platform Polls and Surveys

Polling is a quick, effective way to capture feedback from a large user base without requiring a significant time investment from your customers. Use in-app polls for brief, focused questions that help validate specific aspects of your hypothesis.

Tips for Effective Polling

1. Limit the Number of Questions: To maximize participation, keep polls short, ideally just one or two questions. Polls are best suited for validating specific features or preferences.
2. Ask Targeted Questions: For example, if you’re testing the assumption that users need more customization options, a poll question could be, “How often do you customize your settings?”

Responses to these questions offer immediate data points to guide your decision-making.

Tips for Crafting Effective Surveys

When more detailed feedback is needed, email or text surveys offer a great way to validate hypotheses on a broader scale.

Surveys allow you to collect both qualitative and quantitative feedback, providing a well-rounded view of customer sentiment.

1. Define Clear Objectives: Start by clarifying what you aim to learn. Define objectives around specific information you want to gather, whether it’s validating a need for a new feature or understanding pain points in the current product.
2. Keep It Concise: Long surveys lead to survey fatigue and lower response rates. Focus only on essential questions, and consider breaking up the survey into sections if it’s lengthy.
3. Use a Mix of Question Types: Combine multiple-choice questions for quick answers with open-ended questions to capture richer feedback. Rating scales are also helpful for gauging sentiment or satisfaction levels.
4. Offer Incentives: To increase participation, consider offering a small reward, such as a discount or gift card. Incentives often lead to higher response rates and more complete feedback.
5. Use Survey Tools: Platforms like SurveyMonkey, Qualtrics, and Google Forms make it easy to design, distribute, and analyze surveys.

When well-designed, surveys provide powerful data that supports or challenges your hypotheses, guiding your next steps with more confidence.

Takeaway 3: Leverage Customer Support Insights

Your customer support team is on the front lines, hearing directly from users about their issues and requests.

Support tickets, chats, and calls can reveal patterns in customer needs that might otherwise go unnoticed.

How to Use Support Insights

1. Identify Recurring Issues: Look for common problems or requests from customers. Frequent complaints about the same issue indicate a pain point that could form the basis of a hypothesis.
2. Capture Feature Requests: If multiple customers ask for the same feature, it’s a strong signal worth investigating. These requests can validate assumptions or inspire new hypotheses.
3. Analyze Sentiment: Pay attention to tone and language in support conversations. Frustrated or enthusiastic customers often provide clues about what’s working and what’s not.

Customer support insights are a valuable and often underutilized source of qualitative data. Incorporating these insights into your validation process helps ground hypotheses in real user experiences.

Takeaway 4: Test with Structured A/B Experiments

Once you’ve collected initial qualitative insights, consider running A/B tests to validate hypotheses quantitatively. A/B testing allows you to measure the impact of potential changes by comparing outcomes between two groups.

Best Practices for A/B Testing

1. Set a Clear Hypothesis: Formulate a precise hypothesis that includes an expected outcome. For example, “If we add a search function, we expect an increase in daily active users by 10%.”
2. Define Success Metrics: Choose metrics that directly relate to the hypothesis. For example, use retention rate or engagement frequency to gauge the success of a new feature.
3. Run Tests Long Enough for Statistical Significance: Ensure your test runs long enough to capture a reliable dataset. Cutting it short can lead to misleading conclusions.

A/B testing provides quantitative evidence, allowing you to confirm or disprove your hypothesis with hard data.

Takeaway 5: Use Feedback Loops to Refine Hypotheses

Validating hypotheses isn’t a one-and-done process; it’s iterative. As you collect feedback, continue to refine your hypotheses, adapting them based on new data and insights.

Tips for Effective Feedback Loops

1. Review Regularly: Schedule regular check-ins to review customer insights and test results. Use these to identify patterns and adjust hypotheses accordingly.
2. Document Changes: Track updates to your hypotheses over time to understand how they evolve. This documentation helps you see the full picture and learn from each validation cycle.
3. Engage the Team: Collaborate with cross-functional teams, such as design and engineering, to interpret findings and align on next steps.

Creating a feedback loop ensures you’re continuously validating and refining your hypotheses as the product and market evolve.

In Closing

Validating hypotheses is at the heart of user-centered product development. Each validation step brings you closer to building solutions that genuinely resonate with users.

In next week’s newsletter, we’ll explore how to turn validated hypotheses into actionable product strategies, ensuring every insight you gather translates into impactful decisions.

Thanks for reading

​
​