Creative Briefing Playbook: Avoiding 33% Waste

Idea from the episode

A formal creative brief in a PDF is easy to spot. The harder ones are the Slack message, the walkthrough call, the offhand "can you handle this?" at the end of a meeting. Sebastian's argument is that briefing is not an event: it is a situation. Any moment where someone translates a task for another person to execute is a briefing.

Once you see it that way, the frequency becomes apparent. A client presenting a project to an agency is briefing. A CMO assigning a campaign to a brand manager is briefing. A creative director handing work to a designer is briefing. All of these moments follow the same logic and all carry the same risks when done badly.

The organisations that are good at briefing are good at it at every level, not just in the formal client-agency relationship.

In the conversation, Sebastian widens briefing beyond the formal agency meeting. A one-line email, a phone call, a WhatsApp message or a colleague saying "can you do this quickly" can all be briefing situations if one person is translating information so another person can fulfil a task.

Idea from the episode

Sebastian's framework reduces to five questions. Every good brief answers all five. Every weak brief skips at least one.

Who is the first question, and it has two answers. The first is the target audience: who should be affected by the work. The second is the person receiving the brief: who is doing the work. A brief to a junior designer and a brief to a senior strategist are different briefs even when the task is identical. Most briefs answer the audience version of "who" and ignore the second entirely.

What is the task: the deliverable, the output, the scope.

Why is where most briefs fail. Why does this matter? What does success look like in business terms? Without it, creative decisions become arbitrary and feedback becomes subjective.

How is the approach: tone, constraints, references, what to avoid.

When is the timeline, and it belongs last, not first.

The transcript gives the five questions different weight. "Who" is not only the target audience, but the person receiving the brief, because a screen designer, a creative director, a media agency and a freelancer need different information and language.

The other questions then build on that: "what" defines the deliverable and the form of the next meeting, "why" clarifies the business objective and the metric behind it, "how" sets boundaries and uses past learning, and "when" creates checkpoints rather than only a final deadline.

Idea from the episode

The most common misunderstanding of briefing: filling out the template is the work. It is not. Filling out the template is documentation of the work. The actual work, deciding what matters, what to leave out, what the real goal is, what success looks like, happens before the template.

When that thinking is skipped and the template is handed to the process instead, the result is a document that looks complete and is strategically empty. All the boxes are filled. None of the hard questions were asked.

Sebastian's test: if your brief was produced in less time than the conversation that preceded it, the template is doing more work than your thinking.

Sebastian is explicit that the document is not the work. A good briefing can happen without a formal file if the communication makes the task, goal, boundaries, outcome, budget and timing clear. Templates help only after the thinking has happened.

Idea from the episode

A good brief is not one that contains everything. It is one that has had things removed. The courage to leave things out is one of the rarest skills in briefing, and one of the most valuable.

Every additional requirement in a brief narrows the creative solution space. Sometimes that narrowing is the point: you are setting a precise boundary. But when briefs accumulate requirements because no one was willing to decide what was most important, the result is a brief that cannot be executed without contradiction.

The act of reduction is the act of prioritisation. Choosing what to include means deciding what matters. That decision should happen before the brief is written, not after.

The reduction point comes directly from his warning that briefs often contain everything the company knows. That overwhelms the receiver, makes the wrong detail look important and can produce advertising that tries to say every product feature at once.

Idea from the episode

Every brief has a fundamental orientation. Some briefs are invitations: they open creative space and ask for exploration. Others are specifications: they close off options and define what must not be violated. Both are legitimate. The problem is when the type is not chosen deliberately.

An inspiring brief handed to a team that needed guardrails produces ideas that are creative and miss the client's actual requirement. A constraining brief handed to a team that needed room produces work that is technically correct and strategically inert.

Sebastian argues this choice, inspire or constrain, should be made explicitly and stated in the brief itself. The right choice depends on the stage of the project, the maturity of the client-agency relationship, and what the work is for.

The inspire-or-constrain choice depends on the receiver and the goal. Some teams need a springboard or almost-big-idea, while others mainly need budget, scale, brand rules, product, audience and deliverable boundaries so they can do the craft themselves.

Idea from the episode

Briefing is a translation process. The client translates their business problem into a task. The agency translates that task into a creative interpretation. Each translation can introduce error.

The rebriefing step, asking the agency to present back their understanding of the brief before execution begins, is the check most teams skip and most agencies resist. It feels redundant. It is not. The moment a creative team explains what they understood, the gaps that will cost three revision rounds later become visible now.

Sebastian's recommendation: make rebriefing a contractual step, not an optional one. Build it into the process before execution begins, every time.

Sebastian treats the rebrief as a translation check. The receiving side puts the task back into its own words, sometimes reducing a client brief into an agency or creative-team brief, so both sides can see whether the same task has actually been understood.