Wireframe
A wireframe is a simplified layout of a page or screen that shows structure, content hierarchy and key elements before visual design starts. It settles what goes where and why, without debating colour, imagery or polish.
- Also called
- Wireframing, Low-fidelity wireframe, Mid-fidelity wireframe, Lo-fi mockup
- Category
- Design and UX
- Updated
A wireframe is the blueprint of a screen. It shows which blocks exist, in what order, how much space each gets and what each one is for: headline, product visual, proof, pricing table, form. Nielsen Norman Group defines it as a skeletal outline of a layout, used before visual design is considered.
Wireframes range in fidelity. Low-fidelity versions are quick sketches or boxes used to compare options. Mid-fidelity versions use real copy, real content blocks and a basic grid, close enough to the final layout to make decisions on. When wireframes are linked with arrows to show what happens on each action, they become wireflows, a common format for documenting app user flows.
Why it matters for a SaaS website
Most website and product problems are structural: the page says the wrong thing first, the proof sits too low, the form asks too much. Wireframes let you fix those problems while changes are cheap, before anyone has polished a hero illustration. They also keep stakeholder feedback on substance. Nobody argues about the shade of blue when there is no blue yet.
How DesignMe handles it
On website design projects, we turn the sitemap and copy direction into mid-fidelity page layouts, so the structure is solved before the visuals. On product design projects, the wireframe stage covers key screens, dashboard structure, empty states and interaction notes, solving layout, hierarchy, states and interaction logic. We do not treat wireframes and visual design as separate worlds: logic, layout, copy and UI are shaped together, and we use AI to explore more wireframe options quickly before narrowing down.
For N3XT we wireframed every flow in low fidelity, from sign-up and approvals to instant payments and business settings, across admin, member, payer and provider roles. That came to 300+ screens across the web and mobile apps.
Example
Say a SaaS homepage gets traffic but few demo requests. The wireframe round tests two structures: one leads with a product screenshot and three feature blocks, the other with the problem, a short product walkthrough and customer logos right under the headline. Reviewing both with sales shows the second answers the questions prospects ask on calls, so it moves to visual design.
Common mistakes
- Lorem ipsum everywhere. Layouts built around fake text fall apart when real copy arrives.
- Skipping states. Empty, loading and error states belong in product wireframes too.
- Too polished, too early. High-fidelity wireframes invite feedback on visuals instead of structure.
- Wireframing pages, not flows. A perfect page is useless if users cannot reach the next step.
Questions
- What is the difference between a wireframe, a mockup and a prototype?
- A wireframe shows structure and hierarchy with little visual styling. A mockup is a static, high-fidelity picture of the final design. A prototype is interactive: you can click through it to test a flow. Teams often move from wireframes to mockups to prototypes, though a clickable wireframe is also a low-fidelity prototype.
- Should wireframes use real copy?
- Yes, as far as possible. Placeholder text hides the real problems: headlines that do not fit, sections with nothing to say, proof that does not exist yet. Draft copy, even rough, turns a wireframe into a test of the message as well as the layout, which is where most website projects are won or lost.
Sources
- Nielsen Norman Group: UX Deliverables Glossary (opens in a new tab)nngroup.com
- Nielsen Norman Group: How to Draw a Wireframe (Even if You Can't Draw) (opens in a new tab)nngroup.com
- Nielsen Norman Group: Wireflows (opens in a new tab)nngroup.com
Press Escape to close.