Short answer
It is not about magic phrases. It is about writing down what you already know but have not said.
Five parts are enough for almost everything work-related: recipient, task, source material, format, limits.
The most common gap is describing the task but leaving out the recipient and the format — and those two are exactly what decide whether the answer can be used without being rewritten.
Why short instructions give poor answers
“Write a reply to this customer.”
That is a perfectly understandable instruction between two people who work together, because all the rest is implied: who the customer is, what you usually reply, how formal you are, that it should be short, and that you never promise delivery dates in writing.
None of that exists for a system that does not know you. It has to guess, and a guess that has to suit every conceivable context inevitably becomes the most general answer — polite, correct, empty and twenty per cent too long.
So it is not that the tool is bad at your sort of task. It lacks what you did not write. And that realisation is, in practice, the whole subject.
The five parts
1. Who is the answer for? “For a customer who is annoyed about a delay.” “For our board, which is not familiar with the technology.” “For a fifteen-year-old.” This is the part most often left out, and it makes the biggest difference, because the recipient governs tone, length and what needs explaining.
2. What is the task? A verb and a result. “Summarise.” “Write a draft of.” “Find the counterarguments to.” “Compare these two.” Vague tasks give vague answers.
3. Which source material applies? Paste it in. The single largest difference in quality between a good and a poor instruction is usually that the good one contains the actual material — the email, the quote, the figures, the earlier text — instead of a description of it.
4. What should the answer look like? “Five bullet points.” “Maximum one hundred words.” “An email with a subject line.” “A table with three columns.” Without format requirements you get the system's default format, which is almost never yours.
5. What should be left out? “Don't promise a date.” “Don't use the word exciting.” “No apologies.” “Don't make up figures — say if you lack source material.” The last one is worth making a habit in all work that involves facts.
An example, before and after
Before: “Write a reply to the customer who is complaining about the delivery.”
That gives a polite, generic reply with at least one phrase you would never have written yourself, and you have to rewrite it. Net time saved: roughly nothing.
After: “Write a draft reply to the email below. The recipient is a returning customer who has waited two weeks longer than expected and is entitled to be annoyed. We are a small company and write directly and personally, not formally. Maximum one hundred words. Apologise clearly once, explain briefly what happened, and say what we are doing now. Don't promise a new date — I will fill that in myself. [the email is pasted here]”
It takes forty seconds extra to write and gives something that can usually be sent after a read-through.
And note what those forty seconds actually consisted of: nothing you had to learn. Only things you already knew about your customer, your tone and your policy — things you have never needed to say out loud before.
Three mistakes
Describing the source material instead of attaching it. “Based on our price list” says nothing. Paste the price list.
Giving up after the first answer. The first answer is a draft, not an answer key. “Shorter, and remove the last paragraph” takes three seconds and does more than rewriting the whole instruction. Most people who think the tool is bad have tried once and stopped.
Trusting facts that were not in the source material. This is the only mistake that is dangerous rather than merely ineffective. A system that lacks a piece of information often makes up a plausible one, and it looks just like a true one. The rule: if the figure is not in what you pasted in, check it before it leaves the building. It is worth adding that to the instruction as well.
What makes the biggest difference over time
This part is rarely mentioned, and it is the one that gives the most in an organisation.
Once you have written an instruction that gives good results — save it. A document on the company's shared drive with ten good instructions for the ten most common tasks is worth more than a full day's training in prompt technique.
The reason is that the hard part was never the wording. It was thinking through what actually characterises a good answer for you. That work only needs doing once per type of task — and it should not live in one person's head.
It is also the point where it stops being individual employees' tricks and becomes a shared way of working. In my courses this is often the exercise that gives the most: the group together writes the three instructions they will use every week.
The most important thing
If you take just one thing away: write as you would have instructed a competent new colleague who does not know your business.
That person is capable but knows nothing about your customers, your tone or what you never promise in writing. Everything you would have needed to tell her is exactly what is missing from your instruction — no more and no less. There is no secret beyond that.
Best wishes, Mikael GlännströmWellbeing coach, author and father of two