Keeping a Prototype Honest

A prototype is easy to misunderstand because it resembles the thing we hope to make. Put a screen inside a device frame, add realistic copy, smooth the transitions, and people begin offering feedback as though the product exists. Sometimes that is useful. Often it means the prototype has become persuasive before it has become informative.

I have built too many prototypes that were good at looking inevitable. They made an idea comfortable to approve while leaving its difficult question untouched: will someone understand this interaction, will the material survive daily handling, will the information still matter at the moment it appears?

Name the uncertainty first

The most productive first sentence in a prototype brief is not a feature description. It is a risk.

For a small weather display, the risk might be whether a glanceable forecast can be understood without reaching for a phone. For a writing tool, it might be whether returning to an unfinished draft feels inviting or burdensome. For a lamp, it may be whether the control can be found in the dark without turning the object into a machine panel.

Once the uncertainty is explicit, fidelity becomes easier to choose. A paper sketch is enough to test hierarchy. A working sensor in an ugly enclosure may be required to test placement in a room. A polished visual design is justified only when visual trust, tone, or comprehension is the actual question.

Fidelity has a cost

Polish does not merely consume time. It changes the feedback a prototype can receive. People hesitate to criticize an object that appears finished, or they focus on corner radii and wording because those are the decisions the artifact presents as available.

Making unfinished parts legible helps redirect that attention. Placeholder content is labelled as such. A taped enclosure does not pretend manufacturing has been solved. A single developed workflow sits beside plainly inactive paths. This is not carelessness; it is a way of pointing toward the decision still in motion.

Three questions help clarify what a prototype actually needs to be:

• What decision will this prototype allow me to make?
• What is the least convincing artifact that can answer it reliably?
• Which visible detail might accidentally imply a decision already made?

💡 If you cannot answer the first question, building more usually creates an object to admire rather than evidence to use.

Let failure remain cheap

An honest prototype is permitted to be wrong. More than that, it is structured so that being wrong is useful. A test session that shows an interaction is unnecessary can save weeks. A cardboard model that reveals awkward reach can prevent an elegant but unusable enclosure. The discovery feels less like loss when the artifact was never expected to earn its survival.

This changes how I present prototypes. Instead of asking "Do you like this?" I describe the question and watch for the moment the artifact answers it. Preference still matters later. Early on, behavior and hesitation offer cleaner information.

Enough finish to learn

There is a lower limit to roughness. A prototype that is confusing because it is carelessly built cannot tell me whether the underlying idea is confusing. The craft is to finish exactly the aspects under examination and leave the rest lightweight.

That balance is less glamorous than a fully rendered concept, but it is more generous to the eventual product. A prototype should not audition for praise. It should expose the next true decision while it is still inexpensive to change our minds.

🗒️ In short, the goal is not to make the prototype look ready. It is to make the right question answerable.