Early in my product career, I believed that validating an idea meant building it.
If customers requested a feature, we discussed requirements, designed screens, wrote tickets, and started development. Weeks or months later, we launched and finally learned whether people actually wanted it.
Looking back, that process was incredibly expensive.
Today, if I can validate demand before writing a single line of code, I will.
That’s where fake door tests come in.
They are one of the simplest and most effective ways to test whether users genuinely want something before investing significant time and resources into building it.
What Is a Fake Door Test?
A fake door test is exactly what it sounds like.
You create the appearance of a feature that doesn’t actually exist yet.
Users can see it and attempt to access it, but instead of reaching a working feature, they receive a message such as:
- “Coming soon”
- “Join the waitlist”
- “We’re currently building this”
- “Request early access”
The goal is not to trick users.
The goal is to measure genuine interest before committing development effort.
Think of it as testing demand before building supply.
Why Product Teams Need Fake Door Tests
One of the biggest risks in product development is solving a problem nobody cares about.
Teams often mistake:
- Customer requests
- Internal opinions
- Stakeholder enthusiasm
For actual demand.
But there is a huge difference between someone saying they want a feature and someone taking action to use it.
Fake door tests help bridge that gap.
Instead of asking users what they might do, you observe what they actually do.
And behavior is usually more reliable than opinions.
A Simple Example
Imagine you’re working on a project management platform.
Several customers mention that they would like an AI-powered meeting summary feature.
You have two options.
Option 1
Spend three months building it.
Launch it.
Then discover only 2% of users actually use it.
Option 2
Add a button labeled:
“Generate AI Meeting Summary”
When users click it, they see:
“This feature is coming soon. Join the waitlist.”
Now you can measure:
- Click-through rate
- Interest by user segment
- Number of waitlist signups
- Frequency of interaction
Within days, you have valuable evidence about demand.
Without building the feature.
What Fake Door Tests Actually Validate
A fake door test doesn’t prove that users will love the finished feature.
What it validates is something equally important:
Intent.
It answers questions like:
- Are users interested?
- How many users care?
- Which users care most?
- Is the problem worth solving?
These insights help teams prioritize more effectively.
Why I Like Fake Door Tests
The biggest advantage is speed.
A fake door test can often be implemented in a few hours.
Compare that with:
- Design work
- Engineering effort
- QA testing
- Release planning
The learning-to-effort ratio is incredibly high.
As product managers, our job isn’t to build faster.
It’s to learn faster.
Common Mistakes When Running Fake Door Tests
Not all fake door tests are useful.
One mistake is placing the fake door in a highly visible location where users click simply because it’s prominent.
Another mistake is measuring clicks without considering context.
For example:
A click doesn’t necessarily mean strong demand.
A click followed by a waitlist signup is usually a much stronger signal.
The goal isn’t collecting vanity metrics.
The goal is understanding real customer interest.
The Ethical Side of Fake Door Tests
Some teams worry that fake door tests feel deceptive.
I think transparency matters.
If a user clicks a feature that isn’t available, the response should be honest.
Tell them:
- The feature is being explored
- You’re gathering interest
- They’re welcome to join a waitlist
Most users understand and appreciate being involved in the product’s evolution.
The key is never pretending the feature works when it doesn’t.
When Fake Door Tests Work Best
I’ve found them especially useful for:
- New feature ideas
- Expansion opportunities
- Pricing experiments
- New workflows
- Product market fit exploration
They are particularly valuable when development costs are high and uncertainty is even higher.
What Happens After the Test?
The test itself is only the beginning.
Once demand is validated, product teams should dig deeper.
Talk to interested users.
Understand:
- Why they clicked
- What problem they’re trying to solve
- What alternatives they’re using today
The fake door identifies interest.
Customer conversations uncover the real opportunity.
Final Thought
One of the hardest lessons in product management is realizing that building something does not prove it was worth building.
Learning should come before investment whenever possible.
Fake door tests embody that principle perfectly.
They allow teams to test demand, reduce risk, and make smarter decisions before committing valuable resources.
Because the cheapest feature to build is the one you discover nobody wanted in the first place.
Leave a Reply