What is wireframing?

A wireframe is an argument about hierarchy, made cheaply enough that you can be wrong twice before lunch. Everything else it appears to be — layout, spacing, copy — is a side effect.

Introduction

Wireframes exist because the alternative is arguing about a finished screen. Once a design has colour and photography in it, feedback drifts towards taste, and the structural question you actually needed answered goes unasked.

Strip those out and the conversation changes. People stop saying they dislike the blue and start saying they cannot find the thing they came for, which is the only feedback worth having at this stage.

Keep the fidelity low enough that nobody mistakes it for a decision. Grey boxes and real words beat lorem ipsum and rounded corners every time, because the words are what people will actually read.

Write the real copy first, even if it is wrong. Layout follows language far more reliably than language follows layout, and a heading you cannot write is usually a section you do not need.

Then test the smallest thing: give someone the wireframe and a task, and watch where they hesitate. Two people is enough to find the problems that matter at this fidelity.

Software and tools

Any tool works. Paper works. What matters is that the artefact is quick to throw away, because a wireframe you are reluctant to delete has already failed at its job.

If your team shares a component library, borrow only its spacing scale at this stage. Reaching for finished components pulls you into visual decisions you have not earned yet.

Other resources

Three habits carry most of the weight when you are starting out:

1. Sketch three layouts before you refine one.
2. Use real content, in the real quantity you expect to have.
3. Show it to someone who was not in the room when you made it.

None of this is unique to interface design. The same shape works for API design and org charts, because the constraint is identical: make the structure visible before it becomes expensive.

Start rough, get it wrong quickly, and keep the version that answered the question rather than the one that looked best.