Write a clearer AI brief

Name the result you need and who will use it

Start with the work the output needs to do. A customer email should explain a change and make the next step clear. A research comparison should help someone decide between options. A project plan should make responsibilities and dependencies visible.

Include the audience and what they already know. A technical explanation for a colleague needs different detail from a first introduction for a customer. Say whether you need a rough draft, a comparison to discuss, or material ready for a final review.

• Name the task and its purpose.
• Describe the reader or person making the decision.
• State the format and level of finish you need.

Supply the context that changes the answer

Attach the relevant notes or files, or select the Library material that belongs to the task. Explain which source is authoritative when documents disagree. Include facts that must remain exact, such as a date, product name, requirement, or approved statement.

Keep facts separate from preferences. The source may establish what a feature does; the brief can ask for a warm tone and a short introduction. If a necessary fact is missing, ask for it to be identified for review rather than filled in with a plausible claim.

• Identify the source of factual claims.
• Include the constraints that affect the result.
• Name anything that needs a separate decision or confirmation.

Change the brief when the kind of work changes

A useful brief describes the decisions involved in the particular task. “Make it better” leaves those decisions unstated. Point to what needs to improve and explain how you will judge the result.

In AI Chat, the models and tools available to your workspace affect what you can produce. For an image, video, or spoken output, check that the selected model supports the format you need. A written media brief is still useful before any generation begins.

• Writing: specify the reader, message, tone, length, and next action.
• Research: state the question, comparison criteria, acceptable sources, and how recent the information needs to be.
• Planning: include the desired outcome, known constraints, available people or resources, and decisions still open.
• Media: describe the subject, setting, composition, mood, dimensions or duration, and intended placement. Include approved references where you have the right to use them.

Example: a customer email with a clear review boundary

A brief for a release announcement could read: “Draft a customer email from the attached release notes. The readers are account administrators who already use the product. Explain the main change and the action they need to take. Use plain language, one subject line, and an email of about 150 words.”

Add the constraints: “Use only facts supported by the release notes. Preserve the feature names and dates. If timing, eligibility, or a required action is unclear, list the question below the draft. Prepare the email for review; do not send it.”

This gives the draft a purpose and gives the reviewer specific things to check. The same pattern works for a research summary: replace the email format with a comparison, name the decision criteria, and ask for unresolved questions beside the findings.

Review the result against the brief

Check the facts against the source material, then read the output as its intended audience. Does it answer the question? Is the next step clear? Has it introduced a claim, assumption, or promise that the sources do not support?

Give the next instruction a specific purpose. Ask to shorten a repeated explanation, clarify an unfamiliar term, compare another option, or revise a visual composition. Keep the parts that already work. Publishing, sending, or running a connected action is a separate step with its own review.