A company commissions a new campaign, website, or platform.

The agency meets the brief, stakeholders approve the creative, and the work launches on schedule.

A few months later, the problem that prompted the project is still there. Lead quality hasn't improved, customers are still confused, or the new tool sits mostly unused.

When that happens, the execution usually gets the blame, but the brief is often the more useful place to look.

Many briefs describe in detail what should be produced while saying very little about why the work is needed or what should be different once it's done. A team can deliver exactly what was asked and still miss the outcome, because the request was a guess about the solution rather than a description of the problem.

A clear deliverable isn't the same as a clearly defined problem

Briefs tend to be most specific about what's easiest to describe:

• Deliverables

• Features

• Timeline

• Budget

• Visual preferences

Those details matter for production, but behind every requested deliverable is an assumption about what's wrong, who it affects, and what would fix it.

Separating those pieces makes the gap visible. The deliverable is what the organization has asked for, such as a new website. The business problem is the reason it's asking, perhaps that prospects leave without contacting sales. The people affected are the specific audience whose behavior needs to change, the outcome is what needs to be true afterward, and the evidence is what would show the work is moving in that direction.

A brief can be precise about the deliverable and vague about everything else, and when that happens, success quietly defaults to whether the deliverable launched.

The way marketers and agencies see briefs suggests this gap is common. In the BetterBriefs Project survey of more than 1,700 marketers and agency staff, published by the IPA in 2021, 78% of marketers said their briefs gave clear strategic direction, while only 5% of agency respondents agreed. Agencies aren't neutral judges of their clients' briefs, but a gap that wide suggests the reasoning behind a brief often stays with the person who wrote it.

Challenge the assumptions before they become requirements

For example, take a B2B company that approaches an agency because lead quality is declining. The brief is direct: "We need a new campaign to improve lead quality." It goes on to request campaign concepts, a set of assets, a channel plan, and a launch date next quarter.

Before starting, the team asks what declining lead quality actually looks like. Inquiry volume has held steady, so attention isn't the obvious problem. The more revealing evidence comes from sales. Recent discovery calls and the reasons opportunities were disqualified show a pattern: many prospects arrive believing the company offers a service it doesn't, or can't explain how it differs from two better-known competitors. Some of the best-fit buyers ask questions that the website and sales materials never answer.

That changes the diagnosis. If prospects misunderstand what the company does, a campaign that generates more attention could simply bring in more poorly matched leads. The problem looks less like reach and more like positioning and proof, helping the right buyers recognize whether the company can solve their problem.

The revised brief reads differently: "Prospective customers are engaging with our marketing but struggling to understand which of our services address their needs and how we differ from alternatives. We need to clarify our positioning and supporting evidence so better-fit buyers can evaluate us accurately." It names the audience, such as operations leaders at mid-sized manufacturers, and the evidence behind the diagnosis. Its outcome is a higher share of qualified opportunities rather than more inquiries, and progress is judged by whether sales sees fewer early disqualifications and whether prospects arrive at first calls able to describe what they need. A campaign may still be part of the answer, but its job, message, and measures have changed.

The questions that did the work were simple. What does the problem look like in the information we already have? Who sees it most directly, and what are they hearing? What else could explain it, and what would the requested deliverable accomplish if that explanation were right? Questions like these usually take days rather than months, and they're most useful when someone asks them who isn't already committed to the original request.

Give execution a brief it can actually work from

The value of a better brief shows up later, when the team has to make decisions the original request didn't anticipate. A brief that holds up during execution states the business problem and the outcome the work should produce, the audience and the evidence behind the diagnosis, and what's known versus what's still an assumption to test. It names the constraints, the stakeholders involved, who owns the decision when priorities conflict, and how success will be judged after launch.

That clarity matters most midway through a project. Suppose a senior stakeholder asks the team in the example to add a trade-show version of the campaign and a video about a new product feature. The original brief offers no way to judge them, because it only asked for a campaign. Under the revised brief, the team can ask whether either addition helps better-fit buyers understand which services address their needs. One might, and the other might be worth doing separately, but the decision is anchored to the outcome rather than to whoever asked most recently.

Defining the purpose shapes larger, more technical work too. Our work with PepsiCo's marketing technology team was framed around helping the team prepare for renewals and act with clearer ownership, not simply storing contracts in a better place. That purpose meant connecting applications to vendors, agreements, owners, lifecycle stages, and renewal requirements, and building a readiness framework that sets renewal-planning lead times. A repository designed only to hold documents wouldn't have needed most of that structure.

Not every project needs this scrutiny. When the problem is well understood and the deliverable clearly follows from the evidence, extensive discovery adds cost without adding clarity. The signs that a brief needs more work are usually visible early: a detailed deliverable with no stated outcome, stakeholders who describe the problem differently, little direct evidence about the audience, or success measured only by launch. When those signs appear, the work of our Strategy & Transformation practice is to define the opportunity, align stakeholders on what success means, and produce a strategic brief that design, digital, and media teams can work from.

Strong execution depends on knowing what success requires before choosing the solution. A useful brief helps a team decide what's worth making, and then gives them a way to tell whether they made it.