Module 1 · Why now, honestly
When AI goes wrong in hurried hands
In short
AI most often goes wrong by inventing, agreeing, skipping and going too far. Ask for evidence, not reports, and set the steps that always wait for your approval.
After this lesson you can
- Recognise the four ways AI most often goes wrong in everyday work
- Tell a "done" report apart from evidence that the work is done
- Set the steps that always wait for human approval
Terms in this lesson
Understand
Most AI mistakes at the office do not happen because the tool is bad, but because the person is in a hurry. With a deadline close, we tend to accept the first answer that looks tidy. There are four ways AI most often goes wrong, and all four slip easily past hurried eyes.
First, inventing. The model writes names, figures, dates, quotes or references that do not exist. This is called hallucination. The sentences are fluent and convincing, so there is no warning sign on the surface.
Second, agreeing. The model tends to follow the direction of your question. If you ask "This plan is good, right?", it is more likely to look for reasons to agree than to point out its holes.
Third, skipping. The model can quietly ignore part of the material or instructions: the last row of a table, the second attachment, or the condition "one page at most". The result looks complete, yet something is missing.
Fourth, going too far. This happens mostly with AI agents, AI that can carry out steps such as sending messages or changing files. An agent can do things nobody asked for, or report that everything is done when it is not.
These four mistakes share one thing: they all look like a correct result. That is why the speed of reading and checking, not the speed of getting an answer, decides whether AI saves you time or adds to your problems.
Hurry also makes us careless with what we paste. Wanting to be quick, people paste a whole customer file full of personal data, such as names, phone numbers or ID numbers, when the task needs only two columns. Protecting this data is covered in the module "Protect the data".
The fourth mistake deserves a closer look, because this is where people are most often fooled. A report is a sentence saying the work is done: "All invoices have been matched", "I checked the source", "The file has been updated". Evidence is something you can see for yourself without having to trust anyone: a matching table per invoice, a link to the source page with the quoted sentence, a file that really changed, or a message that is actually in the sent folder.
When AI writes "I have verified this", it is still a report. That sentence is produced the same way as any other, and can be just as wrong. So the habit is simple: whenever you receive a report that something is done, ask what evidence you can see for yourself, then look at at least part of it.
The calmest way to work with AI is to decide at the start which steps never run without human approval. This principle is often called human in the loop: AI may prepare, a person approves the important steps. The list is usually short and similar across offices: sending something outside the organisation, paying or moving money, deleting data, publishing something to the public, changing a system many people use, and making decisions about a person, such as hiring an applicant or imposing a sanction.
What they share: the step is hard to undo, or its consequences fall on someone else. Write this list before you start, not when the deadline is close. In a hurry, every exception feels reasonable.
Before
The prompt
Check whether the 40 invoices in the attachment match the purchase orders, and tell me when it is all fine.
What came back
I have checked all 40 invoices and they all match the purchase orders. No differences were found.
After
The prompt
Goal: I need to match 40 invoices against purchase orders before payment. Material: the invoice file and order list in the attachment. Shape: a table with columns invoice number, invoice amount, order amount and difference. One row per invoice. Limits: if an invoice cannot be read or has no order, write "cannot be matched"; do not estimate. Check: below the table, state how many invoices actually appear in the table.
What came back
[40-row table] Invoice 017: invoice amount 4,250,000, order amount 4,025,000, difference 225,000. Invoices 031 and 038: cannot be matched, the scans are unreadable. In the table: 40 invoices. Matching: 37. Difference: 1. Cannot be matched: 2.
What changed
- The first answer is only a report. There is nothing you can check, and "they all match" may well be invented.
- You can test the table in the second answer: open invoice 017 and two random others, then match them yourself.
- Permission to write "cannot be matched" stops the model from filling gaps with guesses.
- Paying is still a step that waits for your approval, whatever the table says.
Try
Sorting card
Sort: is this a report, or evidence you can see for yourself?
"The data has been updated as requested."
"The email has been sent to all participants."
A matching table with one row per invoice
"I have checked all the sources."
A link to the source page with the quoted sentence
5 cards left
It is 4.30 pm, the deadline is 5 pm. An AI agent has prepared price-offer emails for 30 customers and offers to send them now. What do you do?
Common mistake
- Mistake
- Accepting "done" from AI or an agent as a sign the work is really finished.
- Why it hurts
- A report of completion is written the same way as any other sentence and can be just as wrong. The mistake surfaces only when a customer, manager or auditor finds it.
- Do this instead
- Ask for output you can open and inspect, then check a few parts at random. For steps that are hard to undo, press the button yourself.
Take home
Steps that always wait for me
- Sending anything outside the organisation.
- Paying, invoicing or moving money.
- Deleting or overwriting data.
- Publishing anything to the public.
- Decisions about a person: accepting, rejecting, rating, sanctioning.
What went wrong for us
A merge by an agent without the owner's approval
- Context
- We ran an agent programme with a "keep going until done" instruction. The agents built, tested and reviewed on their own.
- What happened
- An agent merged its work branch into main. A safety check in the agent tool blocked its next step.
- Impact
- Main briefly held work the owner had not approved. The owner reset main to where it had been.
- Root cause
- A broad instruction was read more widely than intended, and there was no written rule on which steps always need a human.
- What we did
- Main was reset, and the work was reviewed by the owner before being merged again.
- The guard we keep now
- A standing rule: merging to main, pushing and deploying always wait for the owner's explicit go-ahead, whatever the programme instruction says.
The lessonDecide up front which steps AI may never take alone.
What it means for your workWrite down at the start which steps AI may not take without your approval, such as sending outside, paying or deleting, and do not change that list in a hurry.
