The brief nobody wants to write (and why skipping it costs you later)
Nobody wants to write it. Every project needs it.
SEPTEMBER 18, 2026 / Estimated read time: 4-5 minutes
Every project has a moment where someone wants to skip straight to "let's just start." No brief, no scope conversation, no real answer to what success actually looks like.
Briefs feel like paperwork. Nobody hires an agency to fill out a form together, they hire one to make things.
But skipping the brief doesn't save time. It just moves the pain later, into revision rounds, scope arguments, and a final product that technically works but that nobody's especially proud of.
At HRVST, the brief is the actual start of the project, not a formality before the real work begins. Here's why.
What happens when you skip it
Without a real brief, everyone's operating off their own version of the project. The client pictures one thing. The team designs toward another. Feedback starts contradicting itself round after round, not because anyone's being difficult, but because nobody agreed on what "done" looks like in the first place.
Revisions stack up. Timelines slip. The work that finally ships is usually a compromise between assumptions rather than a clear answer to a clear problem.
None of that is a talent problem. It's a process problem, and it starts on day one.
A brief isn't paperwork (it's a blueprint)
A good brief costs an hour or two at the very start. Skipping it can cost weeks later, in revisions that shouldn't have happened and conversations that should've happened before the work began.
At HRVST, we think of the brief as the blueprint for the whole project. It's not there to slow anyone down. It's there so the fast part, the actual building, can move without second-guessing.
What actually belongs in one
A good brief isn't long. It just has to do a few things well.
It has to get at the why, not just the what. A rebrand driven by "we're embarrassed handing out our business card" needs a different answer than one driven by expansion into a new market. Skip that question and you can end up solving the wrong problem beautifully.
It has to capture taste, not adjectives. Ask someone to describe their brand and you'll usually get "modern but timeless." Ask what they love and what makes them cringe, and you'll get something a team can actually design toward.
It has to turn feeling into direction. Tone, personality, energy, these things are hard to pin down in words alone. A good brief's job is to translate them into something specific enough that two people reading it land on the same idea.
And it has to say what's out, not just what's in. The least exciting line in any brief is usually the most valuable one: the part that names what's not included. It's the difference between a scope everyone agreed to and a scope that quietly grew.
Get those things right, and most of the ambiguity that usually shows up mid-project never gets the chance to.
The pushback we hear the most
The objection we hear most is "we already know what we want, let's just start." Sometimes that's true. More often, everyone in the room has a slightly different version of "what we want," and nobody's noticed the gap yet because nobody's actually said it out loud.
A brief isn't there because we doubt anyone's instincts. It's there because instincts described out loud almost always turn out more specific, or more different from the next person's, than instincts left unsaid. Writing it down is how everyone finds out, before the work starts, whether they actually agree.
The other pushback is timing: we're in a rush, can we skip ahead. Rushed projects are exactly the ones that can least afford to skip this step. A vague brief on a tight timeline doesn't save time. It just moves the confusion into the one phase where there's no room left to absorb it.
What it actually saves you
The math isn't complicated. A brief takes an hour, maybe two, to do properly. A project without one routinely burns entire extra rounds of revisions untangling misunderstandings that a single clear conversation would have caught on day one.
That trade doesn't show up as a line item anywhere. Nobody bills a client for "time spent guessing." It just shows up as a project that ran longer than it should have, for reasons nobody can quite point to after the fact.
Projects that start with a real brief tend to move in the opposite direction. Feedback rounds get shorter because there's a shared reference point to check work against instead of a moving target. Fewer conversations start with "that's not what we meant." The making part just moves faster, because it isn't constantly stopping to re-litigate what it's making.
A brief doesn't slow the work down. It's what makes the work worth shipping. The projects that come out of our studio the cleanest are almost always the ones that started with the clearest answers, not the ones that skipped ahead.
If you're heading into a new project, budget the hour. It'll save you the weeks.
