Most agencies treat the brief as a formality. You write one because you're supposed to write one. It's a scope document. It lists what you're doing, when you're doing it, how much it costs. Then you file it away and move to the actual work.
This is the wrong way to think about it. The brief isn't a scope document. It's a diagnostic tool. It's where you surface whether your client actually knows what they're asking for, or whether they think they know and they're wrong. The quality of the work that comes out of a project is determined almost entirely by the quality of the thinking that goes into the brief.
What a good brief actually reveals
When I write a brief with a client, I'm listening for the moment their clarity breaks. Most founders come in with a very clear understanding of what they want — for about sixty seconds. Then you start asking deeper questions, and the clarity starts to fracture.
They say they want to "reach a younger audience." You ask why a younger audience. They realize they don't have a specific reason; they just know their current customers aren't it. So you dig deeper. What problem are they solving? For whom? What are those people actually struggling with? And somewhere in the answers to those questions, a different brief starts to emerge than the one they came in with.
This is good. This is the brief doing its job. A brief that matches what the client walked in wanting is almost always the wrong brief, because what they walked in wanting is usually a solution in search of a problem, not a problem looking for a solution.
The real brief — the one that will lead to work that actually matters — emerges when you interrogate the assumptions underneath what they're asking for. Why does the brand need to change now? Because the market is shifting, or because they're shifting? What's actually different about them compared to their competition, or is that difference only in their head? What would success look like? How would you measure it?
These questions are not comfortable. Most clients don't like them. But the clients who trust the process — who understand that three hours of discomfort in a room asking hard questions is better than six months of designing something that doesn't solve the actual problem — those are the ones whose work succeeds.
The real question underneath the stated one
Almost every brief process involves translating what the client said they wanted into what they actually need. This is where the skill lives.
A founder comes in and says they need a website redesign. But as you talk, what they're actually saying is, "We built something smart, and the market is responding, but we can't articulate what we do in a way that makes sense to someone who doesn't already know us." The website redesign is the symptom they're pointing at. The real problem is that their communication strategy is incoherent.
Another founder says they need a rebrand. But halfway through the conversation, you realize the rebrand is actually code for, "I'm bringing in a co-founder and we need to reflect that we're not a solo act anymore." Or, "Our customers are changing and we need to reposition to serve the higher-value segment of the market." The rebrand is the tool they reach for; the actual work is usually somewhere else.
The brief is where you make this translation visible and explicit. You write it down. You share it back with the client. You say: "Here's what I think you're actually asking for. Here's why I think that's the real problem. Here's what we're going to solve." And the client reads it and either says, "Yes, exactly," or they say, "No, that's not it," and you keep digging.
The brief isn't done until that first response is yes.
How we write briefs differently
At Studio Novi, the brief is not a formality. It's where the real work starts. I spend as much time on the brief as I spend on the actual creative work — sometimes more. Because if the brief is wrong, nothing downstream fixes it. You can have brilliant design. You can have perfect execution. And if you're solving the wrong problem, the work still fails.
The brief process starts with deep questions. Not about what you want your brand to say, but about what's actually true about your business. Who are you serving? What problem do you solve that no one else solves the same way? What would your customers say about why they came to you instead of somewhere else? If you disappeared tomorrow, what would actually be different in the market?
These questions surface the real story. The story that's worth telling. The brief is where that story becomes explicit.
Then the brief also needs to be tight. Not vague, not aspirational, not philosophical. It needs to be clear enough that someone who wasn't in the room can read it and understand exactly what problem we're solving and for whom. This is the test: Could a designer I've never worked with read this brief and come back with something that's clearly the right direction? If they can't, the brief isn't done.
Why this matters
A bad brief produces good-looking work that solves the wrong problem. The design can be perfect. The craft can be excellent. But if the underlying strategy is wrong, the work doesn't work. It looks impressive and misses entirely.
A good brief produces the foundation for work that actually matters. When we get to the creative phase, we're not guessing. We're not trying three different directions hoping one of them lands. We're solving a specific problem for a specific audience because we've already done the thinking.
The brief is where the work is won or lost. Everything else is execution.