Rapid Prototyping vs Minimum Viable Product (MVP)

Definition

Rapid prototyping is the practice of quickly creating interactive, low-fidelity models of a product to validate ideas before writing expensive production code. By simulating the user experience using design tools (like Figma), product teams can run user tests and gather feedback in days rather than months. If a picture is worth a thousand words, a prototype is worth a thousand meetings.

Common trap

The trap is treating a prototype like a final design. Teams often get bogged down in 'pixel-perfection'—obsessing over colors, shadows, and exact fonts—during the prototyping phase. This transforms a 2-day rapid learning exercise into a 4-week design bottleneck, defeating the entire purpose of 'rapid' validation.

Practical use

Define the core user flow you want to test. Build a clickable mockup using only grayscale boxes and standard fonts within 48 hours. Put it in front of 5 target users and ask them to complete a specific task. Watch where they click and where they get confused.

Formula

Definition

An MVP is the smallest version of your product that delivers real value to early users and generates validated learning. The goal isn't a 'crappy first version' — it's the fastest path to proving whether customers will pay for your solution. 74% of startups fail because they build something nobody wants.

Common trap

The trap is building too much. Founders spend 6-12 months building a 'complete' product before showing it to a single customer. By then, they've burned through runway and assumptions. Dropbox's MVP was a 3-minute demo video — it validated demand before writing a single line of code.

Practical use

Define the ONE core problem you solve. Build only the features needed to test if users will pay for that solution. Launch within 4-6 weeks. Your MVP should be embarrassingly simple — if you're not embarrassed by v1, you launched too late.

Formula