The One-Page Brief: How to Ask an AI Assistant the Way You Would Brief a New Hire

⏱ 7 min read|Published 8 November 2026|By Dibyendu Choudhury

When a new person joins your business, you do not say, "Write something about our product," and walk away. You tell them who the customer is, what the goal is, what has been tried, what good looks like, what must not be said, and when you need it. You do this because you have learned, probably the hard way, that a vague request produces vague work, and that the cost of the vague work lands on you.

Yet that is exactly how many of us speak to an AI assistant. We type one line, receive a generic answer, decide the tool is overrated, and go back to doing the task by hand. The tool did what it could with what it was given. The remedy is not a cleverer trick or a secret phrase. It is an old management habit: write a short brief. One page is enough, and in most cases half a page does the job.

Why a brief beats a clever prompt

Search for advice on talking to AI and you will find endless lists of magic words. Most of them are a poor substitute for the thing that actually matters, which is context. An assistant cannot see your shop, your customers, your previous mistakes or the standard you hold yourself to. It begins every conversation knowing nothing about you except what you type. The brief is how you hand over the knowledge that a human colleague would have picked up over months.

There is a second benefit that is easy to miss. Writing the brief forces you to decide what you actually want. Half of the frustration with AI output is really frustration with our own unclear thinking, which the tool has politely reflected back to us. If you cannot write down the audience and the purpose in two sentences, no assistant, human or machine, can reliably produce the right thing.

The six parts of a working brief

Here is the structure I use, and teach to small business owners. It fits on one page and takes about five minutes to write once you have done it a few times.

First, the purpose. Say what the work is for and what should happen because of it. "A reply to a customer who received the wrong size and is angry" is a purpose. "Write an email" is not. The difference is that the first tells the assistant what tone, what urgency and what outcome to aim for.

Second, the audience. Describe who will read or use the result: their role, their knowledge, their mood, and what they care about. A message to a long-standing wholesale buyer reads very differently from a message to a first-time retail customer, and an assistant that knows the difference will save you the editing.

Third, the material. Paste in the facts the work depends on: the order details, the policy, the price list, the notes from yesterday's call. Do not expect the assistant to know them, and do not expect it to guess them correctly. If a fact matters, supply it. If you do not want a fact used, say so.

Fourth, the shape of the answer. Tell it how long the result should be, in what format, and in what voice. "Under 150 words, plain language, polite but firm, signed with my first name" removes a dozen small decisions and a dozen small corrections.

Fifth, the limits. State what must not happen. Do not promise a refund amount. Do not mention a competitor. Do not invent a deadline. Do not include anything that is not in the material I gave you. Limits are the part most people leave out, and they are the part that protects you from the confident invention that these tools are known for.

Sixth, the test. Say how you will judge the result, and ask the assistant to check its own work against it. "Before you answer, confirm that every figure appears in the material I pasted, and list anything you were unsure of." This one sentence moves the assistant from performing to checking, and it produces a short list of doubts that tells you exactly where to look.

A worked example

Suppose you run a small garment business and a customer has written to complain that the kurta she ordered arrived two sizes too small. A one-line request such as "reply to this complaint" will give you a sympathetic, generic note that might offer a refund you cannot afford or a replacement you cannot ship.

Now consider the brief version. The purpose is to resolve the complaint and keep the customer. The audience is a first-time buyer who is upset but not abusive. The material is her message, the order number, your exchange policy copied in full, and the fact that the correct size is in stock and ships in two days. The shape is under 130 words, warm, in plain English, no jargon. The limits are that no cash refund is offered unless the policy says so, no blame is placed on the customer, and no new promises are made beyond the exchange. The test is that the reply must mention the order number, the exchange route and the shipping time, and must contain nothing that is not in the material.

The result of that brief is a message you can usually send after a quick read. The few minutes spent writing the brief are repaid by the minutes saved in editing, and, more importantly, by the mistakes that never happened.

Keep your briefs, and improve them

Once a brief works, save it. A small business tends to do the same dozen things repeatedly: reply to a late-payment query, summarise a supplier quote, draft a job advertisement, write a product description, prepare a monthly note to staff. Each of these deserves a standing brief that you keep in a folder and adjust. Over a few months you will build a small library of instructions that encode how your business speaks and decides. That library is an asset. It is also a training document for the next human you hire.

When a result disappoints you, resist the urge to blame the tool first. Ask what the brief left out. Was the audience unclear? Was a fact missing? Did you forget a limit? Add the missing line to the standing brief, and the same mistake does not return. This is how the quality of your results improves steadily, rather than by luck.

What a brief cannot do

A good brief improves the first draft. It does not remove your responsibility for the final one. Read what comes back as you would read the work of a capable but new colleague whom you do not yet fully trust. Check the numbers against the source, check the tone against your own ear, and be especially careful with anything that makes a promise, quotes a price, refers to a law or speaks for your business in public. The brief reduces the chance of error; it does not make the assistant accountable. You remain the accountable one, and the business will be judged by what you send, not by who drafted it.

Be careful, too, about what you paste in. A brief that includes a customer's full details or your own confidential figures should be written with thought about where that information is going. Strip out what the task does not need. A good rule is to give the assistant everything required to do the job and nothing more.

A five-minute practice for this week

Pick one task that you repeat at least weekly. Write its brief using the six parts: purpose, audience, material, shape, limits and test. Run it once, read the result carefully, and note what you had to fix. Add one line to the brief that would have prevented that fix. Save it with a clear name. Next week, use it again and notice how much less editing it needs. By the third week, you will have a dependable tool and, just as valuable, a clearer sense of what you want from your own work.

One question to take away

Which task in your business do you explain to people again and again, and what would the one-page brief for it say? Share one line in the comments if you wish; I read every one.

If you enjoy a long read after a long working week, my Spirituality Series book Krishna-Draupadi Samvad is out now on Amazon Kindle, and you can find it on the Spirituality Series page.

---

Published 8 November 2026 · dibyenduchoudhury.com