The Problem With Your Brief Is That It’s a Solution

Most briefs don’t begin with a problem. They begin with a decision.

By the time a brief reaches us, the shape of the work is often already implied: a new site, a refreshed brand, a campaign, a tool. These are rarely bad ideas, and often they’re thoughtful ones. But when the brief starts with the solution, it quietly narrows the work before it has a chance to open up.

Not because teams aren’t thinking deeply, but because they’re operating inside real constraints.

Deadlines, budgets, board expectations, internal alignment. The pressure to be decisive. The need to show progress. A solution feels concrete and defensible in a way a loosely defined problem does not. It gives everyone something to point to and move toward, even if it skips over the harder question of whether it’s the right thing to be doing at all.

And that’s where things start to slip.

Why solution-first briefs feel responsible

Solution-first briefs are simply a response to uncertainty.

Problems are uncomfortable. They invite interpretation, disagreement, and sometimes uncomfortable truths about structure, incentives, or leadership. Naming the real issue can widen the scope in ways that feel risky or unmanageable, especially inside complex organizations. A solution, by contrast, feels containable. It can be scoped, approved, budgeted, and scheduled.

So the brief jumps ahead.

Instead of asking what’s not working, it assumes the answer and moves on. The work becomes less about discovery and more about execution — about making something fit rather than understanding what’s actually needed.

You can still make good work this way. Sometimes, even very good work. But it tends to optimize for momentum rather than meaning.

What happens when the ending is decided too early

When a brief dictates the solution, everything downstream subtly rearranges itself to support that choice.

Research gets framed to confirm it. Strategy fills in justification. Design explores variations within a narrow lane. Questions that don’t neatly serve the outcome are deprioritized or left unasked altogether. The work becomes efficient, but also constrained.

Over time, this shows up as brands that don’t quite cohere, products that feel busy rather than purposeful, and systems that struggle to adapt because their foundations were never fully examined. The issue isn’t that the solution was wrong — it’s that it was never tested against the real problem in the first place.

A brief reflects more than the ask

A brief is never just a list of requirements. It reflects how an organization understands itself.

What it names, what it avoids, and what it assumes all reveal where decisions are being made and what kinds of questions are considered acceptable. A brief that says “we need a new logo” may actually be pointing to something deeper: a loss of shared language, a shift in identity, or a growing disconnect between how the organization operates and how it presents itself to the world.

A logo might be part of the answer. Or it might not. Without pausing to understand the underlying issue, it’s impossible to know.

This is where problem-first thinking matters. Not as a methodology, but as a discipline.

The difference a small reframing makes

Starting with the problem doesn’t require a dramatic overhaul. Often, it’s a simple shift in how the question is framed.

Not “we need a new website,” but “people don’t understand what we do anymore.”

Not “we need to modernize,” but “our current systems no longer support how we actually work.”

That small change creates space. It allows multiple paths forward, some lighter, some more structural, some unexpected. It opens the work up to judgment and prioritization rather than locking it into a single predetermined outcome.

More importantly, it creates room for honesty about constraints, tradeoffs, and what success actually looks like.

Solutions still matter—just not first

None of this is an argument against solutions. Solutions are the point.

But when they arrive too early, they tend to protect something—a timeline, a budget, a decision already made—rather than serve the underlying need. A strong brief doesn’t prescribe the answer. It frames the question well enough that the right answer can emerge.

That requires patience, trust, and a willingness to sit with ambiguity a bit longer than most teams are used to. The payoff is work that holds together over time, not just at launch.

Before finalizing the next brief, it’s worth asking one quiet question:

What problem would we name if we weren’t already attached to the solution?

That’s usually where the real work begins.