Run a painted door test
Measure demand for a feature before you build it, using a fake entry point and an honest follow up.

What it is
A painted door test puts the entry point to a feature in your product before the feature exists. A button, a menu item or a banner. When someone clicks, you tell them it is coming and ask if they want to hear about it.
When to use it
Use it when building costs weeks and you are unsure anyone wants the thing. It will not tell you whether people will love it. It tells you whether they care enough to look.
Be honest with users
The follow up should not pretend the feature works. Say that it is not ready, thank them and offer a short waitlist. Never collect payment details for something that does not exist.
Set it up
- Create a flag that shows the entry point to a random half of eligible users.
- Log exposure when the entry point is rendered, not when the page loads.
- Log the click and the waitlist sign up as separate events.
- Set a guardrail on the metric the entry point might distract from.
Read the result
Compare click through against a benchmark from similar entry points in the same place in your product. A click rate near the benchmark is neutral. Twice the benchmark is a reason to build.
Follow up with people
The best part of the test is the list of people who raised their hand. Interview five of them before you write a line of code.
More playbooks

Run your first checkout test
A step by step plan for testing a checkout change without risking revenue.

Test your pricing page
How to test plan layout, anchoring and copy on a pricing page without changing what anyone pays.

Improve onboarding activation
A playbook for finding your activation event and running a steady series of onboarding tests.