AI Operator

Free lesson

The five-minute brief

The opening lesson of AI for Knowledge Work. Read it, then run it on the next task you were about to do by hand.

Most bad output starts before the model says anything. Someone types “write a summary of this report”, gets three paragraphs of warm mush, and concludes the tool is overrated. The tool was fine. The brief was empty.

A brief is not a longer prompt. It is four pieces of information, and you already have all four in your head.

The four parts

Context. What this is, who reads it, and what happens after they read it. Not “a report” but “a monthly update for a client who is deciding whether to renew”. The model cannot infer the decision from the document.

Constraints. Length, tone, what to leave out, what must be exact. Numbers, names and dates are the usual suspects. Say which ones may be paraphrased and which must be quoted.

Examples. One sample of the output you liked. This single addition does more for quality than any adjective. If you have none, paste a paragraph you would be happy to have written and say “this register”.

Shape. The answer’s structure: five bullets, a 200-word summary, a table with these three columns. Ambiguity here is what produces the essay nobody asked for.

Before and after

The request most people write:

Summarise this report for my client.

The same request as a brief:

Context: monthly update for a client deciding whether to renew in March.
They care about delivery risk and cost, not our roadmap.

Constraints: 200 words max. Use only figures from the attached report.
If a number is missing, write "not reported" instead of estimating.

Example: last month's update opened with the one thing that changed,
then two bullets of evidence. Keep that register.

Shape: one opening sentence, three bullets, one line on what we need
from them before the next update.

Same model, same document, ten times the usable output. The difference is not clever wording. It is that the second version answered the questions the model would otherwise have guessed at.

The three checks

A brief improves the draft. It does not make the draft true.

Can I trace every claim? If a statement has a number or a name, it must point at the source. No source, no claim. This one check removes most of the damage.

Does it survive being read aloud? Read the first paragraph out loud. If you would not say it to the client’s face, it is filler and it goes.

What would make this wrong? Ask for the strongest counter-argument in one sentence. A draft that cannot name its own weak point is usually hiding one.

Your exercise

Pick the next document you were going to write by hand. Write the four parts before you open the chat. Then compare the draft to what you would have produced alone, and note the one place where the model was actually better.

That note is the beginning of your own operator’s loop. The course is eleven more lessons of it.

If the exercise took you five minutes and saved twenty, the full course will pay for itself in the first week. If it felt like extra work, that is a real signal too — the free lesson is the same method the course uses, only slower and with feedback.

Next step

This is week one, lesson one.

The course continues with research that survives a fact-check, documents and decks, meetings, and a personal prompt stack you actually reuse.

See the full course