UX Glossary · W
Wireframe
A deliberately plain layout showing structure, hierarchy and content priority, with the visual design left out.
A wireframe shows what is on a screen, how it is arranged and what matters most, using boxes, lines and real labels rather than finished visual design.
Leaving the styling out is the point. It keeps the conversation on structure, and structure is both the more consequential decision and the more expensive one to change later.
Fidelity is a tool
A wireframe with real content and real labels is worth several with “Lorem ipsum” and grey rectangles. Placeholder text hides the problem that most layouts have: they were designed for content of a convenient length that does not exist.
Why it stays useful
Three things surface in wireframes and nowhere else as cheaply. Whether the page has a clear first, second and third priority. Whether the content that exists actually fits the layout proposed. And whether every state has been considered, since a wireframe set that only shows the populated screen has not asked what empty and error look like.
The stakeholder problem
Wireframes shown to people expecting a design reliably disappoint, and the feedback comes back as “it looks unfinished”. Saying explicitly what is being reviewed, structure rather than appearance, avoids most of that. Some teams use deliberately sketchy styling for the same reason: it signals that the drawing is not a proposal about colour.
In practice
Wireframe the awkward screens, not the obvious ones. The homepage is rarely where the structural risk sits.