If you want to know how to write a design brief, here's the short answer: in one to three pages, tell the studio where your business is, what needs to change, who it's for, what success looks like, what's fixed (budget, timeline, non-negotiables), and what you've already tried. That's it. Everything else — moodboards, font opinions, competitor screenshots — is optional seasoning.
The longer answer is worth your time, because the quality of design you get back is largely decided before a single pixel is made. PMI research attributes 37% of project failures directly to unclear objectives — and in our experience, almost every painful design project traces back to a brief that was either missing, vague, or secretly three different briefs wearing a trench coat.
What is a design brief actually for?
A design brief is not a specification document, and treating it like one is the first mistake. You are not ordering a logo the way you order a part. A brief exists to transfer context — the situation your business is in, the problem you believe design can solve, and the constraints that are genuinely fixed. The studio's job is to challenge it, sharpen it, and often rewrite it in their own words before any design begins. When we ran the identity for Justach, the most valuable thing the client gave us wasn't a list of deliverables — it was an honest sentence about what every other men's grooming brand looked like, and why that was the problem.
What should a design brief include?
Across the guides studios and platforms publish — Asana's and Figma's are solid references — the same core sections keep appearing. Here's our version, in the order a studio actually reads them:
Context — what your company does, what stage you're at, and why this project is happening now. One paragraph. The 'now' is the most revealing part.
The problem — what isn't working, stated as a business problem, not a design instruction. 'Customers don't remember us' is a brief. 'Make the logo bigger' is a prescription.
Audience — who this is for, described as people with needs, not demographics on a slide. What do they currently buy instead of you?
Success — how you'll know it worked. More qualified leads? Recognition on a shelf? A sales team that finally has materials they're proud of?
Constraints — real budget range, real deadline, and anything genuinely untouchable (a name, a colour, a regulation). Honesty here saves weeks.
Prior art — what you've tried, what you liked and hated about it, and any existing guidelines. Include the failed rebrand. Especially the failed rebrand.
How long should a design brief be?
One to three pages. Shorter than feels responsible. The discipline isn't in writing more — it's in deciding what actually influences design decisions and cutting everything that doesn't. A 15-page brief usually means the organisation hasn't agreed on what it wants, and it's outsourcing that argument to the studio at the studio's hourly rate. If you can't get it under three pages, that's not a writing problem; it's an alignment problem, and it's cheaper to solve internally first.
Which brief mistakes quietly kill projects?
The expensive failures are rarely dramatic. They're slow leaks, and almost all of them are visible in the brief stage if you know what to look for. Poorly defined requirements are the number one cause of scope creep — when objectives and boundaries aren't documented, every stakeholder fills the gaps with their own interpretation. Projects without formal change management are 35% more likely to blow their budgets and deadlines.
The committee brief — five stakeholders, five definitions of success, none written down. Decide who holds the pen before you approach a studio.
The prescription brief — specifying solutions ('we want a sans-serif, something like what Stripe has') instead of problems. You hired judgment; let it work.
The aspirational budget — withholding the real number to 'see what they come back with'. Studios scope to budget. Vagueness buys you a vague proposal.
The frozen brief — refusing to let the brief evolve after the studio's discovery work. The best projects treat the rewritten brief as the real starting line.
What happens after you send it?
A good studio won't just accept your brief — they'll interrogate it. Expect questions that feel slightly uncomfortable: why now, what happens if you do nothing, who can kill this project internally. Then expect them to play it back to you rewritten. That rewrite is the real contract of understanding, and it's the moment to disagree cheaply. At Afterthought we research the category and write the brief back in our own words before building anything — it's the step that makes everything downstream faster, whether the work is brand identity, naming, packaging, or digital.
Thinking about briefing a studio?
If you've got a project forming — even if the brief is still half-sentences and a feeling — that's enough to start a conversation. We work with founders and brands globally, fully remote, and we'll help you sharpen the brief before you commit to anything. Start a brief — it takes five minutes, and we reply within the week.