AI Guides › Prompting

The Brief Beats The Prompt

By Nigel Guy · 2 min read

Most prompting advice is about wording — magic phrases, the right adjectives, a clever framing sentence. Wording matters less than people think. What actually determines whether you get a useful answer is whether you gave it a brief or just a prompt, and most people never notice the difference because a prompt and a brief can look almost identical on the screen.

The rule: a prompt asks for an output; a brief gives enough shape that a follow-up question doesn't start you over — write briefs, not prompts.

The mechanism

A brief, at minimum, answers four things a bare prompt usually skips:

  1. The actual decision or use this is for. Not "write a project description" — "write a project description that a busy stakeholder will read in under a minute and use to decide whether to approve funding."
  2. The constraints that are non-negotiable. Length, tone, what must be included, what must never be included. State these once, up front, rather than correcting them one at a time afterward.
  3. What "done" looks like. A concrete example, even a rough one, does more work than three more sentences of description.
  4. What you already tried or ruled out, if anything. This stops it from confidently suggesting the thing you already know doesn't work.

The test

If a genuine follow-up question ("should this be formal or casual?" "is this for internal or external use?") would force you to restate the whole request from scratch, you wrote a prompt, not a brief. A real brief absorbs the follow-up because the answer was already in there.

What to skip

Skip decorative language ("you are a world-class expert in…") — it does far less than people assume, and the words you'd spend on it are better spent on an actual constraint. And skip writing an exhaustive brief for a trivial, low-stakes request; briefs earn their setup cost on anything you'll reuse or anything that matters.

Guardrails

All 751 AI guides · JulieMango plans from £17/mo