It's not the wireframe. It's not the visual design review. It's the brief — and almost no one writes a good one.
The shape of a useful brief
A good brief answers three questions in plain language:
- Who is this for? — Not a persona document. One sentence that describes the person at the moment they need this thing.
- What changes for them when this works? — The outcome, not the output.
- What would make this obviously wrong? — The guardrails that protect the work from drift.
Everything else — tone, references, deadlines — is logistics.
Why this beats process
Briefs that read well make every other decision faster. Briefs that don't add a week to the project, every time.
