Creatives do not hate briefs. They hate the particular kind of brief that wastes their talent: vague on the goal, rigid on the execution, and rewritten three times before the work even starts. If your creative team seems prickly about briefs, the brief is probably the problem, not the team.
A creative brief is a written agreement about three things: what we are making, who it is for, and how we will know it worked. Everything else is helpful context. If those three are missing or fuzzy, you do not have a brief. You have a suggestion.
What do creatives actually need from a brief?
Three things: context, constraints, and freedom. Context tells them why this matters and who it is for. Constraints tell them the budget, the timeline, and anything genuinely fixed. Freedom is the space between, where their talent actually lives.
Most briefs get this backwards. They are thin on context, vague on constraints, and prescriptive about the execution. That combination tells a talented team two things: you do not trust us, and you have not thought this through. Neither builds goodwill.
What kills goodwill before the work starts?
The fastest goodwill killer is prescribing the solution. Tell a designer to make the logo bigger and blue and you have given art direction, not a brief. Describe the problem instead, and let the team solve it.
The second killer is the moving brief. Every time the goal shifts mid project, the team quietly recalculates how much of their work was wasted. Do it twice and they stop investing. A stable brief is a sign of respect. For the longer version of what a real brief contains, read the brief that was not a brief.
How much context is enough?
Enough that the team could explain the project to a stranger at a party. Who the audience is, what they care about, what has been tried before, and what success looks like in plain language.
Context is not a data dump. Ten pages of background nobody reads is worse than useless, because it looks thorough while teaching nothing. One page of sharp context beats a deck of vague slides. If you are briefing external help, the same rules apply in how to brief a contractor for a brand project.
Should you show them examples?
Yes, but show them as direction, not destination. Saying you like the energy of a reference, not the look, is useful. Saying make it look like this turns your team into photocopiers.
References work best when you explain what you are pointing at. Mood, tone, ambition level, craft standard. Without the explanation, the team guesses, and they will guess wrong in the most expensive direction.
What does a good briefing meeting look like?
Short, with the decider in the room. Twenty to thirty minutes is plenty if the written brief did its job. The meeting exists for questions, not for reading the brief aloud.
End the meeting with the team playing the brief back to you in their own words. If their version matches yours, you are aligned. If it does not, you just saved yourself two weeks of wrong work. That playback step is the cheapest quality control in the whole project.
Working with Avy
Briefing is a delivery skill, not a writing skill. The test of a brief is not whether it reads well, it is whether the team can act on it without coming back with twenty questions. I stress test briefs for a living, usually in week one of an engagement.
If your projects keep starting soft and getting harder, the brief is the first place I would look. Book a call and bring your latest brief. We will read it the way a creative team would.
Need someone to get your project over the line?
Project delivery support for brand, digital, and creative teams that need clearer direction and smoother progress.