The brief behind the brief

“We need a new website.”

We hear some version of that sentence more than any other, and after fourteen years we can tell you it’s almost never about the website. It’s a symptom presenting as a diagnosis. Somewhere upstream, something happened: a competitor launched something impressive, sales flattened, a new executive arrived with a mandate, the founders looked at their own homepage and felt a small private shame. The website is just where the feeling landed.

This is why the first phase of our process looks less like design and more like detective work. Not because we distrust clients. Because the brief is a translation, and translations lose things.

The request is evidence, not instruction

Think about how a brief gets made. Someone inside the company notices a problem. They describe it to a colleague, who reframes it for a boss, who assigns it a budget line, which requires naming it something procurable. By the time it reaches an agency, the original problem has been converted into a purchase order for the most plausible-sounding solution. “Our positioning is muddled and our sales team can’t explain what we do” becomes, through this game of corporate telephone, “we need a new website.”

Take the brief at face value and you’ll deliver exactly what was asked and none of what was needed. The site launches, everyone celebrates, and eight months later the flat sales are still flat, because the website was never the patient. It was the waiting room.

So we treat the stated request the way a good detective treats a witness statement. Sincere, useful, and incomplete. Evidence of the truth rather than the truth itself.

What the detective work looks like

Discovery, done honestly, is mostly asking one question in escalating forms: what happens if this goes perfectly? Push on it a few times and the real brief starts surfacing.

“We need a new website.” Okay, it launches and it’s beautiful. What changes? “Well, leads should go up.” Why aren’t they coming in now? “Honestly, people get to the site and don’t understand what we sell.” Do people understand it when your team explains it in person? “…Not really, no.”

Four questions in and we’re not talking about a website anymore. We’re talking about positioning, and any pixel pushed before that conversation would have been expensive decoration. That exchange is a composite, not a transcript, but we’ve had it so many times we could set it to music.

The other thing we do is watch for the gap between what a company says and what it does. We ask to see:

• The sales deck the reps actually use, which is never the official one.
• The support tickets, all of them if the pile allows.
• The newest employee, who gets asked what confused them in week one, because they still remember.

Companies, like people, are most honest in their unguarded habits, and a brief is the opposite of an unguarded habit.

A brief has been to three meetings and had its hair done.

The question behind the question

Over the years we’ve built a rough field guide. “We need a rebrand” often means we’ve changed and our image hasn’t, and it’s starting to cost us. “We need an app” frequently means our internal process is chaos and we’re hoping software will impose discipline that management hasn’t. “We need more content” can mean almost anything, which is precisely why it needs the most interrogation. And “we need a new agency” sometimes means the last agency did exactly what the brief said.

None of this makes the client wrong. Sometimes the brief behind the brief, once excavated, turns out to be the original request after all, and the site really does just need rebuilding. Great. Now we’re building it for the right reasons, with everyone agreed on what success means, and that agreement is worth every awkward question it took to get there.

What we won’t do is skip the excavation because the purchase order is ready. An agency that takes every brief literally isn’t being respectful. It’s being convenient, and billing for it.

Why clients put up with this

Fair question, since the detective phase can feel like stalling to a team that arrived ready to pick fonts. The answer is that the interrogation is the cheapest part of the entire project. A hard question in week two costs an hour of mild discomfort. The same question unasked costs a rebuild in year two. Every experienced client we’ve worked with has lived through the second version somewhere else, which is why they’re the ones who lean into discovery hardest. They know what a beautifully executed wrong answer costs.

Our favorite moment in any engagement comes near the end of discovery. It’s when someone on the client side, usually the person who wrote the original brief, says some version of: huh, that’s not what I thought we were asking for, but it’s what we meant.

That sentence is the actual deliverable. Everything we build afterward is just proof.