Fakedoor Test

A testing method to quickly verify user interest and behavior hypotheses towards a not yet existing service or functionality by creating an offer and measuring conversions.


A Fakedoor Test is a validation technique where a non-functional feature (the "fakedoor") is introduced to gauge user interest. By tracking clicks, interactions, or feedback, businesses can test demand without fully building the feature. Fakedoor Tests are valuable in product development, lean startups, and innovation projects, where they help in prioritizing features, reducing development risks, and ensuring that efforts are focused on what users truly want or need.

Suitable for

  • Quick verification of user behavior hypotheses
  • Verification of interest in a product or service before launching a minimum version
  • Teams that have already gone through the ideation and design phase


Test Objectives

Clearly defined objectives for the Fakedoor Test, outlining the goals and purpose of the study and what the team expects to learn from the test.

Target User Profiles

Description of the ideal participants for the study, including demographics, characteristics, and behaviors that represent the user base for the product.

Test Scenarios

Creation of realistic use-case scenarios for the test, including specific tasks or actions the user would typically perform in order to interact with the fakedoor elements.

Fakedoor Design

Designs and mock-ups of the fakedoor elements (e.g., buttons, calls to action, links) that will be inserted into the product, simulating the future features or functionality being tested.

Study Protocol

Detailed outline of the steps and procedures to be followed during the test, including instructions for moderators, interactions with participants, and sequencing of tasks or scenarios.

Data Collection Plan

Methods and tools to be used for collecting and recording data during the study, such as user interaction data, click rates, time on task, satisfaction ratings, and any qualitative feedback.

Pre-test Survey

A short survey to gather baseline information from participants before the test, including demographics, prior experience with the product, and any relevant attitudes or beliefs.

Post-test Survey

A survey to collect user feedback after the test, including questions related to user satisfaction, ease of use, perceived usefulness of the fakedoor feature, and any suggestions for improvement.

Test Findings Report

A comprehensive report detailing the findings from the Fakedoor Test, including data analysis, key takeaways, user feedback, and recommendations for product improvements based on the results.

Recommendations and Next Steps

A summary of the actionable insights gained from the test, including suggested design changes, feature edits, and a prioritized list of product updates to be made based on user feedback and observed behaviors.



Identify the Hypothesis

Determine the specific feature or product you are looking to test and what its value proposition is. Form a clear hypothesis about the potential demand, usability, or functionality of the product or feature.


Design the Fakedoor

Create a simple, realistic representation of the proposed feature or product. This could be a button, link, or banner that appears to be functional but does not actually lead to a fully-developed feature or product. The design should be convincing enough for users to believe it is real and should entice them to interact with it.


Integrate the Fakedoor

Incorporate the fakedoor into the appropriate location, such as your website or app. Ensure that it is seamlessly integrated into the user flow and does not disrupt the overall user experience or create friction.


Monitor User Interactions

Track user interactions with the fakedoor using analytics tools, such as click-through rates and hover states. Observation of users interacting with the fakedoor can also be valuable for collecting qualitative data.


Capture User Feedback

When users interact with the fakedoor, present them with a message, survey, or form explaining that the feature or product is in development and that their feedback is valuable. Collect user input regarding their expectations and desires for the tested feature or product.


Analyze Results

Evaluate the quantitative and qualitative data gathered from user interactions and feedback. Determine if the hypothesis was validated or if user responses indicate a different direction should be taken in the feature or product development.


Iterate and Refine

Based on the results and insights gathered, adjust your hypothesis, feature design, and fakedoor as necessary. Repeat the fakedoor test process until you achieve desired results and are confident in moving forward with full development.

Support the project

Donate to UX Methods today. As the largest UX method database on the web, your contributions will help maintain our platform and drive exciting new features. Keep the resource free, up-to-date, and comprehensive for everyone. Make a difference in the UX community!