Campaign Design Notes
A design brief is the working document that connects a marketing objective with the visual and digital work required to support it. It gives designers, copywriters, marketers, developers, and reviewers a shared understanding of what must be produced, why it matters, and how the result will be evaluated.
Without a clear brief, a campaign can drift during production. Different participants may interpret the audience, message, tone, format, or deadline in different ways. Feedback then becomes a matter of personal preference rather than a comparison with agreed requirements. A useful brief reduces that ambiguity before design work begins.
The document does not need to predict every creative decision. Its role is to define the problem, the constraints, and the conditions for success while leaving enough room for professional judgment. The best briefs are specific about outcomes and requirements, but open about the visual route that may achieve them.
Begin by explaining the situation that led to the campaign. Avoid opening with a vague instruction such as “create something engaging.” Describe the practical problem that communication must address. For example, an audience may not understand a new service, may be unaware of a product feature, or may need more information before taking an action.
This context helps the creative team distinguish between a campaign that must build awareness and one that must support a decision. It also prevents the design from becoming disconnected from the wider marketing activity.
Include the following information:
Keep this section focused. A long history of the organisation can hide the information that production teams actually need. If background material is important, refer to it as an attachment or supporting document and summarise its relevance in the brief.
A design brief needs an objective that can guide decisions. The objective should describe a change in audience behaviour, understanding, or perception. “Promote the campaign” is an activity, not an objective. A more useful formulation might be to introduce a service to a defined audience and direct interested people to a specific information page.
Separate the primary objective from supporting goals. If every desired outcome is treated as equally important, the design team cannot resolve competing priorities. A campaign may need to inform, reassure, differentiate, and generate action, but one of these usually has to lead.
Use a structure such as:
Objectives should be realistic for the campaign's role. A set of display assets cannot solve a product, pricing, service, or reputation problem on its own. State what the design is expected to influence and what falls outside its scope.
Demographic labels rarely provide enough direction for design. A stronger audience description explains the people involved, their situation, their level of knowledge, and the barriers that may prevent action.
Address questions such as:
Audience insight should be supported by available research, analytics, customer-service evidence, interviews, or other documented sources. Do not present assumptions as facts. If a point is uncertain, label it as a hypothesis that the campaign may need to test.
When several groups are involved, identify the primary audience and adapt the message hierarchy accordingly. A brief that tries to speak to everyone often produces cautious, generic communication. Secondary audiences can still be listed, but their requirements should not obscure the main communication task.
Design cannot compensate for an unclear message. Define what the audience must understand first, what information supports that understanding, and what action comes next. This creates a hierarchy that can be translated into headlines, supporting copy, calls to action, imagery, and layout.
A practical message framework contains:
Mark which wording is fixed and which wording can be developed during production. If a legal statement, product name, URL, or call to action must appear exactly as supplied, label it as mandatory. This avoids late changes caused by uncertainty about approved language.
Do not pack every possible message into one asset. If an advertisement, landing page, email, and social format are all required, explain which message belongs to each stage. The campaign can then have a consistent idea without forcing every execution to carry identical content.
The creative direction should explain the intended impression and communication approach. It may describe the desired tone, emotional register, visual principles, references, and things to avoid. It should not replace the designer's role with a list of untested visual instructions.
Useful direction can cover:
References should clarify intent rather than invite imitation. Explain whether a reference demonstrates composition, clarity, pacing, accessibility, atmosphere, or information density. Also distinguish between a fixed brand requirement and a creative preference.
When a campaign requires digital design, include expectations for interaction and responsive behaviour. A layout that works on a large screen may become unusable on a small screen if content order, button size, contrast, or navigation is not considered from the beginning.
Deliverables define the work that must exist at the end of the project. List each item rather than relying on a broad phrase such as “campaign assets.” The list should make the production scope visible and expose dependencies between design, copy, development, translation, and media placement.
| Requirement | What to specify | Why it matters |
|---|---|---|
| Asset | Format, channel, purpose, and quantity | Prevents missing or unnecessary outputs |
| Dimensions | Required sizes, orientations, and responsive states | Protects the layout across placements |
| Content | Copy, imagery, logos, disclaimers, and calls to action | Clarifies what must be supplied or created |
| Technology | File types, motion rules, platform limits, and implementation needs | Reduces rework during delivery |
| Accessibility | Contrast, text alternatives, captions, focus, and readable structure | Makes the experience usable for more people |
For web content, identify whether the output is a static asset, a component for a content management system, an email module, a landing page, or an interactive experience. For video or animation, state duration, aspect ratios, captions, audio requirements, and whether the first frames must communicate without sound.
Accessibility should be a design requirement, not a final inspection. The Web Content Accessibility Guidelines published by the World Wide Web Consortium provide a recognised reference for digital content. The relevant requirements depend on the medium, but the brief can still request sufficient colour contrast, meaningful text alternatives, captions where needed, keyboard access for interactive content, and a logical reading order.
Constraints are not administrative details. They shape the possible solutions and should be known before concept development. Include brand rules, approved assets, legal requirements, platform specifications, translation needs, media limitations, technical dependencies, and any fixed launch conditions.
Assign ownership for each input. A brief becomes difficult to use when nobody knows who supplies the final copy, checks product accuracy, approves legal wording, provides image rights, or confirms technical compatibility.
Useful questions include:
For photography, illustration, fonts, music, and user-generated content, record usage rights and permitted channels. Avoid treating a file's availability as proof that it may be reused. Rights information belongs in the project record, alongside the final assets.
A deadline alone does not create a schedule. Break the work into stages and identify what must be approved at each stage. A typical sequence may include briefing, discovery, concept development, first design direction, content integration, accessibility and technical review, production, final approval, and handover.
Each review gate should answer a particular question. An early concept review may assess whether the direction addresses the objective and audience. A later production review may check copy accuracy, formatting, responsive behaviour, and required disclaimers. Mixing all types of feedback at every stage creates delays and encourages subjective revisions.
Document the following:
Agree on how feedback will be consolidated. One coordinated review is more useful than several unconnected comment streams. Feedback should identify the requirement or objective affected, explain the problem, and distinguish a mandatory correction from a preference.
The design brief should state how the campaign will be evaluated, while recognising that design is one part of the overall result. Choose measures that correspond to the objective. If the goal is understanding, consider evidence that the audience has received and understood the message. If the goal is action, define the relevant interaction and the path leading to it.
Possible measurement categories include:
Do not add metrics because they are available by default. A high volume of impressions, clicks, or views does not automatically demonstrate that the communication solved the stated problem. The measurement plan should explain what each indicator represents, what it cannot show, and who will review the findings.
Where a baseline, tracking method, or consent requirement is needed, identify it before launch. Measurement often depends on implementation decisions that cannot be added after the campaign has finished.
Approval should test whether the work meets the brief, not whether every reviewer would have made the same aesthetic choice. Before sending a design for review, check the core objective, message hierarchy, audience assumptions, technical requirements, accessibility considerations, and required content.
Reviewers can use a structured set of questions:
Keep version names and decisions traceable. Record which version was reviewed, who responded, what was changed, and what remains open. This is particularly important when a campaign contains many adaptations or when content changes after visual approval.
The following structure can be copied into a project document and adapted to the campaign:
End the document by asking every contributor to confirm that the brief is understood. Agreement at this point does not remove the need for creative discussion. It establishes a reliable reference for that discussion.
The useful length depends on the campaign's complexity. A small asset may require a short document, while a multi-channel campaign needs more detail about audiences, content, technical formats, approvals, and dependencies. Prioritise information that changes a creative or production decision.
The person responsible for the campaign usually coordinates the brief, but relevant contributors should validate their sections. Marketing can clarify objectives and audiences, subject experts can check accuracy, technical contributors can confirm implementation requirements, and approval owners can define the review process.
It can include references or a rough direction when these clarify the intended communication. A finished concept may constrain exploration before the problem and audience have been properly considered. Describe the required outcome and constraints first, then allow the creative process to develop the visual solution.
The terms are often used differently across teams. A creative brief commonly covers the campaign idea, audience, message, and tone. A design brief may place more emphasis on visual outputs, formats, technical requirements, accessibility, and production constraints. For a complex project, combining both perspectives in one working document can prevent gaps.
Update it whenever a change affects the objective, audience, message, deliverables, schedule, approval route, or technical conditions. Keep the previous version available for traceability and highlight decisions that alter the agreed scope.
