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

A good design brief states the business problem, the audience, what success looks like, and the real constraints. It is not a description of the design you think you want. Write down the outcome you need and the conditions the work has to survive, and let the studio propose how to get there.

Most briefs fail in the same way. They arrive full of instructions about colour, layout, and style, and say almost nothing about why the project exists or how anyone will know it worked. The result is a studio guessing at intent while following your surface preferences. You get something that looks close to what you asked for and solves none of the problem you actually had.

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

What is a design brief actually for?

A brief exists to transfer intent. It gives the people doing the work enough context to make good decisions when you are not in the room, which is most of the time. A strong brief lets a designer resolve a hundred small questions the way you would have, without asking you each one.

That means the brief 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.

What should a strong brief contain?

Seven things carry most of the weight. State the business problem and why it matters now, so the work is tied to a real cost or opportunity rather than a vague wish to look more modern. Describe the audience and what they need to believe by the end, because design that changes nothing in the reader's head has failed regardless of how it looks. Define what success looks like, measurable where you can manage it, so everyone is aiming at the same target.

Then set the boundaries. Name the scope and deliverables in concrete terms. State the hard constraints honestly: the budget range, the deadline, the brand rules you cannot break, and the technical limits the work has to live inside. Provide references and, more importantly, the reason you chose each one. And say who decides, so approval does not dissolve into a committee halfway through.

• The business problem, and why it matters now
• The audience, and what they need to believe or do
• What success looks like, measurable where possible
• Scope and deliverables, in concrete terms
• Hard constraints: budget range, deadline, brand rules, technical limits
• References, each with the reason you chose it
• Who decides, and who only advises

Why does prescribing the solution get worse results?

There is a difference between briefing the problem and prescribing the solution. Briefing the problem tells the studio where you need to be. Prescribing the solution tells them exactly which road to take, usually before anyone has checked whether it leads there.

When you over-specify the design, you spend your budget on execution rather than thinking. The studio builds what you drew instead of what you needed, and you have quietly capped the outcome at the limit of your own first guess. You hired the studio for judgement you do not have in-house. Prescribing the solution throws that judgement away.

Tell us the problem you are trying to solve, not the picture in your head. The picture is usually a symptom of the problem, and we can find better ones.

References are where this tension is easiest to manage. A reference is useful when it comes with a reason: we chose this because the tone is confident without being loud, or because the information density matches ours. A reference offered without a reason is just an instruction to copy, and it tells the studio nothing about what you value underneath it.

What does a vague brief actually cost?

Vagueness does not save time. It moves the cost later, where it is more expensive. A brief that skips the business problem produces work that looks fine and misses the point, which surfaces at review as a feeling that something is off. That feeling turns into rounds of revision, each one negotiating intent that should have been settled on day one.

The pattern is predictable: rework, misalignment, and a final result that disappoints everyone while breaking no specific rule. The budget is spent, the deadline is closer, and the problem you started with is still there. Most of that could have been bought back with an hour of honest writing before the project began.

How do you know the brief is ready?

Run it against a short checklist before you send it. If any answer is missing or hand-waved, the gap will not disappear; it will resurface as a revision. It is cheaper to close it now.

• 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?

You do not have to write the perfect brief alone. A good studio will help shape it, pushing back on the parts that prescribe a solution and drawing out the problem underneath. At WeTrio every engagement starts with a working session that turns a rough brief into a sharp one before any design begins, because the quality of that document sets the ceiling for everything after it.

Write the brief as if you were handing your problem to someone smart who has never met your company. Give them the reasoning, the boundaries, and the definition of done. Then let them design. That is the version that gets you the work you actually wanted.