A brief that starts with format and channel gets you polished work with nothing underneath it. This is the walkthrough of how I actually brief a creative team: concept before channel, idea before deliverable, every time. Here’s what that looks like in the room.
The brief that kills the idea before it’s born
Most briefs walk in the door already dressed for production. Fifteen-second cutdown. Three static posts. A landing page with a hero image and two CTAs. The deliverables are decided before anyone in the room has said a single true thing about the brand or the problem.
I don’t work that way, and I don’t let clients hand me a brief that works that way either.
Execution-first briefs feel efficient. They give the team something to point at, a shape to fill. But a shape isn’t an idea. When the format gets locked before the concept does, the team spends the whole project decorating a decision nobody made on purpose. You end up with something technically correct and completely forgettable, a video that hits fifteen seconds on the nose and says nothing anyone will remember by the time the next one loads.
Safe doesn’t survive here. And a brief that starts with specs instead of substance is the safest, most forgettable move there is.
So I start somewhere else. Before a single deliverable gets named, I ask what the idea is. Not the tagline. Not the visual direction. The one true thing this project needs to say, and why it matters to the person on the other end of it. Everything downstream, channel, format, length, medium, gets decided after that answer exists, because those choices should serve the idea, not replace it.
The one-sentence test
Here’s the actual mechanic. Before a brief leaves strategy and lands on a creative team’s desk, someone has to write the concept in one sentence. Not a paragraph of positioning language. One sentence, plain enough that a stranger at a coffee shop would understand what the work is trying to do and why it’s worth doing.
If I can’t get the idea down to one sentence, it isn’t ready. That’s not a stylistic preference, it’s a diagnostic. A concept that needs three paragraphs to explain usually means nobody has actually found the idea yet, they’ve found a description of the problem instead. Problems aren’t ideas. A problem statement tells you what’s wrong. A concept tells you what you’re going to do about it, and why that specific move is the right one for this specific brand.
“If I can’t get the concept down to one sentence, it isn’t ready. That’s not a style preference. It’s a diagnostic.”
I’ve killed strong-sounding directions at this stage because they couldn’t survive the sentence test, and I’ve saved rough, unglamorous ideas because the sentence was undeniable even when the deck around it wasn’t. The sentence is the whole point. Everything else is packaging.
How I pressure-test a concept before it touches production
A concept that survives the one-sentence test still has to earn its way into production. This is where I get hard on the work and soft on the person who brought it, because the two are not the same thing and treating them like they are is how teams stop taking risks.
The pressure test asks three questions, out loud, in the room, before a single asset gets built. Would the audience feel seen by this, or does it play it safe in a way that just looks busy? Does the idea survive if you strip the polish, the music, the typography, and say it flat? And is this specific to this brand, or could a competitor’s name slot into the same headline without anyone noticing the difference?
That last one kills more concepts than anything else. A lot of creative work is technically good and completely swappable. If the idea works just as well for the brand next door, it isn’t a concept, it’s a template with better lighting.
I run this pressure test collectively, not from one desk. Strategy, creative direction, and whoever built the idea sit in the same room and argue about it honestly before it goes further. Nobody’s title makes their objection more or less valid. That’s not a nicety, it’s how weak ideas actually get caught before a client ever sees them, and how strong ones get sharper instead of watered down by committee.
Building briefs loose enough for craft to happen
Once a concept clears the pressure test, the brief that goes to the team building it looks nothing like the execution-first version I started with. It names the idea in one sentence. It names the audience and the one thing they need to feel. It names the non-negotiables, brand marks, legal constraints, platform requirements that actually can’t move.
And then it stops.
It does not name the exact shot list. It does not pre-decide the edit rhythm or the exact copy line before a writer has had a chance to find something better than what strategy imagined at a desk. A brief that specs everything out isn’t protecting the idea, it’s boxing out the craft that’s supposed to bring the idea to life. I don’t dictate, I educate. I hand the team the why and the guardrails, and I trust the people doing the work to find the how.
“A brief that specs everything out isn’t protecting the idea. It’s boxing out the craft that’s supposed to bring it to life.”
This is the part clients sometimes have to get comfortable with. A loose brief can look like a less finished brief. It isn’t. It’s a brief that’s finished with the right things and deliberately open on the things that should stay open until a photographer, editor, or writer gets their hands on it. The industry has spent years rewarding this instinct at the highest level. When Cannes Lions introduced its Creative Effectiveness Lions in 2011, it built an entire award category around campaigns proven to work in the real world, not just campaigns that looked good in a case study reel (Wikipedia, "Cannes Lions"). The idea has to hold up on its own before the execution gets to take a bow.
What this looks like when it works
When a concept-first brief works, you can feel it before you can measure it. The team isn’t asking "what do we build next," they’re asking "does this still serve the idea." That question only makes sense if the idea got locked before the deliverables did.
D&AD has run its student New Blood Awards on a version of this same principle since 1979, handing emerging creatives real briefs from working agencies specifically to close the gap between classroom polish and the harder discipline of finding an idea that means something before you touch production (Wikipedia, "D&AD"). The lesson holds at any level of experience. Craft is not the hard part. Finding the thing worth crafting is the hard part, and it’s the part a rushed, execution-first brief skips.
I’d rather hand a team a rough concept that’s true than a polished spec sheet that’s empty. The rough concept gets better in the room. The empty spec sheet just gets more expensive to produce.
If this is the problem you’re facing, let’s talk.
