Prompting is delegation, not magic words

Working with Claude — CC BY 4.0

There’s a myth that getting good work out of Claude is about finding the right incantation — the secret phrase, the clever trick, the “act as a world-class expert” opener that unlocks a better answer. It isn’t. A prompt is a brief. You are handing a task to a capable new hire who is fast, widely read, tireless, and has never met you, doesn’t know your business, and can’t see your screen. The quality of what comes back is mostly decided by the quality of what you sent in.

That’s the reframe worth keeping: prompting is delegation. Nobody expects a new staff member to read their mind. You’d give them the background, tell them what “done” looks like, show them an example, and name the limits. Do the same here and the results stop being a lottery.

What a good brief carries

Five things. You won’t need all five every time, but when an answer comes back wrong or generic, it’s almost always because one of these was missing.

• Context — who this is for, what the situation is, what’s already been tried. Claude has no memory of your world unless you supply it.
• Goal — what you actually want out the other end, and why. “Help with this email” is a wish. “Get this customer to accept a later delivery date without losing their goodwill” is a goal.
• Format — length, structure, tone, medium. Three short paragraphs? A bullet list? A table? Say so, or you’ll get whatever shape Claude guesses.
• Examples — one sample of the thing done well is worth a paragraph of description. Paste a past email you were happy with, or attach a file, and say “match this.”
• Constraints — what to avoid, what’s fixed, what’s off-limits. “Don’t promise a refund,” “keep it under 150 words,” “we’re a small family firm, not a corporate.”

A memory hook: context, goal, format, examples, constraints. Not a spell — a checklist.

Weak vs strong: a real task

Say you run a small landscaping business and a customer has emailed, annoyed that their job has slipped a week because of rain.

The weak prompt:

Write a reply to an unhappy customer whose job is delayed.

You’ll get something. It’ll be polite, generic, and probably over-apologetic — full of corporate padding that doesn’t sound like you and may promise things you never agreed to. It reads like it was written for anyone, because it was.

The strong prompt:

I run a two-person landscaping business in Christchurch. A customer, Sarah, booked us to lay a patio. We’ve had to push her start date back a week because of heavy rain — laying on wet ground would ruin the job. She’s emailed, frustrated, asking why we’ve “let her down.” I want to reply.

Goal: keep her as a customer and get her to accept the new date, without grovelling or offering money off.

Format: a short, warm email — three short paragraphs, plain and human, the way one tradesperson talks to a neighbour. No corporate tone.

Constraints: acknowledge her frustration without over-apologising; explain the weather reason plainly; don’t offer a discount or a refund; end by proposing the new start date and asking her to confirm.

Here’s a past reply I was happy with, for the voice — match this: [paste your own example].

Same tool, completely different result. The second reply sounds like you, holds your line on the discount, and does the one job you actually needed — getting the new date confirmed. Nothing magic happened. You briefed properly.

Why “magic words” is the wrong model

Dressing a prompt up — “you are a genius copywriter,” “think step by step,” politeness, ALL CAPS urgency — occasionally nudges the tone, but that’s not where the gains are, and treating it as the secret sets you up to be disappointed. Structure beats flourish every time. If you find yourself hunting for a clever phrase, stop and check the five instead: which one did I leave out?

There’s a practical bonus to briefing this way. A vague prompt fails quietly — you get a plausible answer and can’t tell what it assumed. A specific brief fails loudly: if Claude misreads something, you can usually see it, because you can hold the reply up against what you asked for. That’s the whole game — keeping yourself in a position to check.

You’re the one signing it off

Delegation doesn’t end when the work comes back. When you hand a task to a new hire, you read what they produce before it goes out the door — you own it, your name is on it. Same here. A good brief gets you a strong first draft, not a finished product you send unread. Claude can get details wrong, invent specifics, or misjudge your customer; the next lesson on accuracy goes into exactly how. The point of a clear brief isn’t to hand over control. It’s to get work back you can actually judge — and then to judge it.

Brief it like a capable colleague. Then review it like one, too.