Prototyping

What it means

Prototyping is quickly building a simplified but clickable or physical version of a product to test an idea with users before investing in development. It exposes flaws in the concept while fixing them is still cheap and does not require reworking finished code or production.

Prototypes vary in fidelity. Paper sketches and wireframes test structure and flow, clickable prototypes in design tools simulate use, and functional prototypes contain some real logic. The choice depends on what question the prototype needs to answer.

Prototyping is at the heart of design thinking and closely related to the MVP. The difference is that a prototype serves learning and is often thrown away, while an MVP is the simplest version real customers use and may pay for.

How it works in practice

When designing a new service, such as an accounting firm's client portal, a clickable prototype of the key screens is enough to start. Five to ten tests with real clients reveal where they get lost, what they misunderstand and what they miss, without a single line of code.

Tests should have clear tasks, such as find the March invoice or upload a document, and the focus should be on behaviour rather than opinions. Users often say they like the design and then fail the task; the latter is what counts.

The findings feed into the next iteration until the concept is sufficiently validated. Only then does development begin, building on the UX insights from testing. If the tests show the idea does not work at all, that is a cheap reason to pivot.

What to watch out for

A prototype that is too polished can backfire. If it looks like a finished product, the sponsor or customer expects launch within days, and users comment on colours instead of flow. Fidelity should match the project phase.

A prototype is not a product. Code written in haste to test an idea rarely meets security, performance and maintainability standards; putting it into production without reworking it is a frequent source of later problems.