What key activities do you do to validate problem statements?

When I have a hypothesis about a customer problem, which is where I believe we all should start, I treat validating that problem as a mini-project. User interviews: Basic, right? The first and most important activity is talking directly with customers or potential users who might have the problem. But that's not so simple. The goal is to hear in their words how painful the problem is (or if it’s a problem at all), and never lead them to specific assumptions. I like to ask them to tell stories: “ ...Read More

It's critical to stress-test if the problem is even worth solving - and if it’s urgent enough for someone to pay (in time or money) to fix it. Some dimensions I'd use to evaluate problem statements before trying to build a product for them: Frequency – How often do users encounter it? Intensity – How painful or disruptive is it when it occurs? Current alternatives – Are users cobbling together painful workarounds? Adoption willingness – Would they use a better solution if one existed? While simp ...Read More

Validating problem statements requires a user-centered approach that involves collecting data through user research, defining the problem statement, prioritizing the problem statement, developing a hypothesis, creating a prototype, testing the prototype, and iterating based on user feedback. Let's talk about each of them in a little more detail. Conduct user research: The first step in validating problem statements is to conduct user research. This can involve talking to users, observing their b ...Read More

In general, the main thing I look for when validating any problem or solution is data. As a PM, it is important for you to figure out where to get the right data for what you are validating. For example, if it's a problem statement around a user need or pain point, the first step would be to run user research panels to get data directly from users or potential users. I recommend you augment that with market research data such as independent analyst reports, research reports published by competit ...Read More

Validating a problem statement isn't a single activity, it's a combination of signals that together tell you whether the problem is real, widespread, and worth solving. Here's what we do at BILL: Customer interviews. This is the foundation. We go direct to users, listen for the language they use, the workarounds they've built, the frequency and intensity of the frustration. One interview is anecdote. Ten starts becoming signal. Product usage data. Where are users dropping off, slowing down, or n ...Read More

When you are thinking about problem statements, you need to first rephrase the problem as a hypothesis, then try to gather as much as data as possible quantitative (usage patterns, experiment results, etc) and qualitative (user research), analyze competitors trying to solve a similar problem, creating prototypes and lightweight experiments. The most critical and fun for me is customer research. This information can be gathered through surveys, interviews, focus groups, 1-1 discussions or observa ...Read More

It really depends on what the problem statement is and the hypothesis is. If it's about learning from existing needs and behaviors I conduct interviews, surveys, and sometimes observational studies to see firsthand how users experience the problem. This helps confirm whether the problem statement reflects real user challenges. Once your trying to understand if your solution hypothesis is valid, it's then time to figure out the cheapest thing you can build (maybe even just use humans) to validate ...Read More

Embrace prototyping. Especially for a 0 to 1 offering, asking customer and market feedback is hard because they have to envision the problem, your solution and on top of all this provide you with improvement ideas. So by sharing prototypes, you make it easier for potential customers to provide feedback.  Start with prototypes or user journey maps to demonstrate your product concept and solicit actionable feedback. Asking questions like will you find this useful, how often will be using the produ ...Read More