Validate the problem before funding the full solution
Validation means collecting evidence that a specific group experiences the problem and will change behavior to solve it. Compliments and survey interest are weak evidence.
Evidence ladder
From weaker to stronger:
- interviews about past behavior
- observation of the current workaround
- waitlist or request for access
- design-partner commitment
- paid manual service
- pre-order or paid pilot where lawful and clearly described
- repeat use of a limited product
Interview well
Ask about the last time the problem happened, what the person did, what it cost, who approved the solution, and why existing alternatives were rejected. Avoid pitching during the interview.
Define a decision rule
Before the test, state what result would justify building, changing direction, or stopping. The threshold must fit the market and business model; there is no universal validation score.
Be honest with buyers
Do not take payment for capabilities that do not exist without clear terms, refund handling, and delivery expectations.
Validation does not guarantee success. It reduces one category of uncertainty before the expensive work begins.
Fact-check sources
- Editorial framework; no external benchmark asserted
Sources and product documentation can change. Recheck time-sensitive pages on the publication date.