An AGD creative brief connects audience, promise, format and hypothesis. It gives a creator direction and an analyst an interpretable question.
01STORY BRIEFThe idea in three screens.3 SCREENS

A good brief starts with what we want to learn.
An AGD creative brief connects audience, promise, format and hypothesis.
Replace “make a viral video” with “test whether this friction resonates with students revising.” List requirements, freedoms and boundaries. A useful constraint explains its role: the first screen should make the situation visible, not merely contain a keyword.
Add the sentence a viewer should be able to repeat afterward. It is not a mandatory slogan but a comprehension check. If the creative team proposes a better way to convey the idea, the brief should allow it. The document sets the job’s objective without confusing that objective with the first imagined solution. This distinction keeps constraints useful while preserving the creator’s judgment.
A brief should make the review easier before production begins.
Write the audience situation, the claim and the evidence before choosing an effect or a format. A useful brief might ask whether a visible before-and-after helps a certain viewer understand a workflow. A weak brief asks for three viral videos with different hooks. The first gives the team a question it can answer. The second turns every result into an argument about taste, energy or whether the creator tried hard enough.
A brief an editor can review
- 01Question
What do we want to learn about this audience or explanation?
- 02Evidence
What must the viewer actually see?
- 03Boundary
What can change, and what would invalidate the comparison?
Editorial model: a way to reason about the process, not measured platform results.
Include what must stay fixed and what the production is allowed to change. Specify the source material, rights context and the person who can approve the final version. Give examples of the desired mechanism without asking a creator to imitate someone’s identity or reproduce their clip. During review, compare the finished asset with the original learning question. A technically polished video can still fail the brief; a rough prototype can be useful if it resolves a decision before expensive production. Keep that distinction visible in how the team labels and evaluates work.
Emily Mariko's recipe is useful as a reference for a concrete transformation. The reported ingredients and the finished bowl give the viewer something specific to understand and potentially try. Translate that clarity into the brief rather than copying the setting or aesthetic. Name the starting state, the visible action and the result. Add the one detail that makes this example worth showing instead of describing in a sentence. For a software tutorial, that might be the awkward source file or the inspection step that proves the output is usable. The brief should tell an editor where the explanation becomes visible, not merely request an engaging video.
“A good brief starts with what we want to learn.”
02FIELD KITFrom concept to practice.2 SCREENS

Write the learning question.
Adapt this to your audience, budget and test scope.
Put it to work.
- 01Write the learning question.
- 02Define what the creator can choose freely.
Notes & sources.
The limit. An overly prescriptive brief can eliminate the variation the test was meant to explore.
Further reading is linked throughout this article. Worked examples explain a process; they are not campaign results.
THE ORGANIC CLUB is an editorial project initiated by TokPortal. That relationship is separate from the evidence behind claims. Editorial signatures and image credits are explained in our policy. Our editorial policy →



