What is a Prototype?

TL;DR

• A prototype makes an idea tangible enough to explore or test.
• It can range from rough sketches to realistic interactive simulations.
• A prototype is not necessarily production code.
• Fidelity should match the question the team needs to answer.
• Prototypes reduce uncertainty before expensive implementation.

What does a prototype do?

A PRD can describe a checkout flow. A prototype lets someone experience it.

By clicking through the sequence, teams can discover missing states, confusing transitions, and assumptions that were invisible in text.

Types of prototypes

Low-fidelity

Rough structure and flow used for early exploration.

High-fidelity

Realistic visuals, content, and interactions used when behavior or presentation needs believable testing.

Coded prototype

A functional implementation used when technical behavior is central to the question.

Prototype vs. mockup

A mockup is usually a static visual representation. A prototype emphasizes experience and interaction.

Prototype vs. MVP

A Minimum Viable Product is a real minimum offering intended to test important assumptions through actual usage. A prototype can be disposable and may simulate functionality.

How do teams use prototypes?

• align stakeholders
• test user flows
• evaluate interaction concepts
• run usability tests
• surface edge cases
• clarify engineering handoff

Common mistakes

Building too much fidelity too early

Polish can waste time and make weak ideas feel settled.

Prototyping without a question

Know what uncertainty the artifact should reduce.

Showing only the happy path

Important product behavior often lives in alternate states.

The bottom line

A prototype asks: what do we need to make tangible now so we can learn before we build the real thing?

Related terms

Prototyping · Wireframe · Mockup · Usability testing

Relevant Figr resource

Read Prototyping for Product Teams for the complete workflow.