What it is
Detailed, visually complete static designs showing final colors, typography, imagery, and spacing, used to finalize visual direction and hand off to engineering.
When to use it
Later in Prototype, once structure is settled and visual design decisions are needed.
Why (value)
Communicates the exact intended look, aligns stakeholders on visual direction, and provides a precise reference for build.
How to run it
- Start from settled wireframes/structure.
- Apply the visual system: color, type, spacing, imagery.
- Design real states (empty, error, loading).
- Review for consistency and accessibility.
- Prepare for handoff or interactive prototyping.
Inputs and outputs
- Inputs: Approved structure and a visual/design system.
- Outputs: Pixel-accurate mockups ready for handoff.
Time and effort
Medium. Hours to days.
Evidence and limitations
A visual artifact, not usability evidence; looking finished does not mean it works. Validate with testing. See Evidence and limitations.
Tips and pitfalls
- Design real states, not just the happy path.
- Check contrast and accessibility.
- Do not treat a polished mockup as validated.
Variations
Static mockups, design-system-driven comps.
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.”
Explore related methods
- Wireframing — Lay out structure and content priority without visual design to focus on function.
- Interactive prototyping — Build a clickable simulation of the experience so people can try it before it is built.
- Style tiles — Define the visual language, color, type, buttons, in a compact reference before full mockups.
