Blog

Before You Hand AI a Task, Give It a One-Paragraph Brief

Write a short brief (goal, facts, limits, done) before you ask AI to do a task.

By Nathan Brumand ·

Most bad AI output I see starts with a bad ask.

"Write something for our customers." "Clean up this list." "Make this better."

The tool does something. It's fast. It looks finished. And it's not what you wanted.

That's not really the tool's fault. You wouldn't hand a new hire one vague sentence and walk away. You'd tell them what the job is, what they need to know, and what not to touch.

AI needs the same thing. It just needs it in writing.

Four lines are enough

Before I hand a tool a task, I try to answer four questions. One line each.

1. What's the goal?

Not the task. The goal. "Reply to this customer" is a task. "Keep this customer, and get them a clear date" is a goal.

2. What are the facts?

Paste them in. Prices, hours, names, dates, what you already promised. If it's not in the brief, the tool will guess.

3. What are the limits?

What it must not do. Don't offer a discount. Don't promise a time. Don't change the numbers. Keep it under 150 words.

4. What does "done" look like?

A short email? Three bullet points? A table with these columns? Say it, and you'll get it.

That's it. Four lines. Two minutes.

What it looks like

Here's a brief for a simple customer reply:

Goal: keep this customer and give them a clear next step.
Facts: their order is delayed two days. The new date is Thursday. We already apologized once by phone.
Limits: no discount, no new promises, no blame on anyone. Under 120 words.
Done: a short, friendly email that ends with the Thursday date.

Compare that to "write a reply to this angry customer." Same tool. Very different email.

Why this works

A vague ask gives the tool room to fill in blanks. It fills them with something that sounds right.

A brief takes that room away. The tool has a goal to aim at, facts to use, lines it can't cross and a shape to fill.

You also get something else: when the answer is wrong, you can see why. Either the brief was missing something, or the tool ignored it. Both are easy to fix.

Keep your best briefs

After a few weeks you'll notice you write the same briefs again and again. Customer replies. Weekly summaries. Job posts. Meeting notes.

Save those. A short file with your five best briefs is worth more than any list of fancy prompts from the internet. They're written for your business, in your words.

When someone new joins the team and starts using AI, hand them the file. Now everyone asks the same way, and the output is a lot more consistent.

Still read the result

A good brief makes the first draft better. It doesn't make it safe to send without looking.

Read it once before it goes out. Check the facts against what you pasted in. If it went past a limit, fix the brief, not just the draft.

The simple point

AI does what you ask. Most of the time the problem is that we didn't really say what we wanted.

Goal. Facts. Limits. Done. Write those four lines first, then hand over the task.

What's the one task you keep asking AI to do that never quite comes out right?

Keep reading

— Nathan Brumand

← All articles