Reverse Prototype

01 / UNDERSTAND

The idea

Start with an existing product and create a prototype with selected functionality removed or simplified. Observe whether people can still complete their important tasks. It is a way to investigate a design hypothesis before changing a live service.

A reverse prototype starts from an existing product and removes selected functionality to discover what is truly needed. It can help investigate an overgrown product, a narrower audience or a distinction between core and paid value. Find out what users miss through evidence. A simpler prototype can fail precisely because an infrequent feature is still essential.

02 / RECOGNISE

See it in real products.

Examples of how the principle can appear in an interface.

WeBullEXAMPLE 01

Test the absence of advanced interface elements

WeBull’s optional Lite mode offers a less complex view. Comparing the tasks supported by both modes can reveal which controls different audiences actually need.

View detail

AtomsEXAMPLE 02

Question an assumed prerequisite

Atoms lets people begin creating a habit before account setup. Removing that step from the initial experience tests whether it was necessary at that point.

View detail

04 / APPLY

Put it into practice.

1. 01

   State the simplification hypothesis

2. 02

   Test critical and infrequent workflows

3. 03

   Record what becomes impossible or confusing

CONNECT THE IDEAS

Related principles

Experience Creep

Small additions can accumulate into a complicated experience.

Law of Minimal Effort

Make the useful path easier to follow.

Pareto Principle

Find the few problems or tasks that account for a large share of the impact.