Book a call

Glossary

Wireframe

A wireframe is a plain drawing of a screen or page that shows what goes on it, in what order and how it connects to the next, before any colour, type or imagery is decided.

  1. Queue title and count12 waiting, oldest first
  2. FiltersTeam, amount, policy flag
  3. Claim rowsWho, what, amount and any flag
  4. Detail panelReceipt and history, opened from a row
  5. Approve or returnPolicy warning sits above it
A wireframe of an expenses approval screen, top to bottom, with no colour, type or imagery yet.

Wireframe in detail

Also called
Low-fidelity design, Lo-fi wireframe, Screen blueprint
Topic
Product
Updated

What it is

A wireframe deals with structure. It uses grey boxes, lines and plain labels to show which pieces of content and which controls a screen holds, which come first, and what sits behind a click. Leaving out colour and type is deliberate: it keeps the review on whether the screen works.

Fidelity varies. Some wireframes are sketches on paper, others are tidy greyscale screens in Figma with real labels. They come after the flows are agreed and before visual design, and a set of them is often linked into a wireflow, which shows how one screen leads to the next. Once the structure holds, the wireframes become finished designs, and the finished designs become a clickable prototype or the build.

Why it matters

Moving a table above a chart takes a minute in a wireframe and a week once the screen is designed, built and reviewed. Wireframes let a team test structure while it is still cheap to change, with stakeholders and with the people who will use the product. They also keep the visual debate for later, so feedback on the first round is about what is missing and where it sits.

How we do it

Wireframes come after the flow and before any visual design. We trace the task through the product first, then draw the screens it needs, so navigation and hierarchy get tested while they are still cheap to move. We fill them with real content: the longest title, the most detailed record, the field that is sometimes empty.

We test them with representative users where the scope allows and check feasibility with your engineers. Once the structure holds, we design every screen on your content with its loading, empty and error states, and the components your developers build from. A focused piece of product design on one area takes four to six weeks, and product design starts from $10,000 a month.

An example

Say a finance team is redesigning the screen where managers approve expense claims. The first wireframe puts the approve button beside each row. A manager reviewing it points out that she approves claims that break policy without noticing, because the warning only appears after she clicks. The second version shows the policy flag in the row and puts the warning directly above the button. Nobody has chosen a colour yet.

Common mistakes

  • Filling it with lorem ipsum. Placeholder text hides the long supplier name, the claim with eleven receipts and the label that does not fit, which are the things a wireframe is there to catch.
  • Wireframing screens one at a time. A screen that works alone can still strand someone, so draw how each one connects to the next.
  • Drawing only the full state. The empty queue, the failed load and the account with no permission need wireframes too, or engineering ends up designing them.
  • Adding brand colour too early. Once colour and type appear, reviewers start judging the look and stop questioning the structure.

Wireframe vs mockup

A wireframe shows the structure of a screen in plain greyscale before visual design starts, and a mockup is a static picture of the same screen with its final colour, type and imagery.

WireframeMockup
ShowsContent, order and controlsHow the finished screen looks
FidelityLow: boxes, lines, plain labelsHigh: colour, type, imagery
Feedback onWhat is there and whereVisual design and brand
ComesAfter the flows, before visual designAfter the wireframes are agreed

Questions

What people ask about wireframe.

  1. A wireframe is a plain layout of a screen that shows structure and content. A mockup is a static picture of the same screen with its final visual design. A prototype is something people can click or use, at any fidelity, built to test how the design works. Many projects make all three, in that order.

  2. A wireframe should include every piece of content and every control the screen needs, in priority order, with realistic labels and data. Show what opens from the screen, where each action leads and the states beyond the full one: empty, loading, error and a user without permission. Leave out colour, imagery and final type.

  3. Wireframes can be drawn on paper or a whiteboard, which is quickest for early ideas, or made in a design tool such as Figma, which suits wireframes that will be shared, linked into a wireflow or turned into finished designs. The tool matters less than keeping the drawing plain.

Working on this now?

Tell us what you’re building and where it’s stuck. We reply within 12 hours.

Most teams start with a call, then a sprint or an audit.

Book a call
  • Angus
  • James
  • Naiya
  • Lilian
  • Luca
  • Minh
  • Jorge
  • Toffee

The people you’d work with, from the first call to launch