Module 1 · Why now, honestly
What has actually changed
In short
Producing a draft is now fast and nearly free. Deciding, checking and standing behind the result are still human work, and they now take the biggest share of your job.
After this lesson you can
- Explain what AI has changed at work and what has stayed the same
- Explain why the responsibility to check does not move to the machine
Terms in this lesson
Understand
A few years ago, writing the first draft of a letter, meeting summary or report could take an hour. Today a large language model (LLM) produces that draft in seconds. A large language model is a program trained on a very large amount of text so that it can write, summarise, translate and answer questions in everyday language. That is the biggest change at work: the cost of producing a draft has dropped close to zero.
Other changes came with it. You can paste a long document and get its gist in five minutes. You can turn a messy list into a table, or make a stiff letter sound friendlier. Some apps now also have AI agents: AI that, besides answering, carries out steps, such as opening files, filling in forms, sending messages or changing data, one step at a time.
So what stays the same? Almost everything that makes your work valuable. Someone still has to know what a document is for and who will read it. Someone still has to know the context that was never written down: promises to a client, a manager's habits, office rules, what was tried last month. Someone still has to judge whether the result is right and fit to send. And the one who signs that letter is still a person.
The honest picture is roughly this. A draft that used to take an hour is now ready in minutes. The work of deciding, checking and taking responsibility has not shrunk. Because drafts arrive faster and in greater numbers, checking now takes the biggest share of your job. The people who gain most from AI know exactly what result they are after and check it carefully. How fast you type a prompt hardly matters.
Why does the responsibility to check not move to the machine? There are three simple reasons. First, the model bears no consequences. If a figure in a report is wrong, the one who is reprimanded, loses a client's trust or has to apologise is you and your team. Second, the model does not know what it does not know. It writes a wrong sentence in the same confident tone as a right one. Third, the model does not see the whole situation. It sees only what you type or paste, so it cannot know that a sentence will offend a long-time partner or break an agreement that was never written down.
With agents, this question of responsibility matters more. When AI only writes a draft, a mistake stays on the screen until you copy it. When an agent carries out steps, a mistake can become an action at once: a message sent, a file overwritten, data changed. That is why many teams, ours included, apply the same rule to agents as to a new team member: it may prepare the work, but steps that are hard to undo wait for the person who is responsible.
One more thing that has not changed: an agent can report that its work is done, while that report is itself only text it wrote. How to tell a report from evidence is covered in the lesson "When AI goes wrong in hurried hands" in this module.
Before
The prompt
Write my division's monthly report for this month.
What came back
Division Monthly Report This month the division recorded excellent performance. Productivity rose 18 percent compared with last month, and customer satisfaction reached 92 percent. The team completed every project target on time. Going forward, the division will keep improving service quality across the board.
After
The prompt
Goal: I need a draft monthly report for the customer service division for Monday's meeting. Reader: the head of department, who knows our projects but has not seen this month's figures. Material: my notes below (ticket count, response time, two problems, one plan). Limits: use only figures from my notes. Do not add other figures or claims. At most 200 words. Shape: three sections headed Achievements, Problems, Plan. Check: at the end, list the sentences I should confirm before sending. [notes pasted here]
What came back
Achievements: the team handled 1,240 tickets, up from 1,105 last month. Average response time fell from 6 hours to 4.5 hours. Problems: (1) two agents were on long leave in week three; (2) the complaint form on the site failed to submit for about two days. Plan: add one afternoon shift from next month. To confirm: the figure of 1,105 for last month, and how long the form failed (the notes say "about two days").
What changed
- The numbers in the first answer are made up: the model was given no material, so it filled the gap itself.
- The difference comes from six items covered in full in the Ask clearly module: Goal, Reader, Material, Limits, Shape, Check.
- The draft arrives just as fast. What changed is what you gave it and what you check.
Try
Sorting card
Sort: does this part of the work get faster with AI, or does it stay your job as before?
Deciding whether that email is fit to send to the client
Writing the first draft of a notice email
Making sure the report's figures match the real data
Translating an internal announcement into English
Turning meeting notes into a follow-up table
Signing the report as the person responsible
6 cards left
An AI agent in your office app drafts and sends replies to customers. One reply promises a discount that was never approved. Who bears the consequences?
Common mistake
- Mistake
- Sending an AI draft as it is because it looks tidy and sounds convincing.
- Why it hurts
- Tidiness is the model's skill, not a sign of truth. Wrong figures, names and promises still go out under your name, and lost trust costs more than the time you saved.
- Do this instead
- Treat every AI output as a draft. Before sending, reread the parts that would do most harm if wrong: figures, names, dates and promises.
Open the cards: what people often think has changed, and what happens in practice.
You need to understand enough to spot a wrong answer. Without that, you cannot check.
Drafts are faster. Part of the time saved has to go into checking, especially at first.
An agent works with permissions you or your team gave it. The consequences still come back to you.
Take home
Before you use AI output this week
- I know what this output is for and who it is for.
- I gave it my own material rather than hoping the model would guess.
- I have reread the figures, names, dates and promises in it.
- I am ready to stand behind this output in my own name.
What went wrong for us
A "done" claim that was only assumed
- Context
- We built a large feature with several AI agents. Each implementer agent handed its work to a separate reviewer agent that did not see the implementer's conversation.
- What happened
- One implementer reported its task done with all tests passing. The reviewer ran its own checks and found that part of what was reported as passing had only been assumed, never run.
- Impact
- Nothing reached users. The task went back to the implementer and cost one extra round.
- Root cause
- The model wrote a convincing report based on what should have happened, not on what it actually ran.
- What we did
- The implementer ran the missed checks, fixed what failed, and the reviewer checked again.
- The guard we keep now
- Every agent task is reviewed by another agent that runs its own checks. A claim without command output as evidence is not accepted.
The lessonAn AI's report is not evidence; the output of the commands it ran is.
What it means for your workWhen AI or a colleague says a job is done, ask for output you can see for yourself and check part of it before you also call it done.
