How to Write a Good Design Brief Even If You Know Nothing About Design

Most projects don't go wrong in execution. They go wrong in preparation — specifically in the brief, or the absence of one.

A studio that doesn't understand what you need will design for assumptions. Some of those assumptions will be right. Many won't. The discovery of which ones were wrong happens during revisions, which are expensive — in time, in energy, in the particular friction that comes from redirecting work that was done confidently in the wrong direction.

A good brief prevents most of that. Not all — no project is without course corrections. But the ones that come from genuine new information are very different from the ones that come from starting without adequate understanding.

The encouraging thing is that writing a useful brief doesn't require design expertise. It requires clarity about your business situation and honesty about what you know and don't know. The studio provides the design knowledge. Your job is to provide the context — and to provide it well.

What Most Briefs Get Wrong

Before the practical guide, it's worth understanding the common failures, because they're instructive.

They're aspirational rather than specific. "We want to be seen as the leading studio in our field" is not brief material. It's aspiration. A brief that describes aspiration without describing the current situation, the specific audience, or the concrete constraints gives the studio nothing to work with.

They describe what they want without explaining why. "We need a new logo" is not a brief. Why does the current one not work? What does it communicate that you don't want it to communicate? What has changed that makes the old one no longer fit?

They avoid giving a budget. This is the most reliably unhelpful omission. A studio that doesn't know your budget can't tell you what's achievable within it. The proposal you receive will be scoped against their best guess — which may be significantly above or below what you were prepared to spend.

They describe the deliverable rather than the problem. "We need a new website" is a deliverable. The problem is something more specific: you're not appearing in search, your current site doesn't represent the quality of your work, you're losing potential clients who arrive at your site and leave immediately. The deliverable follows from the problem; the problem is what the brief should articulate.

They're written for the studio's approval rather than the project's clarity. Some briefs are written to sound impressive or professional rather than to be genuinely useful. The test is simple: does this document, read by someone who knows nothing about your business, give them an accurate and honest picture of your situation?

The Information That Actually Matters

A useful brief covers six areas. They don't need to be exhaustive. They need to be honest and specific.

1. The business

Start with the facts. What does the business do, who for, and where. How old it is. How it currently generates clients. What the business model is. Whether it operates locally, nationally or internationally.

Then the context that facts don't capture: what makes this business genuinely different from its competitors, if anything. Not the marketing claim — the real operational or positioning difference. If you struggle to articulate this, say so. That struggle is useful information for the studio.

Include the competitive landscape honestly. Who are the main alternatives a potential client would consider? What do their brands and websites look and feel like? Where do you want to sit relative to them?

2. The problem you're trying to solve

This is the most important section of any brief, and the one most often skipped or given a vague answer.

Be specific. Not "we need to improve our online presence" but something more like: "We receive around 400 visitors a month but almost none of them convert to enquiries, and the clients we do speak to often seem surprised by our pricing because the website doesn't signal the level we operate at." That's a brief. The other is a category.

If there are multiple problems, list them in priority order. What is the one thing that, if solved, would make the project a success?

If you don't fully understand the problem — if you know something isn't working but can't diagnose what — say that. The studio can help you investigate during discovery. What they can't do is solve a problem they've never been told about.

3. The audience

Describe the people this project needs to serve. Not demographically — that's usually less useful than it sounds. Describe them behaviourally and motivationally: what they care about, what they're looking for when they encounter your brand, what would make them trust you, what would make them hesitate.

If you have different audience segments with genuinely different needs, describe each one. If one is clearly more important than the others, say so.

If you've received direct feedback from clients — things that influenced their decision, things that gave them pause — share it. Real audience intelligence is far more useful than assumed profiles.

Key: The more concretely you can describe who this project needs to serve and what they need to experience, the more precisely the studio can design for that audience. General descriptions produce general solutions.

4. What success looks like

Not the deliverable — the outcome. What needs to be true in six months that isn't true today? More enquiries? A specific type of client you're currently not attracting? A brand that can justify higher pricing? An online presence that your current work and clients can be proud to share?

Be honest about this. If you want more clients, say so — that's a legitimate business goal and there's nothing to hide about it. Vague success criteria produce projects that technically deliver what was requested while missing what was actually needed.

If there are metrics that matter — enquiry rate, average order value, search visibility in specific terms — include them.

5. Constraints

Budget, timeline, technical requirements, internal approvals, brand elements that must be retained — all of these belong in the brief, stated directly.

Budget especially. A range is better than silence. "We have between £8,000 and £12,000 available for this project" gives the studio something to design a proposal around. It doesn't mean you'll be invoiced £12,000. It means the scope will be realistic.

Timeline constraints with reasons are also more useful than abstract deadlines. "We need this live by September because we have a significant industry event" is more helpful than "September deadline." The reason helps the studio understand how firm the constraint is and prioritise accordingly.

6. Visual references and what you want them to say

References are useful. Vague references are less so.

If you share websites or brands you admire, explain what specifically you admire about them: the photography, the typographic rigour, the simplicity of the layout, the tone of the copy. Without that context, references are ambiguous — the studio might respond to exactly the element you were unconsciously ignoring.

Also share things you genuinely dislike, and why. Knowing what to avoid is as useful as knowing what to aim for. And if there are brand elements — a typeface, a colour, a logo — that must be retained or definitely not used, say so clearly.

Questions to Ask Yourself Before Writing

Some clients find it easier to prepare a brief by working through a set of questions first, then writing the answers up. These are the ones that tend to produce the most useful material.

What would have to be true for this project to be a success? Answer this as concretely as possible.

Why is this the right time to do this project? What has changed, or what is about to change?

Who are the three to five people most important for this project to work for? Not abstractly — specifically. You can describe a real client by way of example.

What is the single most important thing you want someone to feel when they first encounter this brand or website? Not a list — one thing.

What does your current situation communicate that you don't want it to communicate?

If someone asked a current client to describe your business in one sentence, what would you want them to say? What do you think they currently say?

What have you tried before, and why didn't it produce the result you needed?

The answers to these questions are not all equal — some will be more useful than others for a given project. But working through them will surface the clarity that makes a brief genuinely useful.

The Brief Is a Conversation Starter, Not a Specification

One thing worth saying plainly: a brief is not a contract. It's the beginning of a conversation.

A good studio will read your brief, ask follow-up questions, challenge things that seem unclear or that might not achieve what you're describing, and share their own perspective before proposing anything. The brief opens that conversation; it doesn't close it.

This means you don't need to have perfect answers to every question. You need to have honest answers — including honest uncertainty where it exists. A brief that says "we're not sure whether our target audience is primarily local or national — we've been working both ways but haven't been strategic about it" is more useful than one that claims false clarity on the point.

The goal is to give the studio the real picture, so that the work that follows is grounded in your actual situation rather than a polished version of it.

If you're preparing to brief a studio on a web design or brand project, our approach page explains how we use the brief within our own process — and what happens in the discovery phase that follows. Our contact page is the simplest way to start a conversation if you'd like to understand whether a project makes sense before committing to writing anything formal.

For context on what that project might reasonably cost, what a well-built website really costs covers the pricing landscape honestly — and helps explain why the brief has such a significant effect on the quality of the proposal you'll receive.