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.

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.