On 23 July 2026 I landed at Gatwick and spent the next fifteen minutes talking to a man about whether he was going to have a job.
He organised the cars. Not one car, all of them, matching arriving passengers to vehicles that had to be moving before the aircraft was on the stand. He asked what I did. I said AI, and that I was in London to do some interviews about it, and I watched him decide whether to say the next thing.
He said it anyway. He'd used ChatGPT a bit. He didn't know how any of it worked, he couldn't tell what it would do to the business he was in, and underneath both of those was the real one: he didn't know whether he'd still be earning in a couple of years. He wasn't being dramatic about it. He was being polite about something that frightened him.
So I gave him the honest answer.
Change takes longer than the headlines say and arrives more completely than the sceptics expect. Some of it would start inside six months. Most of it would take a couple of years. And yes, parts of what he did every day would go, because a system can already do them and nobody is going to keep paying a person to do work a system does for nothing.
Then I told him the part he wasn't expecting, and it's the argument of this chapter.
Every piece of work either of us does runs through five stages. Four of them are already being done better by a machine. One of them is not, and almost nobody can name it.
That is why is my job safe is the wrong question. It's too big to answer and it arrives too late to act on. The useful question is which of the five you are actually being paid for, and you can answer that this afternoon.
This is not a theory about jobs. It is a description of what happens between somebody asking you for something and you handing it over. It's the same five whether you are pricing a job, writing a board paper, or getting a passenger into a car.
1. Gather. Find what already exists. The numbers, the file, the precedent, the last version, what the supplier said in March.
2. Notice what's missing. The questions that occur to you, and the ones that don't. What is absent from the pile in front of you, and whether its absence matters.
3. Judge. What this means, for these particular people, in this particular business, this week. What it is safe to conclude and what it isn't. Who will be difficult about it and whether they're right.
4. Synthesise. Put the past, the present and the gaps together into one thing that holds. Not a list of what you found. A position.
5. Land it. Get it into somebody else's head at the lowest possible cost to them. This is the stage everybody underrates and it is a harder problem than it looks, which is why it gets its own section below.
Read those five again and notice something. Not one of them is your job title. They are what your job title is made of, and they are made of the same five in every role in your building.
Here is where I am going to say the thing most people writing about this will not say.
On gathering, the machine is already better than you. Not faster. Better. It reads more, forgets less, and does not get bored on page forty. There is no version of the next ten years where a person competes on this and wins.
On synthesis, it is usually better. Give it the material and ask for a position rather than a summary and it will produce one, with the reasoning attached, in less time than it takes you to open the folder.
On landing it, it is usually better. It will restructure the same content for a board, a customer and a technician without complaint, and it will do it in the form each of them can actually absorb.
On noticing what's missing, it is better than you at half the job. Ask it what you have failed to consider and it will list things you had not thought of, reliably, on any topic. That should be uncomfortable, because noticing gaps is what most people privately think their experience is for.
The half it cannot do is the half nobody has written down. It does not know that this client always goes quiet before they cancel, or that the number from that department has been wrong since the reorganisation, or that the person who has to approve this is in the middle of something and needs it next week rather than today. Those absences are not in any training set. They are in the room.
And on judgement it is not better, and it isn't close.
Not because judgement is mystical. Because judgement is deciding what a thing means for these people, here, now, and carrying the consequence of being wrong about it. A system can produce the sentence. It cannot be brought into a room afterwards and asked what it thought it was doing.
Four out of five. That is the honest count and I would rather you had it from me than found it out slowly.
Picture the tower at an airport, and put yourself in it.
The aircraft coming in are the systems doing their work, and every one of them is better than you are at the thing it does. You are not going to fly them. Your job is to say this one lands now, that one holds, that one slows down, that one goes. Line them up. Keep them apart. Decide the order.
And the traffic you are directing is the data moving through your business.
Nobody in that tower is the best pilot on the airfield, and it has never once been the job. The job exists because without it, four extremely capable aircraft arrive at the same place at the same moment.
That is the shape of the work now, and it is the reason the rest of this book is about thinking rather than typing.
Landing it deserves more than a line, because it is the one people think is presentation and it isn't.
Communication is a coding problem. You have something in your head, and you encode it, into words, into a document, into a tone of voice. You transmit it. Somebody else receives it and decodes it using their own experience, their own worries, and whatever they were doing thirty seconds before it arrived.
The message you sent and the message that was received are two different objects, and only one of them matters.
Almost everybody optimises the first. They make the document more complete, more accurate, more defensible. Then they send nine paragraphs to somebody who reads two, and the decision gets made on the two.
The machine is genuinely good at this stage, and it is good at it for an unflattering reason: it has no ego about the version it just wrote. Ask it for the same position at half the length, for a reader who is tired and sceptical, and it will simply produce it. It does not experience that as an insult.
That is worth stealing. Not the tool. The willingness.
Go back to the man at Gatwick, because his job ran all five and nobody had ever shown him that.
Arrival times, flight status, who was on which manifest. Gathering. Then the thing that isn't on the screen: this flight is always late on a Friday, and that passenger has a connection nobody has flagged. Noticing what's missing. The flight lands ninety minutes late, the car has gone, and there is a passenger who was promised something, so what happens now and who gets told. Judgement. Then a plan that holds, made of the cars, the drivers and the four minutes he actually has. Synthesis. Then saying it to a driver, a terminal desk and a tired passenger, three different ways, so that each of them does the right thing next. Landing it.
Five stages, one job, one badge. The gathering is going. The synthesis is going. Most of the landing is going.
The noticing and the judgement are the reason he is worth employing, and nobody had ever told him there was a difference.
That is the whole of this chapter, and it applies to your week exactly as it applied to his.
Now the thing that actually worries me, and it isn't unemployment.
The path of least resistance, when a well-formed and logical answer arrives, is to accept it. It reads as reasoned. It has structure. It anticipated the obvious objection. Everything about it says this has been thought about, and the felt need to think about it yourself quietly disappears.
Do that once and nothing happens. Do it for a year and something does.
Critical thinking is not a talent. It is a habit, and habits decay when they stop being used. The muscle that asks hold on, is that actually true is the same muscle whether it is pointed at a colleague, a supplier or a screen, and it is currently being offered a thousand opportunities a week to stay in bed.
I am not neutral about this. I think it is the part of being a person we should fight hardest to keep, and I think it will have to be a deliberate discipline rather than something that survives on its own, because nothing in the design of these tools will remind you to do it.
The alternative is a workforce that accepts thoughts it was handed, at speed, at scale, without anybody noticing the moment it started. That generally ends somewhere bad, and it ends there quietly.
This book has a chapter on the mechanism, which is next, and a chapter on the discipline, which is twelve. Between here and there, every technique I give you is a way of keeping the judgement alive while handing over the other four.
Or ten seconds, if that is what you have. Think of last week and name the one piece of work where you were genuinely judging rather than gathering. If nothing comes, that is the finding and you already have what this chapter is for. The twenty-minute version below just puts a number on it.
Open last week's calendar and your sent items. Do not work from memory, because memory hands you the week you meant to have and the calendar has the week you had.
Write down every distinct piece of work. Beside each one write which of the five it actually was · gather, notice, judge, synthesise, land. Then total the hours against each name.
Most sheets come back weighted towards gathering, synthesis and landing. That is normal rather than damning. It describes how the job was scoped, and the scoping was somebody else's work.
Here is a week, sorted. It belongs to somebody who runs pricing for a mid-sized distributor, and it is a completely ordinary week with nothing dramatic in it.
| Hours | The work | Stage | > |---|---|---| > | 6 | Pulling competitor prices into the tracker | 1 · gather | > | 4 | Building the monthly margin pack | 1 and 4 | > | 3 | Reformatting the pack for the sales meeting | 5 · land it | > | 2 | Chasing three suppliers for updated cost sheets | 1 · gather | > | 5 | The quarterly review deck | 1, 4 and 5 | > | 2 | Answering questions about last month's numbers | 5 · land it | > | 1 | Deciding what to do about the Kelso account | 3 · judge | > > Twenty-three hours. One of them is judgement.
Look at that last row before anything else. One hour in twenty-three, and it is the only hour on the sheet that could not have been done by somebody who had never met these customers.
The Kelso hour was this. A long-standing account had asked for a discount that the tracker said was refusable, because the margin was already thin and the volume did not justify it. Every number on the page said no. She said yes, on a smaller number than they asked for, with a volume commitment attached — because she knew they had lost a contract in March, that this was the first time in eleven years they had asked for anything, and that the person asking had had to go to his own board to do it.
None of that is in the tracker. It is not in any system. It is the entire reason she is employed and it occupied one hour of her week.
Now the uncomfortable bit, and it is why this exercise is worth twenty minutes. Six hours went on pulling competitor prices into a tracker. That is the largest single block on the sheet and it is gathering, start to finish. She is not bad at it · she is the best in the building at it, which is exactly the problem, because being the best in the building at gathering is a description of a job that is leaving.
Then the move, and it costs eleven minutes. She keeps doing the tracker. But on Friday she adds three lines underneath it: what moved this week, what she thinks it means, and what she would do about it. Nobody asked for those three lines. They are noticing and judging, on material she was already handling, and they take the time it takes to type them.
Inside two months, the three lines are the thing people open the email for and the tracker is the attachment nobody scrolls to.
That is the whole chapter, on one sheet of paper, on a week that had nothing special in it.
Now the harder pass, and this is where people stop enjoying it.
Office language is built to make gathering sound like judgement. Go back over anything you marked two or three and hold it against these.
“I own the month-end close.” If the close runs to a checklist whose shape hasn't changed in years, and every exception goes upstairs for somebody else to rule on, that's gathering in a very good coat.
“I manage the supplier relationship.” Where managing it means sending the reminder on the agreed day and forwarding the reply, it's a verb with a courteous name.
“I approve the invoices.” An approval that has rejected nothing since you inherited it is a signature, and a signature is gathering.
“I train the new starters.” Training somebody to perform a task is that task performed twice. It becomes judgement on the day you're deciding what the new starter is for.
“I'm the only one who knows how the system works.” That is a moat, and it's the one that worries me most, because it holds exactly until the process gets written down. Writing processes down is the single thing these systems are best at.
You will sit with somebody for a fortnight explaining it patiently, so that it can finally be documented properly. Then it's documented.
Two questions settle most of the arguments you're about to have with yourself. When this goes wrong, who decides what happens next. And what does being wrong cost, in money or in a relationship, that can't be got back.
Where somebody else decides and the cost is an afternoon of rework, you were gathering.
If you're two years into your first job, this chapter matters to you more than to anybody else reading it, and for a reason nobody will tell you at your induction.
Graduates are hired to gather and assemble. That is what entry-level work is. Fetching, checking, formatting and building the first draft of somebody else's pack. It was the historic apprenticeship and it worked, because three years of it taught you what ordinary looks like, and knowing what ordinary looks like is where judgement comes from.
The apprenticeship is the part that's moving.
That is not a reason to despair; it's a reason to move deliberately rather than serve time. The people ahead of you got to judgement by waiting. You will have to get there on purpose, about two years earlier than they did, and the ones who work this out are going to pass a lot of people who have been there longer.
There is only one move in this chapter and it is the same move at every level.
Stop being the person who gathers. Start being the person who notices what's missing and says what it means.
Somebody keys supplier invoices. All week, every week, and the work is going.
She starts sending a note on a Friday. Three invoices this week that didn't match their purchase order, here is which supplier, here is what it looked like last month. Nobody asked for the note and it takes eleven minutes.
Inside two months she is the person the finance director asks about that supplier, and the keying has gone somewhere else, which is exactly what she wanted and told nobody.
Look at what she actually did. She was already gathering, so she had the material. What she added was noticing and judging, in eleven minutes a week, on work she was doing anyway. She didn't ask permission and there was nobody to ask, because the job she moved into did not exist until she described it.
The rung you're standing on happens to be exactly the work these systems do well. The hours they hand back are the hours the move needs. That is a piece of luck worth using rather than admiring.
I ran this sort myself, on software rather than staff, in systems I pay for out of my own money.
Twenty-five jobs run under a written routing policy. Eighteen go to a cheap fast model and six are pinned to the expensive one, which leaves one job I can't place from my own table.
Each pinning carries its reason in plain English. What I weighed was the size of the mess when the output goes wrong, and who has to answer for it. Difficulty barely entered.
There is a hole in that, and you should have it before you trust the rest. I hold cost telemetry on all twenty-five. I hold quality telemetry on none, because the folder that would contain it is empty, and I have looked.
So I know what the eighteen cost me. I can't tell you which of them I sorted wrongly, and that hole is still open.
Your employer will run the same sort with worse information than I had, on people rather than software, and in most buildings nobody will ever write the reason beside the name.
Five numbers and a total. Where your hours actually went, against the five stages, last week.
Now one decision, and only one. Pick the single piece of work where you are currently gathering and could be judging, and do the eleven-minute version of it this week. Not a plan. One note, on work you already touch, that says what you noticed and what you think it means.
Put a date on the sheet and keep it, because in the last chapter we work out what your time is now worth and this page is the before.
The car came, eventually. He walked me out to it, which he did not have to do, and on the way he asked for my details so he could stay in touch. Then he said he was going to go and learn this properly, so he'd be worth more to whoever he worked for next.
I have no idea whether he did. That is the honest end of the story and I'm not going to tidy it up for you.
But I know what he had that most people don't, and it wasn't confidence and it certainly wasn't a plan. He'd stopped asking whether his job was safe, which is a question nobody can answer, and started asking which part of it was actually his. That took him fifteen minutes in a car park.
It is going to take you twenty, and you have the advantage of a sheet of paper with five numbers on it.
Then there is the other half of it, which almost nobody does, and which decides whether any of this ever reaches the person who signs off your salary. A climb nobody witnesses is just a walk.
We come to that. But there is something smaller and much closer first, and it happens in the second after an answer lands on your screen.