The design brief is already too late.

By the time the design brief lands in your designer's inbox, the audience has been defined, the positioning has been written, and the offer has been structured. The brief describes what to make. Every decision about what it needs to accomplish was already made without the designer in the room.

A quick note on terms before we go further. The brief is the document handed to design after strategic decisions are made, describing what to build. The GTM design layer is the websites, landing pages, decks, and campaign assets where strategy meets the customer. Design before the brief is design input applied during positioning and diagnosis, before the brief is written.

The brief is a closing document, not a starting point

The brief signals that strategy is done. It does not signal that the work is beginning.

A client sent me a six-page brief on a Tuesday. Thorough, well organized, clear on the audience, the core message, the campaign objective, and the asset list. What it did not include was any of the thinking that produced those decisions, because that thinking had happened four weeks earlier at a leadership offsite. By the time the brief arrived, every meaningful decision was already made.

The design work that followed was technically sound. The campaign ran. The results were mediocre. Six months later, the team was still searching for what went wrong at the execution level, because nobody thought to question what arrived in the brief.

What this means for you: if your team is reviewing completed campaigns and the problem is always traced back to execution, look at when the brief was written. The execution is often fine. The brief arrived too late to shape anything that mattered.

Why "a seat at the table" changes nothing

Giving designers a seat at the strategy table is the standard fix, and it doesn't work if the brief is still written after all decisions are finalized.

Most marketing managers have been in a kick-off where the design team was invited for the last 15 minutes to hear "what we're building." That is not involvement. That is notification. The decisions are already made, the presentation is already prepared, and the designer's job at that point is to ask clarifying questions about the brief they are about to receive.

Even when designers are involved earlier in name, the structural problem persists. The designer in the room is witnessing decisions, not shaping them. You can change the org chart, add cross-functional syncs, build a culture of creative collaboration, and none of it changes the underlying sequence: strategy first, design after.

What this means for you: if you have added design to your strategy meetings and the work still feels reactive, the problem is not attendance. It is when the brief gets written relative to when decisions get made.

The sequence is the problem, not the culture

Design keeps reacting because the sequence puts it there, not because of talent, budget, or organizational attitude toward creative work.

In a standard B2B GTM motion, the order of operations looks roughly like this: define the ICP, develop the positioning, write the messaging hierarchy, choose the channels, set the budget, build the plan, brief the designers. Design is last. Not because anyone decided it should be last, but because it is the layer that makes everything else visible, and making things visible feels like the final step.

The problem is that the GTM design layer is not just aesthetic output. It is the surface where strategy meets the customer. The website is not a brochure for the positioning, it is the positioning, experienced by a real person under time pressure with a dozen other tabs open. If the positioning is wrong, the website is wrong in a way no amount of visual refinement will fix. But by the time the brief arrives, the positioning has been approved, the stakeholders have signed off, and questioning the message is no longer a design decision. It is a political one.

What this means for you: if your design team is producing polished assets that still don't convert, ask whether they had any input on the positioning and message before the brief was written. If not, the problem was baked in before a single file was opened.

What changes when design enters before the brief exists

When design is involved while positioning is still being stress-tested, the questions are completely different.

Not "what color should the CTA be" but "does this page reflect what we're actually promising?" Not "carousel or grid" but "does the structure of this page match the argument we're making, and does it match the way our ICP actually reads?" These are GTM questions that require design literacy to ask and design judgment to answer. Most strategists don't have that literacy, and most designers don't have the strategic access to apply their judgment at the right moment. The brief is the mechanism that enforces the separation.

When I run the Montovera Diagnostic with a new client, the most common finding is not that their design is bad. It is that their design brief arrives after every strategic decision has already been made. The Diagnostic audits the four phases that precede execution: what signals the business is reading, how those signals are being interpreted, where the actual breakdowns are, and what the strategic direction should be before anyone opens a design file. By the time brief-writing begins, the design direction is almost already obvious, because the argument has been made and tested against what the GTM surface actually needs to do.

What this means for you: design before the brief is not a meeting. It is a different order of operations, with design literacy applied while strategic decisions are still open.

The brief will keep arriving late until someone changes the order

The organizations stuck in reactive design are not stuck because of bad designers or a disrespectful culture. They are stuck because the sequence is wrong and nobody has formally changed it.

Changing the sequence means deciding that design input happens before the brief exists, not because of it. It means treating the GTM design layer as part of the diagnostic and strategic phases, not as a production step that follows them. The brief feels like a clean handoff because it reduces ambiguity and gives the designer something to work from. What it also does is arrive with every meaningful decision already made, leaving design with the job of dressing a strategy it was never asked to shape.

The sequence is inherited, not inevitable. Anyone willing to question it can change it.