Wireframe Fundamentals

Overview

Fidelity should correspond to certainty: never render more polish than you have validated decisions to back. A wireframe's output is shared understanding, not the artifact — it is a sketch/prototype hybrid built to be cheap to make, cheap to change, and cheap to discard, so structural flaws surface before anyone writes code.

When to Use

• Starting any new screen, feature, or product — before visual design, before code
• Choosing the fidelity of the next design artifact, or deciding whether to move up or down a level
• Picking a wireframing method or tool (paper, whiteboard, dedicated software)
• Unblocking a team stuck debating pixels because it jumped straight to polished mocks
• Aligning developers and stakeholders on structure and flow before build starts
• NOT for: visual polish — type, color, brand, motion. That's comp/mockup territory (co-fire hallmark)
• NOT for: validating fine interaction detail with users — that needs a prototype, not a wireframe

Why Low Fidelity Wins