prototyping-pretotyping

Pretotyping helps you validate demand before building by running cost-effective experiments like fake door tests to gauge interest. This approach tests your riskiest assumptions early by collecting real user data before writing any code.

Pretotyping tests core demand and feasibility assumptions with minimal artifacts like fake doors, while prototyping builds paper, clickable, or coded models to test workflow and usability. Both methods guide the decision to pivot, persevere, or iterate based on collected experiment data.

Choosing the right MVP method involves matching fidelity levels to your riskiest assumptions and resources. Use fake door tests for demand, concierge MVPs for workflow validation, or clickable prototypes for usability, ensuring the experiment structure fits your specific assumption testing needs.

Yes, fake door tests can validate pricing by displaying costs on a sign-up landing page. For feasibility assumptions, you might select coded prototypes or concierge MVPs instead, structuring the experiment to collect specific data that informs your decision to pivot, persevere, or iterate.

You should avoid pretotyping when your riskiest assumptions require testing complex workflows or technical feasibility rather than basic demand. In these cases, building a coded prototype or a concierge MVP provides deeper data collection needed to decide whether to persevere or iterate.