Why prototype at all instead of just building the product?

Prototypes let designers test ideas with users early and cheaply, when changes are easy, rather than discovering problems after expensive development. They turn abstract design decisions into something concrete that people can react to, which surfaces misunderstandings and usability problems quickly.

Should a prototype be low or high fidelity?

It depends on the question. Low-fidelity prototypes such as paper sketches are best for exploring overall structure, flow, and concepts early on, while high-fidelity prototypes are better for evaluating detailed interactions, visual design, and feel. Many projects move from low to high fidelity as the design matures.

Prototyping and the Design Process

Interaction design proceeds through an iterative process of understanding needs, generating designs, prototyping them at varying fidelity, and evaluating with users, repeating until the design is good enough.

Definition

A prototype is a concrete but limited representation of a design, ranging from a rough sketch to a working interactive mockup, used to explore ideas and gather feedback; the design process is the iterative cycle of discovering requirements, designing alternatives, prototyping, and evaluating that drives a design toward usability.

Scope

This topic covers the structure of the interaction design process and the role of prototyping within it: low- and high-fidelity prototypes, paper prototyping, wireframes, sketches, and interactive mockups; the trade-offs between fidelity, cost, and what a prototype can test; and the principles of early focus on users, empirical measurement, and iterative refinement. It does not cover the formal usability tests and evaluation methods themselves, which are detailed under usability and evaluation, nor the upstream research methods for gathering requirements, covered under user research methods.

Core questions

Why is interaction design fundamentally iterative rather than a single linear pass?
How do low-fidelity and high-fidelity prototypes differ in what they let designers test?
When is paper prototyping more effective than building a working version?
What core principles, such as early focus on users and empirical measurement, underlie usable design?

Key concepts

iterative design cycle
low-fidelity prototype
high-fidelity prototype
paper prototyping
wireframe and mockup
sketching vs prototyping
horizontal and vertical prototypes
early focus on users

Key theories

Principles of usability-oriented design: Gould and Lewis argued that usable systems come from three principles applied throughout development: early and continual focus on users, empirical measurement of usage, and iterative design that revises in response to what testing reveals.
Fidelity trade-offs in prototyping: Low-fidelity prototypes such as paper sketches are fast and cheap and invite criticism of structure and flow, while high-fidelity prototypes look and behave like the final product and are better for detailed interaction and aesthetics; each suits a different question.
Sketching to get the right design: Buxton distinguished sketching, an exploratory activity for finding the right design among many alternatives, from prototyping, which refines a chosen design; both are needed and they happen at different points in the process.

Clinical relevance

Prototyping lets design teams test and refine ideas cheaply before committing to costly engineering, reducing the risk of building the wrong product; it is standard practice in software, hardware, and service design, and is widely used when developing user-facing health and consumer technologies.

History

User-centered design crystallized in the 1980s, with Gould and Lewis articulating its core principles in 1985. Paper prototyping was popularized in the 1990s as a fast way to test interfaces, and Buxton's later writing reframed sketching as a distinct exploratory phase. Iterative prototyping is now embedded in agile and design-thinking practice across the technology industry.

Key figures

Bill Buxton
John D. Gould
Clayton Lewis
Marc Rettig

Seminal works

gould1985
buxton2007
rettig1994

Frequently asked questions

Why prototype at all instead of just building the product?: Prototypes let designers test ideas with users early and cheaply, when changes are easy, rather than discovering problems after expensive development. They turn abstract design decisions into something concrete that people can react to, which surfaces misunderstandings and usability problems quickly.
Should a prototype be low or high fidelity?: It depends on the question. Low-fidelity prototypes such as paper sketches are best for exploring overall structure, flow, and concepts early on, while high-fidelity prototypes are better for evaluating detailed interactions, visual design, and feel. Many projects move from low to high fidelity as the design matures.