Validation for Product Managers
Validation is the step where a product manager tests whether an idea is worth building before investing in full development. It uses prototypes, fake-door tests, concierge trials and small experiments to check desirability, usability and feasibility, with a clear hypothesis and success threshold set in advance.
Stage: Discovery · Part of the Product Manager roadmap · Last reviewed 19 November 2026
What to learn in Validation
- State a falsifiable hypothesis with a success threshold
- Choose between a prototype, fake door and concierge test for a risk
- Run a usability test with five participants and record findings
- Interpret results and decide whether to persevere, pivot or stop
- Avoid confirmation bias when reading early feedback
Validation interview questions
What is a fake door test?
A fake door test adds a button or landing page for a feature that does not yet exist and measures how many people click or sign up. It checks demand cheaply. Users who click are told the feature is coming, and ethics require honest messaging.
Why set a success threshold before running an experiment?
A threshold fixed beforehand stops the team from reading any result as a win. It forces a decision rule such as proceeding if at least a set share of visitors sign up, which makes the experiment useful rather than decorative.
Where Validation fits in the Product Manager roadmap
Validation belongs to the Discovery stage (beginner level), which takes about 4 hours. Build the right thing.
Other units in this stage
Back to the full Product Manager roadmap