Write a brief that leaves room for a better answer

A good brief is firm about the business problem and constraints while making assumptions visible enough for a specialist to challenge before production begins.

“We need a six-part video series” is a production request. It may be exactly what the business needs, but the sentence does not explain why.

If the real problem is that buyers misunderstand implementation, a video series is one possible response. A clearer proposal, a demonstration or a change to onboarding might solve the problem more directly.

A strong brief lets the specialist examine that choice before the organisation commits to the format. It defines the problem tightly enough to guide work without pretending the first proposed solution is already proven.

Put the business situation first

Describe what is happening, who is affected and why it matters now. Use evidence from customers, operations or commercial performance rather than a collection of broad market adjectives.

For example: suitable prospects request demonstrations, but many withdraw when they cannot understand the migration effort. Sales has documented recurring questions and inconsistent answers.

That is a more useful starting point than “We need more engaging content”. It gives a specialist something to investigate and a business owner something to evaluate.

Keep the problem distinct from the target. Increasing qualified progression may be an objective; uncertainty about migration may be a hypothesised barrier. Both should be visible in the brief.

Identify what is known and assumed

List the evidence supporting the diagnosis and the questions still open. If the conclusion comes from three sales conversations, say so. Do not turn a small qualitative signal into a market-wide fact.

The Design Council’s framework distinguishes problem discovery and definition from solution development. A brief can reflect that by specifying which assumptions the specialist should test before recommending an execution.

Make disagreement useful. Ask for the strongest alternative explanation and the evidence needed to distinguish it. This is more productive than requesting “challenge” while penalising any proposal that departs from the format already imagined.

The company still owns the final decision. Inviting challenge does not mean giving the supplier an unlimited discovery project.

Define the audience and the next behaviour

Describe the person in a relevant situation, including their knowledge, concern and role in the decision. Avoid an audience so broad that every message seems appropriate.

State what the work should help them understand or do next. A technical buyer may need confidence in compatibility; a budget owner may need to understand implementation cost and responsibility.

Do not ask one asset to resolve every objection for every stakeholder. If several jobs are genuinely required, identify them and allow the specialist to recommend an appropriate structure.

Include poor-fit audiences where necessary. This helps prevent an attractive execution from generating demand the business cannot serve.

Separate constraints from preferences

Constraints include legal requirements, confirmed launch dates, available evidence, accessibility needs, budget limits and product capabilities. Preferences include a favoured format, colour treatment or example campaign.

Label them honestly. A preference disguised as a non-negotiable can block a better solution without anyone discussing the trade-off.

Provide the budget range and the internal capacity available for interviews, reviews and production. A brief that conceals resources invites proposals that are difficult to compare and impossible to deliver.

The Sourcing Playbook highlights the importance of realistic delivery and risk allocation. Applied to a marketing brief, that means not assigning a supplier responsibility for outcomes controlled by unavailable company inputs.

Show the proof and the boundaries

Supply approved facts, customer permissions, product limitations and relevant previous work. Explain which claims are supported and which still need investigation.

A specialist should not have to infer the company’s evidence standard from contradictory feedback late in production. Likewise, a creative idea should not create a promise the product team has never agreed to deliver.

Identify the person who can answer each important question. One project owner can coordinate, but technical and commercial facts may require different experts.

Keep decisions in a shared record so later reviewers do not unknowingly reopen resolved questions.

Agree how the work will be judged

Define acceptance criteria for the deliverable and a separate plan for evaluating its effect. An accurate, usable asset can be completed before its commercial impact is observable.

Specify review stages that correspond to real decisions: confirm the diagnosis, approve the concept, verify claims and approve final execution. Avoid collecting subjective preferences from a large group only after production is nearly finished.

Choose one accountable approver for each stage and set response times. Slow internal feedback is a project risk that belongs in the plan rather than being blamed on the supplier afterwards.

Leave a clear invitation to improve the answer

End the brief by asking the specialist to recommend the most effective feasible response, identify assumptions they dispute and explain the trade-offs among options.

The best reply may confirm the original video series. If it does, the company now has a reason for choosing it. If it proposes something better, the brief has done its job before expensive production began.

A useful brief is an agreement about the problem, the constraints and the decision process. It gives expertise a purpose instead of reducing it to the execution of an unexamined request.