How to write a prompt that actually works

Most people's first experience of an AI tool is mild disappointment. They ask something reasonable, get something bland, and conclude the tool is overrated.

The tool is usually fine. The request was underspecified — and a vague request gets an average answer, because average is the safest prediction.

Here is what to do instead. There is no jargon in this, and you do not need to learn a system.

Why your first prompt disappoints

Ask for "an email to my landlord about the boiler" and you will get an email that could have been written by anyone, to any landlord, about any boiler.

That is not a failure. It is exactly what you asked for. You gave no specifics, so it filled the gaps with the most generic version of each one.

The tool is not guessing what you meant. It is completing what you wrote.

Every detail you leave out is a detail it invents. So the fix is not a cleverer phrasing — it is more of the information that was only ever in your head.

The four things a good prompt has

Not a formula to memorise. Just the four gaps that cause most bad answers.

1. Who it should be

"You are a plain-speaking assistant helping a tenant" produces something different from no instruction at all. One sentence is enough. This mostly sets the register — formal or casual, cautious or direct.

2. What it needs to know

This is the big one, and the one people skip.

The boiler has been broken for eleven days. You have emailed twice. You have a baby in the house. Your landlord is normally responsive. You do not want to threaten anything yet.

None of that was in "an email about the boiler", and all of it changes the email.

3. What you actually want

Not "help with an email" but "a short email, under 150 words, firm but not aggressive, asking for a date this week."

Be specific about length, tone and what a good result looks like. If you would recognise a bad answer instantly, say the thing that would make it bad.

4. What shape the answer should take

A bulleted list. A table. Three options. Just the email, with no preamble.

If you do not say, you will often get a paragraph of explanation you did not want wrapped around the thing you did.

The same request, twice

Weak:

Write an email to my landlord about the boiler.

Better:

You are helping a tenant write to a normally reasonable landlord. Our boiler has been broken for 11 days. I have emailed twice with no reply. There is a baby in the flat. I want a firm but polite email, under 150 words, asking for a repair date this week. I am not ready to mention legal action. Give me the email only, no preamble.

The second is not more clever. It is just the information that was always in your head, written down. That is essentially all prompt writing is.

The step almost everyone skips

Your first answer is a draft, not a result.

The single highest-value habit is to reply with what was wrong:

  • "Too formal. Make it sound like a person."
  • "Too long. Half the length."
  • "You invented a tenancy clause. Remove anything I did not tell you."
  • "Keep the second paragraph, rewrite the rest."

People start a fresh conversation instead, and lose all the context they had built. Correcting is faster and gets better results, because the tool now has your first attempt *and* your objection to it.

Two rounds of correction will beat any single perfectly-crafted prompt.

A few things that reliably help

  • Give it an example. If you have an email you liked, paste it in and say "in this style". Examples work better than adjectives.
  • Ask it to ask you. "Before you write it, ask me anything you need to know." This surfaces the details you forgot, and it is remarkably effective.
  • Say what to leave out. "Do not add anything I have not told you" measurably reduces invented detail.
  • Ask for options, not an answer. Three variations, then pick. Reacting is easier than specifying.
  • Split big requests. Plan first, then write from the plan. One prompt doing both does neither well.

Two things that do not help

Politeness. Please and thank you are fine, but they are not doing anything to the output. Say them if you like saying them.

Magic phrases. "Take a deep breath", "you are a world-class expert", "think step by step" — these get passed around as tricks. Specific context beats all of them, every time. If a phrase seems to help, it is usually because writing it made you write more detail as well.

Start here

Take something you are going to do this week anyway. Write the prompt with those four things in it — who, what it needs to know, what you want, what shape. Then correct the answer twice.

That is the whole skill. Everything else is practice.

If it helps to see the four parts laid out as boxes, we built a prompt builder that assembles them for you and gives you something to copy. It runs entirely in your browser — nothing is sent anywhere, and there is no sign-up.

If you are still working out which tasks are worth pointing an AI at, what AI can actually do for you covers where it is strong and where it is not, using AI at work without overhauling everything narrows that to the working day, and why AI gets things wrong explains the one failure mode worth watching for.