The brief is the product

There's a particular kind of meeting we've sat in too many times. A piece of work has come back, and it's not right. The tone is off, or it answers a question nobody asked, or it's technically fine and entirely forgettable. Someone says, carefully, that the writer “didn't quite get it.” And almost always, when we ask to see the brief, we understand exactly why. The writer got precisely what they were given.

Teams treat briefs as throat-clearing — a formality before the real work starts. That's the mistake. The brief is the work. It's the moment where all the thinking happens: who this is for, what it has to achieve, what “good” looks like. Everything after that is execution. If the thinking is vague, no amount of talented execution will rescue it.

A bad brief just moves the work later

A thin brief doesn't save time; it defers it, at a worse exchange rate. The decisions you skipped don't disappear — they resurface during revisions, when they're ten times more expensive to make. Now you're not adjusting a plan, you're rewriting a draft, renegotiating a structure someone has emotionally committed to, and burning goodwill on both sides. The cheapest place to change your mind is the brief. The most expensive is the third round of edits.

Vague in, vague out. A writer can only be as clear as the thinking they were handed.

This is why we've come to treat the brief as the actual deliverable of a content team. The article is what the reader sees, but the brief is what determines whether the article is any good. Get fluent at briefs and your whole operation gets faster — not because people write quicker, but because they write the right thing the first time.

What a real brief contains

A good brief is short but not vague — those aren't the same thing. It fits on a page, and every line earns its place. After a lot of iterations, this is the shape we keep coming back to:

• The one job. In a single sentence, what should this piece change in the reader's head or actions?
• The reader. Not a persona document — the real person. What do they already believe, and what would make them stop scrolling?
• The single takeaway. If they remember exactly one thing, what is it? Everything else supports this or gets cut.
• The angle. Why us, why now, why this take and not the obvious one everyone else has published.
• The proof. The specific examples, data, or stories that make it credible — gathered before drafting, not hunted for after.
• The bar. One or two links to work that hits the standard, so “good” isn't a matter of taste argued in the comments.

Write it with the maker, not at them

The best briefs aren't handed down; they're built in a short conversation with the person who'll do the work. Fifteen minutes talking it through surfaces the assumptions that would otherwise only appear in the first draft. You want those collisions to happen at the brief stage, where they cost a sentence, not a weekend. It also makes the writer an owner of the idea rather than a contractor executing a spec — and people do their best work when they understand the why, not just the what.

The test

Here's the simplest way to know if a brief is doing its job: hand it to someone who wasn't in the room. If they can tell you what the piece is for, who it's for, and what it should say — without asking a single follow-up — the brief is the product, and the writing is just the part everyone can see. If they can't, you haven't saved time by skipping the thinking. You've only hidden it somewhere more expensive.