038Pattern
Reverse Prototype
A method of removing existing functionality, views and steps, to see what the minimal viable product is.
Why it matters
If you're starting with nothing, and designing your first product, you'd likely start by asking what the necessary features were to deliver value (and your vision).
This process is often named an MVP (minimal viable product).
A reverse prototype is a method of reaching this same MVP, but starting with a live product and removing unnecessary functionality .
You may wonder why (and when) this would be necessary, so let's give a few examples:
• You've been building a product for a growing audience, but over time have built many features that you're not convinced are valuable to every user. You may aim for a niche-specific MVP . • Your product has been built over decades, as users, tastes, industry best-practice, technology and context has changed. You now no longer know what's necessary , and what people just are used to having. • You're trying to paywall specific features , but aren't sure what's necessary for 'core value', and what are paid 'nice-to-haves'.
Churn:
• By reducing complexity, you may also reduce frustration and confusion, thereby reducing churn . • It is also possible that by removing features, you increase churn , as some users no longer feel that it's sufficient for their workflow.
What to inspect
- Check whether the UI still supports this: You've been building a product for a growing audience, but over time have built many features that you're not convinced are valuable to every user. You may a…
- Check whether the UI still supports this: Your product has been built over decades, as users, tastes, industry best-practice, technology and context has changed. You now no longer know what's necessa…
- Check whether the experience reflects this: You're trying to paywall specific features , but aren't sure what's necessary for 'core value', and what are paid 'nice-to-haves'.
- Check whether the experience reflects this: By reducing complexity, you may also reduce frustration and confusion, thereby reducing churn .
Common anti-patterns
- Assuming users consciously notice every place where "A method of removing existing functionality, views and steps, to see what the minimal viable product is" could apply.
- Dense copy and parallel actions that increase mental effort unrelated to the user’s goal.
- Ignoring downstream effects on churn when shipping this pattern.
Critique prompts
- You've been building a product for a growing audience, but over time have built many features that you're not convinced are valuable to every user. You may aim for a niche-specific MVP .
- Your product has been built over decades, as users, tastes, industry best-practice, technology and context has changed. You now no longer know what's necessary , and what people just are used to having.
- You're trying to paywall specific features , but aren't sure what's necessary for 'core value', and what are paid 'nice-to-haves'.
- By reducing complexity, you may also reduce frustration and confusion, thereby reducing churn .
- Where on this screen would "Reverse Prototype" show up as friction or misunderstanding?
- What would a first-time user misunderstand here in under five seconds?