Grounded With Data

A brief can look complete and still be doing the wrong job.

When the problem, audience, channel, budget, and ex*****on method are already decided before the strategist enters the room, you’re not asking for expertise.

You’re handing over instructions.

That may feel efficient, but it usually cuts out the thinking that makes the work better.

A good brief should create orientation, not obedience. It should clarify the problem, name the real constraints, and leave room for the person you hired to bring their expertise to the table.

Because at some point, a “brief” that tells someone exactly what to do stops being a brief.

It becomes an order form.

(Post created courtesy of Yeliza Centeio.)

Some of the most important project inputs never make it into the brief.

Not because anyone is hiding them on purpose.

Because assumptions, internal tensions, competing priorities, and quiet concerns are often hard to capture in a document.

That’s why the conversation before the brief matters so much.

A useful project kickoff should surface what people are saying clearly, and what they may only be implying. The hesitation. The repeated point. The thing someone circles back to. The disagreement no one has fully named yet.

Those are often the signals that tell you what the work is really about.

Before we ask, “What should the brief say?” we ask something better:
What needs to be uncovered before the brief can make sense?

(Post created courtesy of Yeliza Centeio.)

The best briefs don’t prescribe the answer.

They define the problem.

They name the real constraints.

They give the person doing the work enough context to make smart decisions.

That’s it.

When a brief tries to solve the problem before the expert gets involved, it quietly removes the very thing the expert was hired to bring: judgment.

A strong brief should say:
Here’s what we’re trying to solve.
Here’s what cannot move.
Here’s what success needs to look like.

Then it should leave room for expertise to do its job.

(Post created courtesy of Yeliza Centeio.)

We’re not against briefs.

We use them. We rely on them. We believe in documenting decisions clearly.

But the sequence matters.

A brief written before the right people have been in the room can create the appearance of clarity while hiding the actual problem. It can make everyone feel like the project is moving forward, even when the alignment hasn’t happened yet.

That hidden tension does not disappear.

It waits.

Then it shows up later as rework, confusion, stalled decisions, or a stakeholder suddenly saying, “Actually, this isn’t what I had in mind.”

The better sequence is simple:
Talk first.
Surface the real problem.
Find the disagreement.
Then write the brief.

(Post created courtesy of Yeliza Centeio.)