Wireframing: what to get right first

There is no clever trick in this one, just a handful of decisions worth making deliberately. If you only fix one thing about wireframing this quarter, make it the first item below.

Consistency is the quiet half of design work: it rarely gets complimented, and its absence is noticed immediately. If two people in the business would answer this differently, that gap is the actual problem.

Start here

Wireframes settle structure before anyone argues about colour. None of that requires a large budget, only a decision and someone to own it. Most teams find the first pass takes an afternoon and the maintenance takes minutes a month.

Then this

Low fidelity keeps feedback focused on flow. There is a version of this that is over-engineered, and it is worth avoiding. Assume whoever inherits this will have half your context and none of your patience.

Eventually

An hour of wireframing saves a week of redesign. The teams that handle this well are rarely the ones with the biggest budgets. It is the sort of thing that looks like polish right up until it costs you an enquiry.

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

If you want a second opinion on how yours is set up, ask.