The Brief Is Not the Problem Statement

The most important skill I've developed as a brand designer isn't drawing logos or choosing typefaces. It's learning to hear what a brief is actually saying versus what it literally says.

Clients are experts in their business. They're not usually experts in design problems. When they write a brief — or, more often, tell you what they want in a conversation — they're translating a business problem into design requests as best they can. That translation is almost always imperfect. Sometimes it's actively misleading.

What Clients Ask For vs. What They Need

"We need to look more premium." What they often mean: our current identity is creating friction with the segment of customers we're trying to reach. The solution might be a more refined identity — or it might be that the identity is fine but the brand experience around it is inconsistent.

"We need a modern logo." What they often mean: we feel like our brand is aging. But "modern" is a direction that changes every five years. A rebrand toward trendy minimalism might solve today's problem and create tomorrow's.

"We need something that stands out." What they often mean: we're losing competitive ground. Differentiation is the right instinct, but the right kind of differentiation depends on the market — sometimes bold color and loud type, sometimes restraint and precision.

I'm not saying clients are wrong. I'm saying the surface request is a symptom, not a diagnosis. My job is to diagnose.

How I Run Discovery

Before I accept any brand design brief, I run a structured discovery process. Not a questionnaire — a conversation. I want to understand:

The competitive context. Who are the direct competitors? What do their identities look like? Where is there visual territory nobody is occupying?

The audience. Who is this brand trying to reach? Not demographically, but attitudinally. What do they value? What brands do they already trust, and why?

The business context. Is this brand growing, stagnant, or declining? Is there a specific moment or milestone driving this project? What changes in six months that makes this urgent?

The internal context. Who will be implementing this identity? What are their capabilities and constraints? A brand system designed for a company with a full in-house design team needs to be different from one designed for a company where the CEO makes the slides.

The Real Problem Often Lives Here

In my experience, the actual design problem reveals itself in the business and competitive context questions, not in the design questions. A company that says "we need to look more premium" often reveals, when you dig, that they've just moved upmarket and their existing identity was built for a different customer. The problem isn't aesthetic — it's that the identity is aimed at the wrong target.

That diagnosis changes the solution entirely. Instead of "make the logo look more expensive," the actual brief becomes "rebuild this identity to signal credibility to a more sophisticated buyer." Different constraints, different references, different outcomes.

When the Brief Is Right

Sometimes the brief is right. Sometimes the client has done the diagnosis themselves and knows exactly what they need. When that happens, I don't complicate it. I work to the brief.

But I only trust the brief after I've checked it against the underlying problem. The moment of discovery is when I ask a question that produces a long pause, followed by "huh, I hadn't thought of it that way." That's when I know I've found the actual brief.