Most disappointing model output is a communication failure, not a capability failure. Communicating with purpose means the request carries everything a competent stranger would need: the task, the material, the constraints and the shape of the answer — written once, properly, instead of five times in frustration.
What changes when you communicate well
- Fewer rounds. A brief that names the audience, length and format usually lands in one attempt; a vague one takes four.
- Answers you can use as-is. Specify the artefact — email, table, patch, slide — and the output drops straight into the work rather than needing a rewrite.
- Less invented detail. Every unstated fact is a gap the model fills by guessing. Stating them is the cheapest hallucination control there is.
Patterns worth reusing
- The brief. Audience, goal, constraints, source material, format — five labelled lines, in that order, with the task last.
- The exemplar. Paste one output you liked and ask for the same shape with new content.
- The contract. For machine-read output, give the exact schema and add “emit only valid JSON, no commentary”.
- The escape hatch. Say what to do when the material does not answer the question, so the model reports a gap instead of filling it.
Example
Vague
Write something about our new pricing.
Better
AUDIENCE: existing customers on the Team plan. GOAL: explain the new pricing without triggering churn. CONSTRAINTS: under 150 words, no jargon, one clear call to action. SOURCE: Team goes from $20 to $24/seat on 1 March; annual billing unchanged; two new features included. FORMAT: email with subject line and body.