Write a Brief People Can Use

Start by naming the audience's situation rather than the object you have been asked to make. A launch film, landing page and poster are outputs; they do not explain why the work exists. Ask who will encounter the material, what they already know and what they need to understand next. Describe one specific use context, such as someone comparing two products on a phone. This gives later choices about length, hierarchy and emphasis a purpose that the team can discuss.

Write the desired change in language you can observe without promising a business result. For example, the viewer should be able to identify the product and explain its main use is more actionable than create excitement. Compare that purpose with the requested output and ask whether the format can reasonably support it. Keep unanswered questions beside the brief, with a person responsible for confirming each one. Do not polish uncertainty into a confident sentence merely because an incomplete document feels uncomfortable.

Practice: Rewrite a vague request as an audience, a situation and a desired change in three sentences.

Make a separate row for every output that requires a different production or approval decision. Two sizes of the same composition may be adaptations, while two messages aimed at different audiences may need separate creative work. Record the destination, format, language, intended use and required variants. Include the source of a requirement when possible, such as a supplied placement specification. If a technical detail is not yet known, mark it as pending instead of borrowing an unrelated specification from an earlier project.

Add an acceptance criterion that describes what the reviewer can check. A subtitle file might need to match the approved edit, use agreed speaker names and contain no missing spoken passages. An image set might need to show the front, side and fastening of the product. These criteria do not replace creative judgment; they make practical completeness visible. Review the table with the person commissioning the work, and distinguish required outputs from optional ideas before using it to estimate effort or schedule production.

Practice: Build a deliverable table for three outputs, including dimensions or duration, destination and acceptance criteria.

List everyone involved in the project and describe the decision they actually own. A subject specialist may check factual accuracy, a brand contact may review identity and another person may approve the final delivery. Those responsibilities can coexist, but they should not remain implicit. Identify who consolidates comments and who resolves conflicting requests. If several people must approve an output, write the order or condition for that approval so the creator knows when a review round has genuinely closed.

Work backward from the next meaningful milestone to identify when each decision is needed. A location choice may affect filming long before someone reviews the final edit. Put these earlier dependencies on the decision list, not only on a delivery calendar. For each open item, record the question, owner, needed date and consequence of delay. Keep the consequence factual: an unresolved language choice may postpone voice recording, for example. This makes the plan useful without turning every uncertainty into an alarm.

Practice: Draw a simple approval path and name one owner for each unresolved decision.

Give the brief to someone who did not help write it and ask them to explain the assignment in their own words. Avoid coaching them through the document while they read. Listen for differences in audience, purpose, deliverables and responsibility, because those differences reveal where the wording depends on shared background knowledge. Ask what they would do first and which question would stop them from beginning. Their interpretation is evidence about the document's clarity, not a test of how attentive they are.

Revise the brief by fixing the cause of each misunderstanding. Replace a vague term with an example, add missing context or move a requirement next to the output it affects. Do not respond by adding every project detail to the opening page. Keep a concise working brief and link or attach supporting information where needed. Finish by reading the deliverable list against the purpose statement. Every required output should have a clear role, and every essential part of the purpose should be supported somewhere in the plan.

Practice: Ask a collaborator to describe the assignment using only the brief, then revise the three points they interpreted differently.