...is the problem really real to anyone? And what is the real problem?
Before you build a product, you will want to understand what problem it solves. Otherwise you may end up with a solution looking for a problem.
When we understand the problem from the customers perspective we will be able to build the right solution.
Note of caution: It is true that some solutions are solving problems that customers never knew the had. They gain something that they are not aware that they need until they see it. So you may also look for customers blind spots: Ways to improve their life that they never knew they could ask for.
The Problem Test is useful when you ask yourself the question: Do people care?
Usually early in the innovation process when you have decided which idea you want to pursue and develop. And before you go into detail with your product innovation. Even before you actually have a clear idea about the final solution.
Arrange meetings with potential users and customers and go through the following 4 steps:
Find a more detailed manual below...
Steve Blank & Bob Dorf: The Startup Owners Manual, 2012. The method is well described in chapter 5, p. 189-226.
Before you meet with a customer or user you should prepare a Problem Presentation. A problem presentation has 4 steps:
Remember that the word "presentation" does not automatically mean PowerPoint.
Define the three most important things to find out during the customer meeting. What do you want to prove or disprove?
This will help you stay focused as the conversation wanders.
Be at least two people doing the interview. It is very demanding both to conduct interviews, to record answers and to be aware of the customer's body language and other unsaid signals.
Let one person focus on the interview while the other focuses on listening and observing. Listening and observing could even be shared between two people.
Don't sound like you're trying to sell something. If you do, the customer may become defensive and less honest.
But in the end, try to get the customer to commit to something - at least if the customer has been positive about your solution. It may just be a request for a new meeting when your solution is more ready for display.
Asking the customer to commit to something is a test of whether they mean, what they say.
Problem:
Solution:
Business Model: