Getting a better second answer · Lesson 4

Start from something nearly right

New chat. Send this. It is a decent request and it will produce a decent, slightly overlong, slightly stiff answer. That is exactly what we want to work on.

The starting request

Write a message to a customer explaining that the part they ordered is delayed by two weeks. They have already waited a month. Around 120 words, apologetic but not grovelling, and offer them the option to cancel.

I have an answer on screen that is close but not quite right

That throws away a decent draft to save a sentence. Ten minutes here on fixing what you already have.

Lesson 04 · Getting started

By the end you can

Improve a mediocre answer without rewriting your original request
Use the three follow-ups that work: cut, change, correct
Recognize the vague follow-up that wastes a turn

What you need

Any of the four. Free tier is fine.

Fundamentals of AI

The three moves that work

Send these one at a time, in the same chat, reading each answer before the next. Each one changes a different thing.

Cut. Remove something specific.

Cut it to 70 words. Lose the opening pleasantry entirely and start with the delay.

Change. Aim it somewhere else.

Now rewrite that for a customer who has already complained twice and is clearly out of patience.

Correct. Fix a specific thing that is wrong.

The cancellation offer sounds like we want them to cancel. Keep the offer but make it clearly a courtesy, not a suggestion.

Cutting made it shorter without losing the point
Changing the reader changed the tone, not just the words
Correcting fixed the exact thing I named

All three name something specific. That is the pattern. You are not asking it to have better taste, you are telling it which part is wrong and what should be true instead.

The follow-up that wastes a turn

Now do the thing almost everyone does. Send this and watch carefully.

Send this, then read the result skeptically

Make it better.

Was it actually better?

Check your own work0/3

It changed the wording
I cannot say what problem it solved
I checked whether it put back something I had already taken out, or changed something I had already fixed

It has no idea what better means to you, so it changes things at random and often undoes your earlier corrections. If you catch yourself typing make it better, stop and name the actual problem instead. That one habit is worth more than any prompt template.

Know when to stop

Iterating has a limit. Past roughly four or five rounds on the same piece, answers tend to circle rather than improve, because every previous attempt is still sitting in the thread pulling it back.

When would you stop and start again?

Check your own work0/2

My answer mentions going round in circles or the same problem returning
I would carry the good parts into the new request rather than starting blank

Where that leaves you

Everything you have done so far lives inside one conversation. Close it, come back tomorrow, and none of it is there. What these tools hold on to, what they quietly forget, and what they never knew in the first place is lesson 5.

Next: What the tool remembers and forgets