Home/Knowledge Base/Knowledge Worker Playbooks/K-06

K-06K-Series · Foundation

Writing Better AI Briefs

The single biggest difference between people who find AI useful and people who find it disappointing is the brief. Vague request in, vague draft out — exactly like delegating to a person. The good news: if you’ve ever briefed a new starter well, you already have this skill. This card gives it a repeatable shape.

Why this matters

AI has no context you don’t give it. It doesn’t know your audience, your organisation’s tone, what’s already been decided, or what the document is actually for. When people type ‘write a report about the project’ and get generic mush back, the tool didn’t fail — the brief did. Five minutes of framing routinely saves an hour of fixing, and framing is the first human bookend: nobody can do it for you.

The five-part brief

  • GOAL — what you need, in one sentence. ‘A one-page update on the intranet project for the steering committee.’
  • CONTEXT — what it can’t know. ‘Phase one delivered late; the committee is nervous; the go-live date hasn’t changed.’
  • AUDIENCE — who reads it and how formal they expect it. ‘Senior managers, plain English, no jargon.’
  • CONSTRAINTS — tone, length, what to avoid. ‘Under 400 words. Don’t speculate about phase three. Never promise dates we haven’t confirmed.’
  • OUTPUT — the format you want back. ‘Three headed sections: progress, risks, next steps.’

Goal, context, audience, constraints, output. Say them in that order and the draft that comes back starts near the target instead of near the average of the internet.

A worked contrast

Weak brief: ‘Summarise this meeting.’ You’ll get a bland paragraph that flattens the one decision that mattered.

Strong brief: ‘Summarise this transcript for team members who weren’t there. Lead with decisions made, then actions as a list with owner and due date, then open questions. Keep it under 300 words and don’t paraphrase the budget figures — quote them exactly.’ Same tool, same transcript, unrecognisably better result — because the thinking arrived with the request.

When the draft comes back wrong

Diagnose before you re-roll. Wrong content usually means missing context; wrong tone means the audience wasn’t specified; wrong shape means no output format. Fix the brief, not just the draft — that’s how the skill compounds instead of resetting every task.

Putting it into practice

  1. Save the five headings as a snippet: GOAL / CONTEXT / AUDIENCE / CONSTRAINTS / OUTPUT
  2. Use it on one real task today — two minutes of filling in, honestly
  3. When output disappoints, identify which of the five was thin
  4. Keep your best briefs; recurring tasks deserve reusable briefs
  5. Notice the transfer: this structure improves your human delegation too

Key takeaways

  • The brief, not the tool, decides the quality of the draft
  • Five parts: goal, context, audience, constraints, output
  • Context is the part people skip and the part that matters most
  • Diagnose weak drafts by finding the thin part of the brief
  • Briefing is the first human bookend — it can’t be delegated
What Next?

You've read the article. Now what?

Pick the one that fits right now — a 5-minute fix, the full answer library, or the complete system.

Free · Takes 2 Minutes

Start Here — Free

12 tips that change how you think about SharePoint for good. No fluff, no theory — just what actually works.

Get My Free Guide →
Free · 207 Answers

Got a Different Question?

Search 207 step-by-step cards for whatever's actually stuck right now. Plain English, no jargon.

Find My Answer →
Buy Once · From $19

Ready to Fix It Properly?

Skip the trial and error. Get the complete toolkit and stop patching the same problem every month.

Shop the Hub →

Not ready for any of that? Get one useful email a week instead. Join the free newsletter →