Three myths about wireframing

It comes up on almost every project, usually later than it should. A few things about wireframing that get repeated more often than they get checked.

Consistency is the quiet half of design work: it rarely gets complimented, and its absence is noticed immediately. Assume whoever inherits this will have half your context and none of your patience.

“It only matters for big sites”

Wireframes settle structure before anyone argues about colour. That sounds obvious written down. It is still the thing most often skipped. It rarely shows up as a line item, which is exactly why it slips.

“We can deal with it after launch”

Sometimes true, usually expensive. None of that requires a large budget, only a decision and someone to own it.

“Our platform handles it”

An hour of wireframing saves a week of redesign. The cost of getting this wrong is rarely visible on the day it happens. Budget a little time for it every quarter and it never becomes a project of its own.

The short version

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 wireframing before you move on:

• Someone can say what the current setup is without going to look
• Wireframes settle structure before anyone argues about colour — and you know whether that is true here
• There is a way to tell whether the last change to this helped

The point is not perfection, it is knowing which of these you have consciously chosen to skip.