Wireframe

Categories:Design

A wireframe is a deliberately unstyled layout that fixes what goes on a page and in what order, before anyone decides how it looks. Working in grey boxes forces arguments about hierarchy and content to happen while they are still cheap to resolve.

Last reviewed

Why remove the styling on purpose

Colour and imagery hide structural problems and start the wrong conversation. Show a styled page and feedback arrives about the shade of blue. Show grey boxes and feedback arrives about whether the proof belongs above the form.

The economics are the real argument. Reordering a wireframe costs minutes. Reordering the same page after the visual design is approved and built costs days.

Fidelity, and what each level settles
FidelityWhat it answersWhen to use it
LowWhat goes on the page, in what orderEarly, while structure is contested
MidWhether the hierarchy holds with real copyOnce content exists in draft
HighExactly what gets builtAt handoff, before visual design

Fidelity, and how much you need

  • Low fidelity: boxes and placeholder labels, for arguing about structure
  • Mid fidelity: real headings and real copy length, for arguing about hierarchy
  • High fidelity: close to final layout without visual styling, for handoff

Use real content

Lorem ipsum makes every wireframe look balanced, because filler text is uniformly the wrong length. Put the actual headline in, even a rough draft of it, and you find out immediately that the eight-word heading you designed for is really nineteen words.

Why it matters for B2B marketing teams

The B2B argument for wireframes is purely commercial. Restructuring a page costs minutes in grey boxes and days after a design is approved and built. Skipping this stage to move faster is the most reliable way to move slower.

Frequently asked questions

What is the difference between a wireframe and a prototype?+

A wireframe is static and answers what goes where. A prototype is clickable and answers whether the flow works. Wireframes settle structure; prototypes test behaviour, which is why usability testing needs the second one.

Do you still need wireframes if you have a design system?+

Yes, though they get faster. A design system decides what components look like. A wireframe still has to decide which components a page uses and in what order, and that is a content and hierarchy question, not a component one.

Related terms

←Back to Glossary