Problem vs Solution Validation: Which First?
Founders often test their solution before they know the problem is worth solving. Problem validation asks whether buyers feel enough pain to act. Solution validation asks whether your answer is the one they’ll choose.
What is the difference between problem and solution validation?
Problem validation proves that a specific group has a frequent, costly problem they already try to solve. Solution validation proves that your approach solves it well enough that they would switch and pay. Validate the problem first: a great solution to a mild problem rarely sells, and solution feedback is misleading until the problem is confirmed.
What evidence does each stage need?
Each stage asks different questions and needs different evidence. The table shows what to look for, so you know which stage you are in and when you’ve finished it.
| Problem validation | Solution validation | |
|---|---|---|
| Question | Is this problem worth solving? | Is our answer the one they’ll choose? |
| Methods | Discovery interviews, observation | Prototypes, demos, smoke tests, pre-sales |
| Strong evidence | Recent stories, costs, current workarounds and spend | Deposits, letters of intent, pilots, switching from current tools |
| Weak evidence | ‘That sounds annoying’ | ‘That looks cool’ |
| Done when | The problem repeats across a segment with real cost | Buyers commit something to get it |
When is the problem validated?
The problem is validated when, across one segment, people describe it in similar words, it happens often, it costs real time or money, and they already try to solve it with tools, staff or workarounds. If any of the four is missing, keep exploring or narrow the segment. Customer interview questions help you collect this evidence.
- Repeats: most interviews in the segment describe it.
- Frequent: it happens weekly or monthly, not once a year.
- Costly: it wastes time, loses money or creates risk.
- Already addressed: they use workarounds or pay for something today.
How do you validate the solution?
Show a simple version of the solution, such as a clickable prototype, a demo or a description on a landing page, then ask for a commitment. Watch for whether buyers would switch from what they use today, and what would stop them. Tests are on smoke tests and pre-selling. Lighter ways to deliver the solution first, such as concierge tests, are in types of MVP.
Fall in love with the problem.
Solutions change many times. A real, costly problem in a reachable segment is what makes a company.
What if the solution tests fail but the problem is real?
Keep the problem and change the solution, the offer or the price. A real problem with a failed solution is a good position: you know what people need, you have the wrong answer. Go back to the interviews and ask what they would need to switch. Reading validation signals helps you decide whether to change or stop.
Frequently asked questions
What is problem validation?
Proving that a specific group has a frequent, costly problem they already try to solve.
What is solution validation?
Proving that your approach solves the problem well enough that buyers would switch and pay.
Should I validate the problem or the solution first?
The problem first. Solution feedback is misleading until you know the problem matters.
How do I know my problem is validated?
When it repeats across a segment, happens often, costs real time or money, and people already try to solve it.
What if nobody is solving the problem today?
Be cautious. It may mean the problem isn’t painful enough to act on.
What if my solution fails but the problem is real?
Keep the problem and change the solution, offer or price, then test again.