How to Define the Right Problem Before Writing the Brief

By the time a brief is written, the direction is often already set. The objective is implied, the format is beginning to take shape, and success is loosely understood, but rarely fully aligned. From there, the work moves forward, but its trajectory has already been constrained. 

What’s often missed is that the most important decisions don’t happen inside the brief. They happen just before it. 

Where Problem Definition Breaks Down

There’s a familiar pattern. A team is aligned on the need to do something. There’s momentum, a timeline, and pressure to move. So, the conversation shifts quickly to execution: what should we create, what kind of experience makes sense here, what have we seen work before? 

At that point, the problem starts to take shape, but not always in the right way. 

Inputs from different stakeholders introduce competing priorities. Known formats begin to anchor thinking. And success is defined in broad, often inconsistent terms. None of this is intentional, but it narrows the work before it’s fully understood. 

What begins as a question of what needs to change quickly becomes a question of what should we make. And once that shift happens, the work tends to follow a more predictable path. 

What a Well-Defined Problem Actually Does

When the problem is clearly defined, the work opens up. 

It creates alignment around what needs to change, not just what needs to be delivered. It gives the experience a clearer role, whether that’s shifting perception, driving behavior, or building something that extends beyond a single moment. And it allows for a wider range of solutions, because the work is no longer anchored to a predefined format. 

In this way, strong problem definition doesn’t limit creativity. It makes it more precise. 

What This Looks Like Before the Brief

There’s a distinct stage where this kind of clarity starts to emerge. It’s not formal, and it doesn’t look like a brief. But you hear it in conversations like: we know this needs to do more than just show up, or we want this to drive something bigger, or we’re not sure what the right format is yet.

This is the moment when the work is still open. And in that space, a few things begin to come into focus: what needs to change, not just what needs to happen; what’s getting in the way, including constraints, realities, and internal dynamics; and what role experiential should play within a broader system. 

This isn’t about solving a problem yet. It’s about defining the right problem to solve. 

The Takeaway

The quality of a brief is determined before it’s written. Because once the brief exists, much of the thinking has already been set in motion. The direction is harder to shift; the format is easier to default to, and the opportunity to shape the work at a more fundamental level has already passed. 

The real leverage sits earlier, in the space where the problem is still being defined, where alignment is still forming, and where better outcomes are still possible. That’s where experientially begins. 

Next week, we’ll look at what happens once the problem is clear and how to structure an experiential RFP that invites better thinking. If you’re navigating this stage now, or rethinking how your briefs are shaping the work, let’s connect.