How to validate a startup idea before you build it
A practical validation process for testing the problem, urgency, audience, and willingness to act before investing in a product.
Validation is about reducing uncertainty
Validation is not collecting compliments for a solution. It is learning whether a specific group experiences a meaningful problem often enough to change its behavior.
Begin by writing the riskiest assumptions behind the idea. Include who has the problem, when it occurs, what it costs, how people solve it today, and why they might switch.
Keep in mind
- Write assumptions as falsifiable statements.
- Test the problem before polishing the solution.
- Look for behavior and trade-offs, not enthusiasm.
Run problem interviews
Speak with people who recently experienced the situation. Ask them to reconstruct the last occurrence, what triggered it, what they tried, who became involved, and what the outcome cost.
Avoid explaining the product during the first part of the conversation. A useful interview produces a detailed story even if the person would never buy your proposed solution.
Ask for a meaningful commitment
Evidence becomes stronger when someone gives up time, reputation, data, access, or money. A follow-up meeting, introduction to a decision maker, pilot dataset, or paid experiment is more informative than an email signup.
Choose the smallest commitment that resembles the behavior your business eventually needs. Record refusals and hesitation as carefully as successes.
Keep in mind
- Define a pass/fail threshold before testing.
- Use a small prototype only when it helps test a specific risk.
- Decide what evidence would make you stop or change direction.