Briefs That Leave Room for Ideas

Every project starts with a brief, even when nobody writes one down. There is always an understanding of what is needed, by when and why. The trouble is that unwritten briefs live in different heads, and they rarely match. A written brief is the simplest way to make sure everyone is solving the same problem.

But a brief can also go wrong in the other direction. Some briefs are so detailed that they describe the solution before any design has happened: the colours, the layout, the tone and the reference websites to copy. That leaves no room for ideas, and ideas are the reason to hire a studio in the first place.

Clear about the problem, open about the answer

The most useful briefs are specific about the situation and generous about the response. They describe what is not working, who the work is for, what constraints are real and what success would look like. They do not prescribe how it should look.

A brief should describe the problem so clearly that the answer has somewhere to go.

This is not about keeping clients out of the creative process. Clients know their audience, their market and their constraints far better than any outside designer. The brief is where that knowledge belongs. The answer is where the studio's experience belongs. Separating the two lets both do their best work.

The questions we ask

We usually write the brief together in a first conversation, then send it back as a short document to check. These are the questions that do most of the work:

• What is prompting this project now, rather than a year ago or a year from now?
• Who is this for, and what do they need to do, feel or understand?
• What is not working at the moment, in specific terms?
• What must stay, and what are you happy to change?
• What constraints are fixed: timing, budget, technology, regulation?
• How will you know the project has worked?
• Who needs to be involved in decisions, and when?

None of these questions asks for a colour or a layout. Those come later, as answers to the questions above.

Short briefs are better briefs

A brief longer than two pages is usually doing too many jobs at once. It may contain a company history, a list of every possible deliverable and a set of design preferences. Each of those has a place, but the brief itself should fit on a page or two, so that everyone can hold it in their head.

A short brief is also easier to return to. Halfway through a project, when a new idea arrives or a decision feels uncertain, everyone can reread the brief in two minutes and check whether the work is still on course.

Keeping it short forces useful choices. If there are five audiences, which one matters most? If there are ten things the work could do, which two must it do well? Those conversations are sometimes uncomfortable, but they are much easier to have before design starts than after a presentation, when people are reacting to images rather than to goals. A brief that makes those priorities explicit gives the design something firm to push against, and gives everyone a fair way to judge the work when it arrives.

References are useful, with care

Examples of work people admire can help a conversation, as long as everyone talks about why they like them. 'This feels calm because there is so much space' is useful. 'Make it look like this' is not. We ask for references early and then translate them into qualities rather than templates.

Let the brief change, once

Early research sometimes shows that the real problem is different from the one in the brief. The packaging is not the issue; the range is confusing. The website does not need a redesign; it needs clearer content. When that happens, we stop and rewrite the brief together rather than quietly drifting.

Changing the brief once, on purpose, early in the project, is healthy. Changing it constantly is a sign that something more basic has not been agreed. Either way, writing it down is what makes the difference visible.