Find a repeatable customer pattern
Look for the same problem, trigger, workaround, and decision process across relevant cases. Record counterexamples. A broad audience with different needs may hide a more promising, narrower segment.
Test a meaningful commitment
Offer a transparent prototype task, discovery follow-up, or bounded pilot. Match the commitment to the question: an email signup tests interest, while repeated use tests something different.
- Document who accepted, declined, and why.
- Check whether the buyer and user are different people.
- Identify access, workflow, or delivery barriers.
- Choose what evidence would justify a larger build.
Set the next milestone
A useful milestone is a clear customer brief and evidence supporting a specific first use case. Seek product discovery or domain expertise when an assumption remains hard to test. Compare programs on learning support and relevance, and confirm current eligibility with the provider.
Questions, answered.
When is an idea fully validated?
Validation is not a permanent certificate. Evidence can justify the next investment of time or resources, while new assumptions appear as the business develops.