# Wireframe

A wireframe represents a screen’s structure, content priorities, and controls so a team can examine layout before detailed visual styling.

- Type: artifact
- Domain: Experience & interface
- Level: Foundational
- Last reviewed: 2026-10-20
- Original: [Soroush’s Product Wiki](<https://wiki.soroush.uk/topic/wireframe/>)

## What it means

A wireframe is a simplified representation of an interface that makes information placement, hierarchy, and available actions explicit. It can be drawn on paper or digitally. Unlike a visually detailed mockup, its main purpose is to explore structure; connected wireframes can also form a prototype for testing a sequence.

## Why it matters

Layout decisions determine whether people notice essential information and understand their next action. A lightweight representation makes competing arrangements inexpensive to compare before detailed components and styling create attachment to one direction.

## When to use it

Use wireframes when content grouping, navigation, or screen structure is uncertain. Skip a separate wireframing stage when an established component pattern already answers those questions or when realistic visual detail is necessary for the study.

## How it works

1. Choose the user task and the screen states needed to examine it.
2. List actual content and actions in order of importance.
3. Sketch alternative arrangements using recognizable labels and representative content lengths.
4. Walk through the task, including missing information and error conditions.
5. Record unresolved behavior and move to a prototype when interaction needs testing.

## A practical example

A subscription team sketches two renewal screens: one organized around plan features and another around the upcoming charge and renewal date. Reviewing the cancellation task reveals that the second makes the decision clearer. The team prototypes that structure before choosing colors.

## Where it breaks

A wireframe does not establish that a flow works, that content is understood, or that the implementation is accessible. Placeholder text can conceal layout problems. Stakeholders may also interpret omitted elements as settled decisions unless the artifact states its scope.

## Common mistakes

- Using empty boxes where content length drives the layout.
- Treating a wireframe as a complete engineering specification.
- Polishing one arrangement before comparing alternatives.

## Sources

1. [What is a wireframe? A guide for non-designers](<https://balsamiq.com/blog/what-are-wireframes/>) — Balsamiq · Professional guidance
2. [UX Deliverables: Glossary](<https://www.nngroup.com/articles/ux-deliverables-glossary/>) — Nielsen Norman Group · Professional guidance

## Related topics

- [Mockup](<https://wiki.soroush.uk/topic/mockup/>)
- [User Flow](<https://wiki.soroush.uk/topic/user-flow/>)
- [Prototype Fidelity](<https://wiki.soroush.uk/topic/prototype-fidelity/>)
