← Resources

Playbooks

Creative brief development

Creative brief development is a workflow, not an event. The multi-sprint process for turning briefs into versioned operating knowledge - what to do at each stage, what to measure, and how teams compound quality.

Updated

Before you start

  • A team shipping creative work on a recurring cadence (weekly, bi-weekly, monthly)
  • Some form of performance feedback loop (ad metrics, conversion data, qualitative feedback)
  • A shared doc archive (Notion, Docs, Linear) - briefs need to be findable across sprints
  • Willingness to treat the brief as a versioned, evolving artifact - not a one-shot document

The playbook

8 steps

0/8
  1. Treat brief development as a v0 → v1 → v2 cadence, not a one-time event

    Most teams write the brief once and ship. Brief development means versioning. v0 is the rough draft; v1 is the brief that ships the first campaign; v2 incorporates what the first campaign taught you; v3 incorporates the second campaign's lessons. After 6-8 versions the brief converges into a brand-and-category operating doc. Set up the version cadence at the start; don't try to retrofit it later.

    Expected outcome

    Brief is in a versioned location with a clear cadence (e.g. one new version after each sprint).

  2. Develop v0 in 60 minutes - the rough draft

    v0 is permissive. Goal, audience, angle, archetype, do-nots, references, deliverables - all present but not yet refined. Don't over-invest in v0; you'll learn more from shipping it than from polishing it. The cost of imperfect v0 is small; the cost of NOT shipping the first campaign is large. Ship v0 fast.

    Expected outcome

    v0 brief drafted in 60 minutes, queued for the first sprint.

  3. Run the first sprint, then capture what you learned in a 'lessons' block

    After sprint 1, write a 'lessons' block at the bottom of v0: what worked, what didn't, what surprised you. Top-3 performers. Bottom-3 performers. The audience cut that converted vs the one that didn't. This block is the raw material for v1; without it, the brief never improves.

    # Lessons block format:
    Sprint 1 lessons (Jul 14 - Jul 28):
    - Top performer: customer-testimonial archetype (CTR 2.1%, CVR 4.3%)
    - Bottom performer: founder-to-camera (CTR 0.6%) — KILL
    - Surprise: 'taste' angle outperformed 'performance' 3:1
    - Audience: 'currently uses generic' cut converted at 2x base

    Expected outcome

    Lessons block appended to v0 with concrete top/bottom performers and surprises.

  4. Develop v1 by tightening the angle and adding 1-2 do-nots

    v1 is the lessons-informed brief. The angle that overperformed becomes a stronger constraint ('lead with taste, not performance'). The archetype that underperformed becomes a do-not ('no founder-to-camera - confirmed cohort fatigue'). The audience cut that converted gets sharpened; the one that didn't gets removed. v1 should be SHORTER than v0 - tighter constraints mean fewer words.

    Expected outcome

    v1 brief shorter than v0; angle and do-nots tightened based on sprint 1 data.

  5. Build a 'do-nots library' that survives across briefs

    Some do-nots are campaign-specific ('no Christmas references in a summer campaign'). Others are brand-level ('we never use stock photography'). Separate the two. The brand-level do-nots go into a 'do-nots library' that gets pulled into every brief automatically. The campaign-specific do-nots stay in the brief. Over 6-12 months, the library becomes one of the most load-bearing brand assets you have.

    Expected outcome

    A separate do-nots library doc exists; brand-level do-nots have been migrated from briefs into it.

  6. Develop archetype expertise by tracking which archetypes win across briefs

    After 4-6 sprints, you'll have data on which hook archetypes consistently win for YOUR brand. Maintain an archetype scorecard: archetype name, win rate, average CTR, average CVR, last shipped date. Brief v3+ should default to the proven archetypes and only experiment with new ones when there's a specific reason. The archetype scorecard is the highest-leverage piece of compounding intelligence.

    # Archetype scorecard:
    - Customer testimonial · 9 shipped · win rate 67% · avg CTR 1.8%
    - Problem→solution · 12 shipped · win rate 58% · avg CTR 1.6%
    - Founder-to-camera · 4 shipped · win rate 0% · DO NOT USE
    - Day-in-the-life · 2 shipped · insufficient data

    Expected outcome

    Archetype scorecard maintained alongside the briefs; v3+ briefs default to proven archetypes.

  7. Develop AI-readability into the brief from v3 onward

    Once the brief is stable (v3+), engineer it for AI receivers. Three changes: explicit naming (no 'you know our voice'), heavier do-nots (AI defaults to category-average without them), named archetypes (no 'engaging hook'). The AI-readable brief is a brief humans also read better - the discipline of naming everything forces decisions out into the open.

    Expected outcome

    Brief v3+ contains explicit naming, named archetypes, and at least 5 specific do-nots.

  8. Develop the brief into team operating knowledge by v6+

    After 6-8 sprints, the brief stabilizes. New team members read it and produce on-strategy work without a meeting. AI generators produce closer-to-finished output. At this point, the brief IS the brand's creative operating system. Maintain it like infrastructure: version it, audit it quarterly, retire stale do-nots, add new archetype data.

    Expected outcome

    Brief is treated as operating knowledge; onboarding includes 'read the brief' rather than 'sit in 4 strategy meetings'.

Shuttergen

Develop briefs in days, not quarters.

