
Adrian Jordan
-
2 min Read
Overview
Most new products fail for a simple reason: nobody needed them badly enough. Validation is the habit of checking that need before investing in design and code. It does not require a big budget, just a clear question, a handful of real conversations and the willingness to change direction.
My seven steps are simple. Write down the problem in one sentence, find ten people who have it, listen to how they solve it today, sketch the smallest useful solution, show it to them, ask for a real commitment and only then decide whether to build. Each step takes days, not months.
Testing an idea early is the cheapest way to build the right thing
Describe the problem in one sentence.
Talk to ten people who have it.
Show a rough sketch, not a finished app.
Ask for a real commitment.
Adrian Jordan
Listening before designing
The most useful interviews focus on what people already do, not on what they say they might do. Ask about the last time they faced the problem, what they tried and what it cost them. Those stories reveal whether the need is urgent, and they often point to a simpler solution than the one you imagined.


Deciding what to build
By the end of the seven steps you have evidence instead of hope. Sometimes the answer is to build, sometimes to adjust, and sometimes to stop.
Each of those outcomes is a win, because it saves time and money you would otherwise spend on guesswork.
Validate first, then build with confidence.



