Customer Validation: How to Know If Your Idea Is Worth Pursuing
•
4 min read
•
2 views
Before building your product, validate that customers actually want it. Here's how to test your assumptions and avoid building something nobody needs.
Having a great idea feels amazing. But ideas are cheap – execution is everything. Before you invest months or years building something, you need to validate that customers actually want what you're planning to create.
Customer validation isn't about proving your idea is right. It's about discovering whether you're solving a real problem that people are willing to pay to solve.
## The Validation Mindset
Most entrepreneurs approach validation trying to prove their idea is good. This is backwards. You should be trying to prove your idea is bad – and only proceed if you can't.
This mindset shift is crucial because:
- It prevents confirmation bias
- It encourages honest feedback
- It saves time and money on bad ideas
- It leads to better products for good ideas
## The Problem-First Approach
Start with the problem, not the solution. Many failed startups had great solutions to problems that didn't really exist or weren't painful enough to pay for.
**Step 1: Define the Problem**
Write down exactly what problem you think you're solving. Be specific about who has this problem and when they experience it.
**Step 2: Validate the Problem Exists**
Before building any solution, confirm that the problem is real and significant. Talk to potential customers about their current challenges.
**Step 3: Understand Current Solutions**
How do people solve this problem today? If they don't, maybe it's not that important to them.
## Customer Discovery Techniques
**The Mom Test**
Never ask "Would you use this?" Instead, ask about their current behavior and past experiences. Good questions:
- "When was the last time you experienced [problem]?"
- "How do you currently handle [situation]?"
- "What's the most frustrating part of [current process]?"
**The Five Whys**
When someone mentions a problem, dig deeper by asking "why" five times. This reveals the root cause and whether it's worth solving.
**Observe Don't Just Ask**
People don't always do what they say they'll do. Whenever possible, observe actual behavior rather than relying on stated intentions.
## Validation Experiments
**Experiment 1: The Problem Interview**
Interview 10-15 people in your target market about the problem (not your solution). Look for patterns in their responses.
**Experiment 2: The Landing Page Test**
Create a landing page describing your solution and measure how many people sign up for updates or pre-orders.
**Experiment 3: The Concierge Test**
Manually deliver your service to a small group of customers. This tests both problem and solution fit.
**Experiment 4: The Smoke Test**
Advertise your product before building it. See how many people click through and try to buy.
## Red Flags to Watch For
- People are polite but not enthusiastic
- No one is already trying to solve this problem
- You have to convince people they have the problem
- People say "that's interesting" instead of "I need this"
- You're the only person excited about the solution
## Green Lights That Signal Opportunity
- People interrupt you to tell you about their struggles with this problem
- They're already spending money on inadequate solutions
- They ask when they can start using your product
- They offer to pay in advance or help you build it
- They introduce you to others with the same problem
## Common Validation Mistakes
**Asking Leading Questions**
"Wouldn't it be great if..." is not a validation question. It's a leading question that generates false positives.
**Only Talking to Friends and Family**
People who know you personally will be more polite and less honest. Get outside your immediate network.
**Falling in Love with the Solution**
Remember, you're validating the problem first, then the solution. Don't get attached to your first idea for how to solve it.
**Not Talking to Enough People**
5-10 conversations isn't enough. You need to talk to enough people to see clear patterns emerge.
## Moving Forward
Validation isn't a one-time activity. As you build and iterate, you'll continue discovering new things about your customers and their needs.
The goal is to build something people want. Validation helps ensure you're on the right track before you invest significant time and resources.
If validation shows your initial idea isn't viable, that's success – you've saved yourself from building something nobody wants. Use what you learned to pivot to a better opportunity.
Customer validation isn't about proving your idea is right. It's about discovering whether you're solving a real problem that people are willing to pay to solve.
## The Validation Mindset
Most entrepreneurs approach validation trying to prove their idea is good. This is backwards. You should be trying to prove your idea is bad – and only proceed if you can't.
This mindset shift is crucial because:
- It prevents confirmation bias
- It encourages honest feedback
- It saves time and money on bad ideas
- It leads to better products for good ideas
## The Problem-First Approach
Start with the problem, not the solution. Many failed startups had great solutions to problems that didn't really exist or weren't painful enough to pay for.
**Step 1: Define the Problem**
Write down exactly what problem you think you're solving. Be specific about who has this problem and when they experience it.
**Step 2: Validate the Problem Exists**
Before building any solution, confirm that the problem is real and significant. Talk to potential customers about their current challenges.
**Step 3: Understand Current Solutions**
How do people solve this problem today? If they don't, maybe it's not that important to them.
## Customer Discovery Techniques
**The Mom Test**
Never ask "Would you use this?" Instead, ask about their current behavior and past experiences. Good questions:
- "When was the last time you experienced [problem]?"
- "How do you currently handle [situation]?"
- "What's the most frustrating part of [current process]?"
**The Five Whys**
When someone mentions a problem, dig deeper by asking "why" five times. This reveals the root cause and whether it's worth solving.
**Observe Don't Just Ask**
People don't always do what they say they'll do. Whenever possible, observe actual behavior rather than relying on stated intentions.
## Validation Experiments
**Experiment 1: The Problem Interview**
Interview 10-15 people in your target market about the problem (not your solution). Look for patterns in their responses.
**Experiment 2: The Landing Page Test**
Create a landing page describing your solution and measure how many people sign up for updates or pre-orders.
**Experiment 3: The Concierge Test**
Manually deliver your service to a small group of customers. This tests both problem and solution fit.
**Experiment 4: The Smoke Test**
Advertise your product before building it. See how many people click through and try to buy.
## Red Flags to Watch For
- People are polite but not enthusiastic
- No one is already trying to solve this problem
- You have to convince people they have the problem
- People say "that's interesting" instead of "I need this"
- You're the only person excited about the solution
## Green Lights That Signal Opportunity
- People interrupt you to tell you about their struggles with this problem
- They're already spending money on inadequate solutions
- They ask when they can start using your product
- They offer to pay in advance or help you build it
- They introduce you to others with the same problem
## Common Validation Mistakes
**Asking Leading Questions**
"Wouldn't it be great if..." is not a validation question. It's a leading question that generates false positives.
**Only Talking to Friends and Family**
People who know you personally will be more polite and less honest. Get outside your immediate network.
**Falling in Love with the Solution**
Remember, you're validating the problem first, then the solution. Don't get attached to your first idea for how to solve it.
**Not Talking to Enough People**
5-10 conversations isn't enough. You need to talk to enough people to see clear patterns emerge.
## Moving Forward
Validation isn't a one-time activity. As you build and iterate, you'll continue discovering new things about your customers and their needs.
The goal is to build something people want. Validation helps ensure you're on the right track before you invest significant time and resources.
If validation shows your initial idea isn't viable, that's success – you've saved yourself from building something nobody wants. Use what you learned to pivot to a better opportunity.