What a brief is for
A design brief is a short document that explains what a project is, why it exists and what it needs to achieve. It is written before design starts, usually by the client, sometimes with help from the designer. Its purpose is not to dictate how the work looks. It is to give the designer enough understanding to make good decisions and to give both sides a shared reference for judging the result.
Without a brief, designers fill gaps with guesses, and clients react to results that do not match what they pictured. A significant part of the rework that frustrates both sides starts here. The designer is not necessarily careless, and the client is not necessarily unclear. Nobody wrote down the answers.
Why vague briefs cause rework
Consider a request like “we need a new look for our business.” It leaves open almost every important question: who the audience is, what is wrong with the current look, where the new look will appear, and how success will be recognized. A designer who proceeds will make assumptions, and some of them will be wrong. The first concept then serves mainly to reveal what the client actually wanted, and the project effectively restarts.
Vague briefs also encourage feedback based on taste, because there are no stated goals to measure against. The conversation becomes “I like this” and “I do not,” which is hard to resolve and tends to lengthen revision rounds. A clear brief gives people something more objective to discuss.
The core parts of a good brief
Briefs can be short. A single page that covers the following is often enough.
Background
Describe the organization or person, what they do, and what prompted the project. Include any relevant context, such as a launch, a change in direction, or a problem with existing materials. The designer cannot read your mind, and a few sentences of background save a lot of guessing.
Goals
State what the project is meant to accomplish. Strong goals are specific enough to guide choices: for example, “help first-time visitors understand what we offer” is more useful than “improve our image.” If there are multiple goals, put them in order of priority. Be careful with goals that promise a particular outcome, since design is only one factor in results.
Audience
Describe who the work is for: their needs, their familiarity with the subject, and where they will meet the design. Details drawn from real knowledge of the audience are better than assumptions. If you have no data, say so honestly. The designer can then plan some basic design research.
Deliverables
List what you expect to receive: which items, in which formats and sizes, and for which uses. This is the foundation of the project scope. Include what you do not need, as well as what you do.
Message and tone
Explain what the work should say and how it should feel. Words such as “friendly,” “serious,” or “playful” help, particularly when paired with a short explanation. If the project involves an established brand, mention existing guidance, such as a brand style guide, and any elements that must stay the same. For a new identity, it is useful to describe brand values and how you want people to perceive the organization.
Constraints
Constraints shape design more than people expect. Mention anything that limits the work:
- legal or regulatory requirements
- required wording, logos or imagery
- technical limits, such as print methods or platform specifications
- accessibility needs
- budget
- existing assets that must be reused
Stating them early avoids discovering them late.
Timeline and process
Give key dates, such as launch or print deadlines, and explain how decisions will be made. Name who gives feedback, who has final approval, and how quickly they can respond. Many project delays come from unclear approval chains rather than design difficulty.
Examples and references
Samples of work you admire, and work you dislike, can clarify taste better than adjectives. Explain what you like about each, whether it is the color, the layout or the overall impression. References are for understanding direction, not for copying, so treat them as a conversation starter and not as a template.
Success measures
Describe how you will know the project succeeded. This might be qualitative, such as clearer communication in a presentation, or based on measures you already track. Be realistic and avoid expectations that depend on factors beyond the design.
Questions a designer may ask
A good designer will often respond to a brief with questions. This is a sign of care, not a criticism. Typical questions include what has been tried before, what the audience currently thinks, who the competitors are, and what has to stay the same. Answering them improves the brief and the work. Some designers use a questionnaire or a kickoff call to gather this information when the client has no written brief.
Keep it short and usable
A brief is not a place for long essays. Aim for clarity and brevity, with bullet points where they help. If a section cannot be answered yet, say so and note who will find out. An honest “we do not know” is more useful than a confident guess.
Treat it as a living reference
The brief is a starting agreement, not a legal cage. If goals change during the project, update the document and agree on the changes, which may affect cost and timing. At each stage, such as when presenting concepts, return to the brief to check the work against its goals. When a disagreement arises, ask whether the request moves toward the brief or away from it.
A good brief takes some effort, usually an hour or two of thought. That investment tends to repay itself in fewer misunderstandings, more focused feedback and work that is easier to approve.