Iterate rather than rewrite everything
You improve a result through precise feedback instead of starting again from scratch.
ObjectiveBy the end of this lesson, you will be able to correct a result by describing the gap, naming the part concerned, showing what you expect and explaining why.
The first answer is rarely the last. That is normal, and it does not mean your request failed. Specifying continues after the first result: you see what is missing, and you say so.
Correct by describing the gap
Rather than rewriting the whole request, describe the gap between what you have and what you want. The agent keeps the rest. It is faster, and you do not lose what already worked.
No, start again.
Keep the structure and the examples. Cut part 2 by half, replace “staff” with “team” throughout, and add a slide on what to do after clicking a suspicious link.
Precise feedback says what stays, what changes and what is missing, and the agent has nothing to guess.
Three kinds of feedback that work
- Name the part concerned: “In the second paragraph…”
- Show what you want: “More in this style: …”, followed by a short example.
- Explain why: “Too technical, our readers work in accounting.”
The third kind is the most powerful. When the agent knows the reason for a correction, it also applies it to passages you did not point out. A remark about the technical level corrects the whole document, not just the sentence quoted.
In Office suite documents, you can also work directly in the file. The revision history keeps every version, so you can ask for a bold change without risk. If it does not suit you, you go back to the previous version.
Finally, remember what worked. If a correction keeps coming back from one task to the next, it is something that was missing from your initial request. Add it next time, or hand it over to memory.