Send the weak version
2mStart a new chat. Send this exactly as written, then leave the answer on screen. You are going to compare against it shortly.
Write something about our new opening hours.
What comes back will be competent and useless. It does not know who is reading, why they should care, how long it should be, or whether it is a poster or an email. So it guesses at all four, and guesses blandly.
Ten minutes here, and the same request will come back noticeably better.
Lesson 03 · Getting started
By the end you can
- Name the four things worth adding to any request
- Turn a vague request into a specific one
- Judge two answers to the same task side by side
What you need
Any of the four. If you want to see the difference most starkly, use the same tool as lesson 2.
The four things it is missing
3mAlmost every weak request is missing the same four things. You do not need a framework or a template, just these.
Send the strong version
3mSame task, same tool, new chat. This time all four are present.
Write a short email to regular customers of a small bookshop, telling them we now close at 6pm on Saturdays instead of 8pm. They will be mildly annoyed, so acknowledge that. I want them to know the weekday hours have not changed. Under 100 words, warm but not apologetic.
Check your own work0/4
Do it with something of your own choosing
2mPick any small writing task you can describe without using real names, figures or anything confidential. A reminder to a club, a notice for a bulletin board, a message to a neighbor. Write the request with all four things in it.
Check your own work0/4
Where that leaves you
A good request gets you a much better first answer. It does not get you a perfect one, and the reflex most people have at that point is to rewrite the request and start again. That is usually the slower path. Lesson 4 is about fixing the answer you already have.