# Prototype

A prototype is a selective representation of a proposed product used to explore an idea, test an assumption, or communicate behavior.

- Type: artifact
- Domain: Experience & interface
- Level: Foundational
- Last reviewed: 2026-10-20
- Original: [Soroush’s Product Wiki](<https://wiki.soroush.uk/topic/prototype/>)

## What it means

A prototype makes part of a possible product concrete enough to investigate a question. It can be a paper simulation, clickable screens, a coded interaction, or a physical model. It deliberately leaves things out. Prototype fidelity describes its realism; a minimum viable product delivers value in real use and has a different operating burden.

## Why it matters

Teams can discover a misunderstanding or an impractical interaction before committing to a full implementation. The value comes from a decision the prototype informs, not from the number of screens or how convincingly it resembles a finished product.

## When to use it

Use a prototype when observing an interaction or inspecting a representation will reduce meaningful uncertainty. A conversation or sketch may be sufficient for a simple alignment question. Production reliability and sustained demand require additional evidence.

## How it works

1. Write the assumption, intended decision, and observations that would change your mind.
2. Choose the smallest scope and necessary fidelity for that question.
3. Build representative tasks and data, documenting simulated boundaries.
4. Pilot the prototype to separate artifact failures from concept failures.
5. Observe relevant users or technical behavior and record evidence.
6. Revise, discard, or implement the idea according to the learning.

## A practical example

A travel team creates a three-screen prototype of changing one room’s checkout date in a multi-room booking. Participants repeatedly assume the change applies to all rooms. The team revises room identity and confirmation before implementing the booking logic.

## Where it breaks

Simulated data and responses can hide constraints. A successful session does not prove market demand or production readiness. Prototype code may omit security, accessibility, and maintainability work and should not quietly become production code.

## Common mistakes

- Building the whole product before testing the uncertain part.
- Explaining every action to participants and calling it validation.
- Treating prototype code as ready to ship.

## Sources

1. [Making prototypes](<https://www.gov.uk/service-manual/design/making-prototypes>) — Government Digital Service · Government guidance
2. [UX Prototypes: Low Fidelity vs. High Fidelity](<https://www.nngroup.com/articles/ux-prototype-hi-lo-fidelity/>) — Nielsen Norman Group · Professional guidance

## Related topics

- [Prototype Fidelity](<https://wiki.soroush.uk/topic/prototype-fidelity/>)
- [Usability Testing](<https://wiki.soroush.uk/topic/usability-testing/>)
- [Minimum Viable Product](<https://wiki.soroush.uk/topic/minimum-viable-product/>)
