Creative brief powerpoint template

A deck brief and a doc brief are not the same instrument. A doc brief is a working document - dense, edited continuously, lives in Notion or Google Docs, optimized for *writing*. A deck brief is a presentation artifact - visual-first, presented to stakeholders for buy-in, optimized for *reading at a glance*. Both have legitimate uses; the question is which one your context needs.

Use a deck brief when: (1) the brief needs C-suite sign-off (executives consume decks faster than docs), (2) the brief includes a lot of visual reference (decks display ad thumbnails inline natively), (3) the brief is presented to clients in agency contexts (decks are the agency-industry standard format), or (4) the campaign is complex enough that a presented walkthrough beats a self-read doc.

Use a doc brief when: (1) the brief is a working document edited continuously through production, (2) the team is small enough that a meeting isn't needed, (3) the brief is long enough that pagination matters more than slide pacing, or (4) the team is doc-native (most modern in-house teams).

Ten slides is the sweet spot between completeness and present-ability. Fewer than seven and you lose load-bearing sections (audience, do-nots, deliverables get compressed). More than fifteen and you've built a working doc disguised as a deck - it stops being presentable in a single meeting.

The structure above puts the angle on slide 5 by design. The first four slides establish context (cover, background, goal, audience). The angle - the single load-bearing decision - lands at the deck's midpoint, in 36-48pt type filling the slide. Slides 6-10 operationalize the angle (how to express it, what to avoid, what to ship, when).

Slide 5 is the deck's hinge. If your angle slide can't carry full-slide treatment - if the angle has to be paragraph-length, with sub-bullets and qualifications - the angle isn't tight enough. The deck format forces the compression that a doc brief lets you avoid. That's a feature.

PowerPoint: download the .pptx template directly. Native Office-suite formatting; uses Calibri (default) and works across versions back to PowerPoint 2016. If you're using PowerPoint 365, the template imports without conversion losses.

Keynote: PowerPoint imports into Keynote with light formatting loss (font substitution if Calibri isn't installed - usually swaps to Helvetica Neue). Recommended: re-apply theme fonts after import. The structure preserves cleanly.

Google Slides: upload the .pptx to Drive, then open with Google Slides. Most fonts substitute correctly; the table on slide 8 may need manual re-alignment. Best for distributed/remote teams collaborating in real-time during brief reviews.

Figma slides / Pitch / Notion deck: the structure transfers but you'll lose Office-native table formatting. Recommended only if your team is already deck-native in one of these tools; otherwise stay in PowerPoint/Keynote/Slides where the formatting holds.

The slides are the artifact; the speaker notes are the meeting. Each slide above should have 3-5 lines of speaker notes that go deeper than the slide content: why this audience cut, why this angle versus the alternatives considered, what was rejected from the do-nots and why. The slides survive past the meeting; the notes are what makes the meeting valuable.

Don't read the slides. A common failure mode in brief presentations is reading the slide text aloud. The audience can read; your job is to add the layer that isn't on the slide - the reasoning, the rejected alternatives, the calibration on resolution. If your speaker delivery is identical to the slide text, the meeting could have been an email.

Time the deck for 15-20 minutes presentation + 15-20 minutes discussion. Anything longer than 25 minutes presented is a deck that should have been a doc - the audience has stopped engaging by the time you hit slide 7. Tighter slides, tighter walkthrough.