What Is Validation?
Validation is the process of testing whether your idea solves a real problem for real people. Most startups fail not because the product was bad, but because nobody needed it in the first place.
Before you build anything, you need evidence that: 1. The problem you identified actually exists 2. People care enough about it to pay for a solution 3. Your proposed solution addresses the problem effectively
Validation saves you from spending months building something nobody wants.
Talk to Real People
The fastest way to validate is to talk to potential customers. Not your friends. Not your family. The actual people who would use your product.
**How to do it:** - Identify 10-20 people who fit your target customer profile - Ask them about the PROBLEM, not your solution - Listen more than you talk (80/20 rule) - Take notes during or immediately after each conversation
**Questions to ask:** - "Tell me about the last time you experienced [problem]" - "What did you do to solve it?" - "What was frustrating about the solutions you tried?" - "How much time or money do you spend dealing with this?"
**Questions to AVOID:** - "Would you use my app?" (people always say yes to be polite) - "Don't you think this is a great idea?" (leading question) - "How much would you pay?" (hypothetical answers are unreliable)
Pro Tips
- Record conversations (with permission) so you can review them later
- Look for patterns across multiple conversations
- If people are not excited about the problem, the idea needs work
The Mom Test
There is a famous concept called "The Mom Test" - the idea that even your mom should not be able to lie to you about your idea if you ask the right questions.
**The Rules:** 1. Talk about their life, not your idea 2. Ask about the past, not hypothetical futures 3. Talk less, listen more 4. Seek facts and commitments, not compliments
**Bad Conversation:** "I'm building an app that helps students find study groups. Would you use it?" "Oh that sounds great, honey!"
**Good Conversation:** "Tell me about the last time you struggled to find someone to study with. What happened? What did you end up doing?"
The second conversation gives you real data. The first gives you false hope.
Build a Simple Test
After conversations, create a lightweight test:
**Landing Page** - Create a simple page describing your solution. Include a sign-up form. If people sign up, there is real interest.
**Pre-Sales** - Offer your product before it exists. If people pay in advance, validation is strong. (Be honest that it is coming soon.)
**Fake Door Test** - Create a button or link for the feature. Track how many people click it.
**Wizard of Oz** - Manually deliver the service before automating it. If you can solve the problem by hand for 10 people, you can build technology to solve it for 10,000.
The goal is not perfection. The goal is learning with minimal effort.
Warning
Never lie to your test users. Be transparent that you are testing an idea. Deception destroys trust and reputation.
Reading the Results
After testing, look for these signals:
**Strong Validation:** - People describe the problem with emotion and urgency - They have already tried other solutions (and are dissatisfied) - They offer to pay or sign up without being pushed - They ask when it will be ready
**Weak Validation:** - People say "that's nice" but show no urgency - They cannot recall experiencing the problem - They are unwilling to commit time, money, or attention - You have to convince them the problem exists
If validation is weak, that is not failure - it is learning. Pivot your idea, target a different customer, or find a more painful problem.