The real cost of ignoring prototyping
This is cheap to get right at the start and expensive to retrofit. Nobody bills you for neglecting prototyping. The cost shows up somewhere else.
The measurable part of design is whether people can find what they came for and act on it without hesitating. Most teams find the first pass takes an afternoon and the maintenance takes minutes a month.
Where the cost lands
- Time spent on work that should not have been necessary
- Enquiries that quietly never arrive
- A clickable prototype surfaces confusion no static mockup will
- Rework, once the problem is finally visible
Prototypes are for learning, not for reuse as production code. The teams that handle this well are rarely the ones with the biggest budgets. The failure mode is not doing it wrong, it is doing it once and assuming it stays done.
What to do next
Test with five people and you will find most of the problems. This is the sort of thing that compounds, quietly, in both directions. The version that survives contact with a real deadline is the simple one.
What this looks like day to day
Design decisions are the ones clients feel most confident arguing about, which makes it worth separating taste from evidence early. Three things worth confirming about prototyping before you move on:
- Someone can say what the current setup is without going to look
- A clickable prototype surfaces confusion no static mockup will — and you know whether that is true here
- There is a way to tell whether the last change to this helped
If you want a second opinion on how yours is set up, ask.