How to validate your problem before building anything

Learn why talking to customers before writing a single line of code is the most important thing you can do as a founder.

Why Validation Comes First

Most startups fail not because they can't build the product — they fail because they build something nobody wants. The painful truth is that many founders spend months (and thousands of dollars) building a solution to a problem that isn't real, isn't painful enough, or isn't experienced by the people they think it is.

Validation is the discipline of testing your assumptions with real people before you invest heavily in building. The goal isn't to gather compliments — it's to find out what's genuinely true.

What You're Actually Testing

When you validate a problem, you're trying to answer three questions:

• Is this problem real? Do people actually experience it, or is it hypothetical?
• Is it painful enough? People complain about many things — but they only pay for solutions to problems that genuinely bother them.
• Is it experienced by who you think? Your target customer may not be who you imagined.

The Mom Test Principle

The classic mistake is asking people "Would you use this?" — that question is nearly useless. People are polite. They'll say yes to avoid conflict, especially to a founder who's clearly excited.

Instead, ask about their past behavior and experiences:

• "How do you currently handle this today?"
• "How often does this come up?"
• "What have you already tried to solve it?"
• "How much time/money have you lost because of this?"

These questions reveal actual behavior, not optimistic intentions.

Running Your First 10 Interviews

Start with 10 interviews before drawing any conclusions. Recruit from your network, LinkedIn, or relevant communities. Aim for people who genuinely match your target customer profile.

During each conversation: 1. Spend 15–20 minutes asking open-ended questions about the problem space 2. Never mention your solution until the very end (and only to get feedback on the idea, not validation) 3. Take notes on exact phrases people use — these become your marketing language

What Good Signal Looks Like

Validation isn't about unanimity. Look for:

• Recurring themes across multiple conversations
• Unprompted stories about pain or loss
• Existing workarounds (people duct-taping solutions = strong signal)
• Willingness to pay or act — letters of intent, joining a waitlist, offering to pilot

If fewer than 6 out of 10 people describe the problem in similar terms, consider pivoting your problem hypothesis.

Moving Forward

Once you've validated that a real, painful problem exists, you're ready to move to understanding the market and designing a solution. But don't rush — the hours you invest here will save you months of misdirected effort.