How to write a design brief that gets you the work you want

Most briefs arrive full of instructions about colour and layout and say almost nothing about why the project exists. The studio then follows your surface preferences while guessing at your intent, and delivers something that looks close to the request and solves none of the problem.

The fix is not a longer brief. It is one that answers a small number of questions honestly, in plain language, before anyone opens a design tool.

What a brief is actually for

Transferring intent. It gives the people doing the work enough context to decide well when you are not in the room, which is most of the time. A strong brief lets a designer settle a hundred small questions the way you would have, without asking you any of them. So it should be dense with reasoning and light on prescription. The question it answers is not what should this look like. It is what has to be true when we are finished.

The seven things that carry the weight

• The business problem, and why it matters now — tied to a real cost, not a wish to look modern.
• The audience, and what has to change in their head by the end.
• What success looks like, measurable wherever you can manage it.
• Scope and deliverables, in concrete terms.
• Hard constraints: budget range, deadline, brand rules you cannot break, technical limits.
• References — each with the reason you picked it.
• Who decides, and who only advises.

Why prescribing the design gets worse work

There is a difference between briefing the problem and prescribing the solution. The first tells a studio where you need to be. The second names the road, usually before anyone checked whether it leads there. Over-specify and you spend the budget on execution rather than thinking — the studio builds what you drew instead of what you needed, and the outcome is quietly capped at your own first guess. You hired them for judgment you do not have in-house. Prescribing throws it away.

How we put it at kickoff: tell us the problem, not the picture in your head. The picture is usually a symptom of the problem, and there are better ones.

References are where this gets manageable. One with a reason attached is useful — “the tone here is confident without being loud”, “the information density matches ours”. One offered without a reason is just an instruction to copy, and it says nothing about what you actually value.

What vagueness actually costs

It does not save time; it moves the cost somewhere more expensive. A brief that skips the business problem produces work that looks fine and misses the point — which surfaces at review as a vague feeling that something is off. That feeling becomes rounds of revision, each one negotiating intent that should have been settled on day one. Budget spent, deadline closer, original problem untouched. Most of it buyable back with an hour of honest writing.

Six checks before you send it

• Can a stranger read this and explain the business problem back to you?
• Is the audience specific, and is it clear what should change in their mind?
• Would you recognise success if you saw it — and can you measure any of it?
• Are the constraints real numbers and dates, not adjectives?
• Does every reference carry a reason?
• Is there one named decision-maker?

Any gap here will not disappear. It resurfaces as a revision, at a worse moment, at a higher price. And you do not have to write it alone — a good studio helps shape it, pushing back on the parts that prescribe a solution and drawing out the problem underneath. We start every engagement with a working session that turns a rough brief into a sharp one, because that document sets the ceiling for everything after it.