A Prototype Can Look Finished Without Being a Finished Product
A polished prototype can illustrate an idea without being a finished service. Learn how to read the label, the example and the limits of a demonstration.

A convincing demonstration can make an idea feel complete. The buttons respond, the pages match, and the sample task reaches an ending. It is easy to mistake that finish for a finished product.
A prototype has a different job. It represents an idea so people can explore and discuss it. Understanding that purpose helps a reader appreciate the demonstration without asking it to prove something it was never built to prove.
TLDR
A prototype is a representation of an idea, not a universal readiness label.
A paper sketch and an interactive model can both be prototypes.
Visual polish does not explain which parts are real or simulated.
A clear demonstration states its purpose and its limits.
The label describes a purpose
The GOV.UK Service Manual describes prototypes as a way to explore, share and test designs. Its examples range from paper sketches to coded prototypes that resemble a live website. That range matters: appearance alone does not tell the audience how an example was made.
A rough sketch may be enough to discuss a layout. An interactive model may help explain movement between screens. Neither label says that every feature of a finished service is present.
A useful distinction: shown versus supplied
Some elements may respond to an action. Others may be fixed examples supplied by the presenter. A demonstration becomes easier to interpret when those differences are named.
A sample event listing, for instance, may use fictional dates and a fixed list of venues. The demonstration can still show how the design presents information. It does not establish that the list comes from a live service.
An illustrative introduction
"This is an interactive prototype of an event-listing page. It shows how someone could browse by neighborhood. The venues are fictional, and the example does not include the rest of the service."
This fictional introduction supplies context before the first click. The audience knows what it is looking at and can keep its questions tied to the idea being shown.
A prototype is allowed to change
The Service Manual describes making multiple prototypes and discarding ideas that do not work well in testing. That is different from treating a polished example as a promise of the final design.
For an educational walkthrough, a note about what changed between examples can be more useful than a claim that one is "nearly done." The note describes the learning; the vague completion label does not.
Frequently asked questions
Does a prototype have to be interactive?
No. A sketch or paper model can represent an idea. The useful form depends on what the author wants to explore or explain.
Does a realistic prototype prove a service is ready?
No. It shows the parts included in that example. A production-readiness assessment is a different activity and outside this explainer.
A practical next step
When watching a demonstration, distinguish the idea being illustrated from assumptions about the finished service. A clear label lets the example do its own job.
Get Board-Ready on AI and Cyber Risk
A 30-minute call. No charge. You'll leave with a clear read on where your oversight stands and what to do about it.


