What is Prototyping?

TL;DR

• Prototyping is a process, while a prototype is an artifact.
• Teams prototype to reduce uncertainty and make ideas testable.
• Fidelity should increase only when the question requires it.
• Prototyping supports exploration, validation, and communication.
• Strong prototyping is iterative rather than a one-time deliverable.

Why do teams prototype?

Because changing a flow in a prototype is usually cheaper than changing production code after launch.

Prototyping helps teams expose missing logic, compare alternatives, test usability, and align around behavior before implementation hardens decisions.

What does the prototyping process look like?

1. Define the question or risk.
2. Choose the minimum fidelity needed.
3. Build enough of the flow to test the assumption.
4. Put it in front of users or stakeholders.
5. Observe what breaks or remains unclear.
6. Revise the prototype.
7. Increase fidelity only when useful.

Prototyping vs. wireframing

Wireframing focuses on structure and layout. Prototyping focuses on simulating how the experience works.

Prototyping vs. product development

A prototype can intentionally fake data or interactions to answer a question. Production development must handle reliability, security, performance, and maintainability.

Common mistakes

Trying to make the prototype production-perfect

The goal is learning, not code quality, unless technical feasibility is what you are testing.

Skipping important states

A realistic prototype should cover the states relevant to the research question.

Never testing with anyone

A prototype viewed only by its creator provides limited evidence.

The bottom line

Prototyping asks: what can we simulate cheaply now to learn something valuable before committing more time?

Related terms

Prototype · Wireframe · Iteration · Usability testing

Relevant Figr resource

Read Prototyping UX Design for an applied workflow.