A campaign brief that people can actually use

Begin with the decision

A campaign brief often starts as a list of requested assets: a landing page, a guide, a webinar, and several emails. The list tells a team what to make but not why the work belongs together. Before choosing formats, describe the business decision the campaign is meant to influence. A useful objective identifies an audience, a situation, and a change you want to support.

Separate evidence from assumptions

Some parts of the brief will come from customer conversations or earlier campaigns. Others will reflect a reasonable hypothesis. Label the difference. If the team assumes a particular buying role cares most about deployment speed, state what supports that idea and what response would challenge it. This makes the brief a working document rather than a set of beliefs that nobody can question.

Name the next action

Ask what an interested person should do after engaging with the campaign. The answer needs to match the offer. An introductory article may lead naturally to a practical guide; a detailed evaluation session may support a direct conversation. Define who receives that response and what context they will have. A campaign is not complete when an asset is delivered if the next step has no owner.

Write for the people doing the work

Make the brief easy to use during production. Include the audience, the message, evidence, deliverables, dependencies, reviewers, and the measurement plan. Resolve contradictory comments in one shared version. At the end of the campaign, return to the brief and record what you would change. The next team should inherit the learning, not just a folder of finished files.