Problem-Before-Product Validation Gate
Prove the need and the solution before writing code
- Difficulty
- Easy
- Time to result
- ~weeks to results
- Steps
- 4
- Confidence
- 98%
This framework separates validation into two gates that must pass before full product development begins. First, test whether the target user genuinely experiences the proposed problem, what they do today, and whether the gap is important enough to change behaviour. Second, test whether the proposed product or service is a credible improvement over those alternatives. Interviews can establish the need, while simple mock-ups, wireframes, or prototypes test the response to the solution. The mechanism is risk reduction: each early conversation corrects the direction before money and code harden assumptions into a product. Leary contrasts this with Fanbase, which was developed in stealth for roughly a year to a year and a half and later showed weak engagement, retention, and usage.
Origin
Sarah Leary derived this rule after her team spent years building Fanbase in stealth, then changed its approach while searching for the idea that became Nextdoor. Extracted from The Foundr Podcast.
Core principles
- 01A plausible idea is not proof of a real need
- 02Problem validation and solution validation are separate decisions
- 03Early user feedback reduces the cost of being wrong
- 04Execution matters more than secrecy
How to run it
- 1
Define the need hypothesis
Write down who appears to have the problem, what is missing, and why it matters. Keep it specific enough for potential users to confirm or reject.
Pro tip Ask about current behaviour before describing your product.
Watch out Founder optimism can turn an assumption into an apparent fact.
- 2
Test the problem
Talk with potential users and investigate whether they feel the gap in their lives. Record the alternatives they already use and the strength of their response.
Pro tip Look for users who become animated without being prompted toward a positive answer.
Watch out Polite interest is weaker evidence than a recurring pain or active workaround.
- 3
Test the solution
Show a simple representation of the proposed product and ask whether it would improve on current alternatives. Treat this as a separate test from confirming the problem.
Pro tip Use a mock-up or wireframe before investing in production code.
Watch out A real problem does not automatically make your proposed solution desirable.
- 4
Release the build gate
Start fuller development only when evidence supports both the need and the solution. If either gate fails, revise the hypothesis or return to discovery.
Pro tip Keep the first build just large enough to generate behavioural evidence.
Watch out Do not use enthusiasm inside the team as a substitute for market evidence.
In the wild
Leary's team noticed that people could connect globally through Facebook and professionally through LinkedIn while often not knowing nearby neighbors. They discussed the need with people, used simple mock-ups and wireframes, and then launched a basic prototype in one neighborhood. Positive use led them to test another neighborhood and eventually five before committing the company to the concept.
→ The sequence provided enough problem and solution evidence for the team to build Nextdoor.
Common mistakes
Building in stealth for too long
Avoiding users preserves secrecy but removes the feedback needed to correct an early error in direction.
Combining the two gates
Evidence that a problem exists does not prove that a particular product is the right answer.
Is it for you?
Best for
It is best for founders evaluating a new product before committing a full team or substantial capital.
Not ideal for
It is not ideal when a reversible experiment is cheaper than a round of customer discovery.
From the transcript
“validate whether or not your assumptions about what's missing in the market is true”
“there's a question of does your solution usually a product or service actually meet that need”
“you couldn't start building anything until we had answered those first two questions”
From the episode
343: How To Find The Next Big Business Idea with Nextdoor Co-Founder Sarah Leary
Sarah Leary