Idea Validation

What Idea Validation means in practice

Validation exists to make being wrong cheap. Most failed products were not badly built — they were built for a problem nobody urgently needed solved. Validation front-loads that discovery so the expensive discovery never happens.

The core discipline is distinguishing evidence from encouragement. Compliments, survey enthusiasm and waitlist signups cost the respondent nothing, which is exactly why they correlate so weakly with revenue. Evidence involves cost: money paid, a pre-order placed, a meeting given, an existing workflow changed. Anything free is interest, not validation.

Validation is not a single test but a sequence, and each stage should be cheaper than the one it protects you from. Establish that the problem is real and urgent, then that your specific solution is wanted, then that people will pay your price, then that you can reach them repeatably. A strong answer at one stage says nothing about the next.

Worked example

Two founders validating the same scheduling tool for clinics.

• Founder A: surveys 200 clinics; 68% say they would 'definitely use' it. Builds for five months. Converts 3 customers.
• Founder B: asks 20 clinics for £200 upfront for early access. Four pay. Builds for six weeks with four paying users guiding scope.
• Founder A gathered opinion; Founder B gathered commitment.

Takeaway: The 68% approval was worthless because agreeing to a survey costs nothing. Four payments of £200 proved more than 136 positive responses.

Common mistakes

• Treating survey responses and verbal enthusiasm as validation when neither costs the respondent anything.
• Asking leading questions that invite agreement rather than describing the current workflow.
• Validating with people who are easy to reach rather than people who would actually buy.
• Building the full product to 'properly test' an idea, which is the expense validation exists to avoid.

Related tool: Validate your idea.

Related terms

• Customer Discovery — Customer discovery is the practice of interviewing potential customers about their existing problems and workflows — rather than pitching a solution — to learn whether a problem worth solving genuinely exists.
• Problem-Solution Fit — Problem-solution fit is the stage at which you have confirmed a real, urgent problem exists and that your proposed solution genuinely addresses it — the milestone before product-market fit.
• Minimum Viable Product — A minimum viable product (MVP) is the smallest version of a product that delivers real value to real users and produces reliable learning about whether the underlying idea works.
• Product-Market Fit — Product-market fit is the point where a product satisfies a real, urgent demand well enough that customers adopt it, keep using it, and tell others — so growth starts pulling rather than being pushed.