Wireframing for small teams

There is no clever trick in this one, just a handful of decisions worth making deliberately. Most advice about wireframing assumes a team that does not exist at your size. Here is the version that does not.

Consistency is the quiet half of design work: it rarely gets complimented, and its absence is noticed immediately. The teams that stay on top of it are the ones who put it on a calendar rather than a wish list.

What to keep

Wireframes settle structure before anyone argues about colour. Where this goes wrong is almost never a lack of knowledge. The teams that stay on top of it are the ones who put it on a calendar rather than a wish list.

What to drop

Process that exists to coordinate ten people is overhead when there are two of you. Getting it slightly wrong is survivable. Ignoring it entirely is not.

How we handle it

An hour of wireframing saves a week of redesign. There is a version of this that is over-engineered, and it is worth avoiding. The failure mode is not doing it wrong, it is doing it once and assuming it stays done.

The short version

The measurable part of design is whether people can find what they came for and act on it without hesitating. Three things worth confirming about wireframing before you move on:

• Someone can say what the current setup is without going to look
• An hour of wireframing saves a week of redesign — and you know whether that is true here
• There is a way to tell whether the last change to this helped

Pick the one that would hurt most if it failed, and start there.