The saving is not the drafting time
A drafted reply appears in four seconds. It used to take you four minutes. The obvious conclusion is that you saved four minutes.
You did not. You saved four minutes minus the time you now spend reading, correcting and deciding whether to trust it. That second number is the checking tax, and almost nobody measures it, which is why so many businesses feel busier after adopting a tool that is working.
Measure it once, properly. Take ten real items. Time yourself doing three the old way. Then draft the other seven with help and time the whole loop: writing the request, waiting, reading, editing, deciding. Divide.
Owners are routinely surprised. A typical honest result on customer replies: four minutes down to a minute and a half, so a real saving of about 60%. A typical honest result on a technical quote: eleven minutes down to nine, because the checking is nearly as hard as the writing. The first task is worth automating. The second is not, and no amount of better prompting changes that, because the cost is in the verification rather than the generation.
Loud errors and silent errors
Not all checking is the same, and this is the distinction that decides whether a task is safe.
A loud error announces itself. Clumsy phrasing, a paragraph in the wrong order, a greeting that does not sound like you. You catch it by reading normally, in seconds, and the worst case if you miss one is mild embarrassment.
A silent error looks exactly like a correct answer. A delivery date that is wrong by a week. A tax rate that was right last year. A dimension transposed from 460mm to 640mm. A clause dropped from a contract summary. You cannot catch these by reading; you catch them only by checking each item against a source, deliberately, one at a time.
So the honest question about any task is not “can it do this?” but ”how expensive is my checking, and what does a missed error cost?” A task with cheap loud errors is a gift. A task with expensive silent errors is a trap that pays you for weeks and then charges you all at once.
Read in passes, not in one go
Most people read a draft once, for general quality, and their eye slides over the numbers because the sentences around them are smooth. Two separate passes catch far more in less total time.
- The numbers-and-promises pass. Ignore the prose entirely. Look only at figures, dates, percentages, quantities, guarantees, and anything phrased as a commitment. Every one must trace back to something you supplied. Anything that appeared from nowhere gets deleted rather than corrected. On a short reply this takes about twenty seconds.
- The reading pass. Now read it as a customer would, for tone and sense.
The order matters. If you read for tone first you have already accepted the text as a whole, and the numbers become part of the furniture.
Checking fatigue is real, and it is predictable
Here is the failure that catches conscientious people, and it is worth naming because it feels like nothing is happening.
The first twenty drafts are good. You correct two small things. The next twenty are good. By the fiftieth you are skimming, because fifty consecutive fine outputs have taught you that the output is fine. The error rate has not changed at all; your attention has. Then one bad one goes out.
Three defences, all cheap:
- Keep batches small. Twenty items, then stop. Attention on a checking task falls off sharply after about twenty minutes.
- Make the check mechanical. A three-item checklist you tick beats “read it carefully”, because a checklist survives boredom and vigilance does not.
- Spot-audit on a schedule. Once a week, pull five items that already went out and check them properly against source. This measures your actual error rate rather than your confidence, and it is the only way you will ever notice drift.
The rule of thumb
If checking a piece of output takes more than about half the time the task originally took, the task is probably the wrong one. Move it back to the list and pick another.
That is not a counsel of despair. It is the reason the two tasks you chose need to be the ones where you can glance at the result and know. Frequency multiplied by a real saving is where the money is, and a real saving is the one that survives the checking.
Every lesson here is open. Your progress is recorded once you pass the AI at Work exam.
Check your understanding
A workshop uses AI to draft cutting lists from customer measurements. The prose is always clean, the checking feels quick, and it has run well for six weeks. What is the strongest reason to distrust the current arrangement?
Pick the one you would defend. Your answer stays private.
Stuck on something?Ask Yetunde, your AI tutor