Shuttergen tracks which angles, archetypes, and do-nots work across your sprints - then surfaces them as defaults in the next brief. Brief development happens automatically, not as a separate process.

Pitfalls

What goes wrong

  • Treating brief development as documentation hygiene

    Brief development is performance improvement, not doc maintenance. The metric is whether the next sprint's ads work better than the prior sprint's - not whether the brief looks tidy. Optimize for performance, not aesthetics.

  • Versioning briefs without capturing lessons

    Version numbers without lesson blocks are decorative. The brief gets better because lessons feed forward; without the lessons block, versions are just file timestamps.

  • Letting brand-level do-nots clutter campaign briefs

    If 'no stock photography' appears in every brief, it should live in a brand-level do-nots library and get pulled in automatically. Repeating brand-level constraints in every campaign brief inflates the doc and dilutes the campaign-specific constraints.

  • Defaulting to new archetypes when the scorecard says use the proven ones

    Novelty bias kills creative quality. If the scorecard says customer testimonial wins 67% of the time, the next brief should default to customer testimonial - even though that feels boring. Experiment in 20% of the cells; default to proven in 80%.

  • Treating the brief as a fixed asset after v6

    Brief development never ends. After v6 the cadence slows (maybe quarterly updates instead of per-sprint) but it shouldn't stop. Markets shift, audiences fatigue, new archetypes emerge. The brief that hasn't been updated in 12 months is starting to drift.

Limits

When this playbook won't work

  • You ship fewer than 5 ads per quarter - the compounding loop needs volume to work
  • You don't have a feedback loop on creative performance (you'll be versioning blind)
  • Your campaigns are wildly different from each other (one-off launches, no shared audience) - briefs don't compound across totally different campaigns
  • You're a 1-person team with no time for the versioning discipline - ship v0s and skip the development loop

Why creative brief development is a system, not a document

Most marketing teams write briefs as documents - one-shot artifacts that get drafted, shipped, and forgotten. This is the dominant failure mode. The brief becomes a checklist exercise; it never gets better because nothing forces it to. Each new campaign starts from blank or a stale template; the lessons of the prior campaign die in the team's memory.

Creative brief development reframes the brief as a versioned system. Each sprint generates lessons. Lessons feed into the next version. The brief gets sharper - shorter, with tighter constraints, with stronger do-nots, with proven archetypes. By the 6th-8th version, the brief contains years of compressed organizational learning.

The compounding is what matters. A team writing brand-new briefs every campaign is doing creative-quality from scratch each time. A team developing briefs across sprints is building a creative operating system. The gap between the two compounds: by year 2, the developed-brief team is producing 3-4x the creative quality at lower writing cost.

Develop briefs in days, not quarters. Shuttergen tracks which angles, archetypes, and do-nots work across your sprints - then surfaces them as defaults in the next brief. Brief development happens automatically, not as a separate process.

Develop briefs free

The artifacts that brief development produces

The current-version brief. Live document, updated after each sprint, the operating constraint for the next campaign.

The do-nots library. Brand-level constraints separated from campaign-specific ones, pulled into every brief automatically. The library typically has 12-20 entries by year 1 and 30-50 by year 2.

The archetype scorecard. Win rate, CTR, CVR by hook archetype across all shipped work. Defaults brief decisions toward proven archetypes; flags new archetypes as 'experiment' slots.

The lessons archive. All historical lesson blocks, sortable by date and campaign. Useful when a new team member joins, when a campaign fails and you need historical comparison, or when leadership asks 'what have we learned about creative this year?'.

Together these four artifacts ARE the creative operating system. The brief is the entry point; the supporting artifacts are what make the entry point load-bearing.

Internal: creative brief process, how to create a creative brief, creative brief template, what makes a good creative brief.

FAQ

Frequently asked

What's the difference between writing a creative brief and developing one?
Writing is the one-shot act of drafting a brief. Developing is the multi-sprint process of versioning, learning, and tightening the brief over time. Writing is episodic; developing is continuous.
How many sprints until a brief 'converges'?
6-8 sprints typically. After that, the brief becomes a stable operating doc with quarterly tweaks rather than per-sprint changes. The first 6-8 sprints are where the steepest learning happens.
Who owns creative brief development?
The marketer or strategist who owns the campaign series. If multiple campaigns run in parallel under different owners, each owner develops their own brief. The do-nots library and archetype scorecard are shared across owners.
How often should the brief be updated?
After every sprint, in the early development phase (v0-v6). Quarterly or as-needed after v6. The brief should never be more than one campaign behind on lessons.
What's the most important artifact to develop alongside the brief?
The archetype scorecard. Knowing which hook archetypes win for YOUR brand is the highest-leverage piece of compounding intelligence. Without it, every brief experiments from zero.
Can AI tools help with brief development?
Yes - AI tools can draft v0 in seconds, surface patterns across past briefs, and generate variants of proven archetypes. The development discipline still needs a human (the marketer owns the lessons and the strategic direction).
What happens if we stop developing the brief?
It decays. Markets shift, audiences fatigue, new archetypes emerge. A brief that hasn't been updated in 12 months is starting to mislead executors. Development never fully ends; the cadence just slows after convergence.

Related

Keep reading

Develop briefs in days, not quarters.

Shuttergen tracks which angles, archetypes, and do-nots work across your sprints - then surfaces them as defaults in the next brief. Brief development happens automatically, not as a separate process.