The brief as the campaign's foundation document
Launch library · evergreen read
Every campaign eventually meets a moment when someone asks why a particular decision was made, and the honest answer should be traceable back to a single shared document rather than a vague memory of a meeting held three months earlier that nobody wrote down properly.
A good brief states the underlying problem plainly before it states any proposed solution. It names the audience, the specific change being sought in that audience, the real constraints of budget and time, and the evidence that will eventually count as proof the work genuinely succeeded once it concludes.
Treated properly, the brief is not paperwork completed simply to satisfy an internal process. It becomes the reference point every collaborator returns to when a tempting new idea arrives mid campaign, testing calmly whether that idea genuinely serves the original problem or merely distracts everyone from it at a critical moment.
Skipping this step rarely saves real time in practice, however tempting it feels when a deadline looms. It only postpones the difficult questions until later, when they arrive harder to answer and considerably more expensive to fix properly, even before the first result comes in.