Start with the decision the project needs to support
A creative brief is a shared starting point, not a prediction of the final design. Its job is to explain why the project exists and give the people doing the work enough direction to make informed choices. Write it before exploring concepts, while there is still room to question assumptions. A page or two is often more useful than a long document that nobody revisits.
Begin with the situation and the intended change. For example, “Our workshop materials look different across channels, making it hard for participants to recognise related events” is more useful than “We need a fresh look.” Then state what the work should help people do: recognise the programme, understand what each session offers or find registration information. This separates the underlying problem from a possible solution.
Define the audience and the message
Name the primary audience as specifically as the project allows. “New participants who have never attended one of our workshops” gives a designer more direction than “everyone interested in creativity.” Add what this audience may already know, what they need to understand and where they will encounter the work. If several audiences matter, identify which one takes priority when their needs conflict.
Next, write the main message in one plain sentence. Avoid strings of adjectives such as “bold, authentic and innovative” unless you can explain what they mean in practice. A more actionable sentence might be, “These short workshops give first-time participants a welcoming way to try a creative method.” Supporting points can follow, but distinguish essential information from details that are merely nice to include. That distinction becomes especially helpful when space is limited.
Describe the work without designing it in advance
List the expected deliverables, their likely uses and any known formats. A brief for a workshop series might call for a reusable event graphic, a social post template and a simple handout layout. Note whether existing identity elements must be used, whether copy and photographs are available, and who will supply missing material. These details prevent a concept from depending on assets that do not exist.
Record constraints as facts, not vague preferences. A fixed print size, a limited production budget or a requirement that a template be editable by a small team can shape a useful solution. At the same time, leave room for creative judgment. Rather than instructing someone to “put a large circle in the top left,” explain the need it is meant to address, such as making the event series recognisable at a glance. Label ideas that are open for exploration as possibilities, not requirements.
Make the process and approval path visible
A brief should say who provides input, who gives consolidated feedback and who makes the final decision. Without that distinction, a team can spend time reconciling comments that point in opposite directions. Include the planned stages of work, such as initial directions, one selected direction for development and final production files. If timing is uncertain, name the decisions or materials that must arrive before the next stage can begin instead of inventing a precise schedule.
Agree on what a useful review will cover. Early feedback should address whether a direction serves the audience and communicates the message, rather than concentrating only on minor visual details. Later reviews can focus on accuracy, consistency and whether the files work in their intended settings. The brief can also list practical checks: Can someone understand the offer without extra explanation? Can the small team update the template? Do the required elements remain clear at the smallest intended size?
Test the brief, then keep it in use
Before work begins, ask everyone responsible to read the brief and explain the project back in their own words. If their answers differ, the document needs another pass. Look especially for contradictions: an ambitious list of deliverables paired with limited time, several competing primary audiences or a request for a reusable system without anyone assigned to maintain it. Resolving those tensions now is usually easier than resolving them after concepts have been made.
Treat the approved brief as a reference rather than a rigid contract for every creative choice. When a new idea appears, compare it with the stated goal, audience and constraints. When the project changes, update the brief and make the change visible to collaborators. A good brief gives a team permission to explore while providing a clear reason to choose one direction over another.
