What it is
Low- to mid-fidelity layouts that show structure, content hierarchy, and functionality without visual styling, used to align on what goes where before investing in polish.
When to use it
During Ideate and Prototype, to define layout and hierarchy before visual design.
Why (value)
Keeps discussion on structure and priority rather than color and typography, and is cheap to change.
How to run it
- Identify the screen’s goal and key content.
- Block out layout and hierarchy with simple shapes.
- Focus on what and where, not how it looks.
- Annotate behavior and intent.
- Review and iterate before adding fidelity.
Inputs and outputs
- Inputs: Content requirements, user tasks, information architecture.
- Outputs: Wireframes showing layout, hierarchy, and functionality.
Time and effort
Low. Minutes to hours per screen.
Evidence and limitations
A design artifact, not evidence. It represents intent; usability must be validated by testing. See Evidence and limitations.
Tips and pitfalls
- Keep it low-fidelity so people critique structure, not style.
- Annotate behavior clearly.
- Do not sneak in final visual design too early.
Variations
Low-fi vs. mid-fi wireframes, wireflows, annotated wireframes.
Related methods
Need help choosing and applying a method?
Gumshoe helps teams connect research, collaborative workshops and service design to the decisions they need to make.
Sources and further reading
- UX Tigers, “100 UX methods.”
- 18F Methods (US government, public domain).
Explore related methods
- Sketching — Think with a pen: explore many ideas fast and cheap before committing to any.
- Wireflows — Combine wireframes with flow arrows to show both screens and the transitions between them.
- High-fidelity mockups — Produce pixel-accurate visual designs that show the real look and feel.
