You are more powerful today than you have ever been in your life, if you can learn to drive this thing.
It comes down to the way you think, the questions you ask, and how you assess what you're given back. That's it. You now control an extraordinary asset, and if you learn how, you'll be paid more, you'll be worth more, and your future stops being something that happens to you.
I'll spend the rest of this book earning that paragraph. But I've just used the word drive, and it carries the whole promise, so let me say what I mean by it.
It's like being handed a race car. You need to learn how to drive it, not how to build the engine.
That distinction is where most people stop before they have started. They assume the price of entry is learning to program, decide they're too old or too busy or too far behind, and never come back to it. It isn't true and it never was. Nobody asks a driver to machine a piston.
What you do have to learn is what the pedals and the buttons actually do. That's a real skill. It's a smaller one than you fear, and nobody hands you the manual.
Now the part that should interest you more. Last year you were going round the track on a push bike. This year there's a car sitting in front of you. The track hasn't changed and the people you're going round it against haven't changed, and you can now cover it a great deal faster than you could.
Speed on its own isn't an achievement, though. With it comes the question this book keeps returning to, which is how you direct the thing well. A fast car pointed at the wrong corner just arrives at the wrong place sooner.
You've used one of these things by now, and you've probably had at least one moment where it genuinely impressed you.
Something came back fast, and well written, and better than you expected. You may have shown somebody.
Keep that. It was real, and it is worth more than the people rolling their eyes about all this will admit.
It was also roughly the first 10 per cent of what was available to you in that moment, and nobody tells you that part.
I know, because I stopped in the same place. For about six months I asked for things, got answers that were pretty good, used them, and assumed I had understood what this was.
Here is what I had not understood.
I was using it like a search engine. One question in, one answer out, take it or leave it; that is what the box looks like, and nobody had told me any different.
It is not a search engine.
It is closer to a very fast, very well-read colleague who joined this morning. Knows nothing about your company. Will attempt anything you ask. Rarely tells you when they have reached the edge of what they know.
You already know how to get good work out of somebody like that. You have been doing it for years.
Nobody had shown you it was the same job.
Let me tell you what this book is, so you know whether to keep reading.
It is about getting good at directing AI, so that you produce work your organisation did not think one person could produce. It ends with you asking to be paid more for it, and having the evidence to make that easy for whoever decides.
There is no code in it. There is a chapter on mindset, and it is not the kind you are expecting.
The rest is method, in the order I learnt it, with the mistakes left in.
One thing about how to use it, because there are exercises in here and some of them take twenty minutes. Read it straight through if that is the time you have. The arguments stand on their own and you will finish able to do most of this. The exercises are not the price of entry, they are what turns the method into evidence you can put in front of somebody · which matters enormously in the last chapter and not at all before then. Do them when you are ready to.
I am going to show you the difference in about four pages, in a job you have almost certainly done. Before that, a word about where I was standing when somebody finally showed it to me, because it was not far from where you are.
Here's the thing nobody says out loud, so I'll say it once and then we can get on with the work.
Somebody one desk over is going to learn this and you are not. Neither of you will be told which one of you it was, until the restructure.
That's the fear. It isn't that a machine takes your job. It's that a person who learned to drive one does, and you never got a warning.
I'm not going to sit in that for the rest of the book, because a book that lives in the fear is a book people put down. But you should know I know it's there.
Somewhere in the last three years you picked up an idea, and it's going to cost you money.
Nobody sat you down and told you. You absorbed it from the shape of the room.
The people demonstrating this write software. The people explaining it use words you would have to look up. The meetings happen in a department you are not in, and the invitations go to people whose job is the machine rather than the work.
So you concluded, quietly and reasonably, that this is a technical job, that you are not a technical person, and that your part in it will be to keep up.
That single idea has cost you more than any other belief you hold about your career right now.
It is also false, and it is false in a way that is worth money to you specifically.
You know from the note that I have never written software for a living, and that for most of my career I paid people who could.
What I did not say there is what I thought that made me.
I assumed it made me the less useful half of the arrangement. The one who talks about the work while somebody else does it, and who would be found out eventually.
What changed for me was not a tool and not a course. Somebody showed me a better way to ask. I tried it on a job I had already done badly that week, and what came back was not the same kind of object at all.
Two years later I build things on my own that would once have taken my development team months, and I build them faster than most of the people who write the code by hand.
I want to be careful here, because this is the part that sounds like a boast and is not.
I did not get cleverer. I am the same person, with the same brain, and I still could not write the software myself.
What I had, and did not know I had, was years of practice at getting good work out of somebody more technical than me. Briefing them. Checking them. Catching them being confidently wrong. Sending it back until it was right.
I said in the note that operating AI is a management job. Here is the part I left out, because it is the part that should annoy you: it has always been a management job, and the reason nobody has told you is that the field is being explained by engineers, to engineers, and they are describing the part they find interesting.
They handed you the engine schematic. All you ever needed was the steering wheel.
If this were one person's story it would be a coincidence. What convinced me was watching it happen to other people, in businesses I advise, none of whom write software either.
A finance manager who had been building the same board pack for six years. She now produces it in a morning, and her version has a recommendation in it, which the old one never did.
Nobody asked her to add that. It is the reason she is now in the meeting where the decision gets made rather than the one where it gets reported.
An operations lead who hated one particular part of his week enough to go looking for a way out of it. He found one, never mentioned it to anybody, and within two months was the person other departments came to when they were stuck.
He is not ambitious. He was avoiding a job he disliked, which turns out to be a perfectly good reason to become the most useful person in a building.
A graduate two years into her first job, doing the work graduates get given. She started writing down the exceptions nobody had a rule for. Six months later she owned the rule.
None of the three is technical. Not one of them learnt to code. All three did the same thing, which was to stop accepting the first answer.
That is the pattern, and once you have seen it you will start noticing it in your own building.
Think about the last person you had to get work out of who did not report to you.
You worked out what they were good at. You wrote them a brief clear enough to act on: the outcome, the deadline, who it was for, and what to flag if they hit trouble.
You checked what came back rather than assuming. When it missed you said so, and you said it without making it personal, because you needed them again next week.
There is no certificate for that and no course that teaches it. That is exactly why it is rare and why it is worth money.
What separates a mediocre answer from an excellent one is three things, and you already do all three. How well it was briefed. Whether the first answer was accepted. Whether somebody knew enough to check the parts that mattered.
You do all of that with people. Who are far harder to brief than any machine.
So let me show you the difference.
Here is how I used to ask, and how almost everybody still does.
“Write me a summary of these three supplier quotes.”
Here is the same request written by somebody who has managed people.
“I have to choose one of these three suppliers by Thursday and defend it to a finance director who will push back on price. Read all three quotes. Tell me which one you'd pick and why. Then tell me the strongest argument the finance director will make against that choice, and how I answer it. Flag anything in these quotes that's unclear or that I should be asking about before I commit.”
Same three documents. Same software. Ninety seconds of extra typing.
The first comes back as three tidy paragraphs, one per supplier, faithfully restating what you already sent. Everything in it is accurate. Everything in it is something you knew when you hit send.
The second comes back looking like this.
Pick: Supplier B. Higher headline price, lower total cost once the site visits in A's quote are counted as chargeable. > > Her strongest argument: B is more expensive on the number that appears on the page, and that is the number that goes in the board pack. > > Your answer: show both figures. The page price and the twelve-month price are not the same number, and only one of them is what you actually pay. > > Before you sign: B's quote does not say whether the rate is fixed for the full term. A's does. Get it in writing.
One reads like a summary. The other reads like advice from somebody senior.
Those three suppliers do not exist, and I want to be straight about that here rather than let you work it out somewhere around chapter nine.
There are two kinds of example in this book and they are held to different standards.
The failures are mine. The figure that was wrong by a factor of three, the message that should never have gone, the security claim in our own marketing that was not true, the checking system I built and never checked. Those happened, they happened to me, they cost me something, and every number attached to them comes out of a file I can open.
The worked examples are composites. The supplier quotes above, and the ones coming in later chapters. The situations are real and the shapes are real, because I have watched all of them happen. The people are invented, and they are invented for a boring reason: the actual people did not agree to appear in a book, and some of them still work with the people the story would identify.
So where you see a name, assume it is not theirs. Where you see a number about my own work, assume I can show you where it came from.
I would rather tell you that once, plainly, than have you decide for yourself halfway through that the vivid parts might be decorated. A book that asks you to check everything has no business being vague about which half of it is which.
Now look at what produced the difference; there is nothing technical in that second request. Not one word of it. Every part of it is something you have said to a person.
That is the shape, and you can put it on any work you do. Four blanks.
I have to decide [what] by [when] and defend it to [who], who will push back on [what]. Read all of this. Tell me what you would choose and why. Then give me their strongest argument against it and how I answer it. Flag anything unclear that I should be asking about before I commit.
Fill those in on something real before you turn the page. Two minutes, and it is the only part of this chapter you actually have to do.
This is the smallest version on purpose. Four blanks is what fits in your head today, and in chapter four it becomes a six-line brief you write once and reuse for a year.
One of those six is missing from the four above, and it is the biggest of the lot, so I will name it now rather than have you find it in forty pages.
You have told it what you need. You have not told it who it is.
It does not know — and left alone it will be a generally competent nobody, writing for a general audience, which is exactly the flavour of answer you have been getting and quietly blaming yourself for. One line fixes it, and the line is not “you are a helpful assistant” · it is the actual person you would want in the chair. You are a procurement manager with fifteen years in a services business who has been burned by a supplier before. Their experience, their standards, and what they are suspicious of.
That single line changes more than the other five put together, almost nobody writes it, and chapter four is where you learn to write it properly. Try it on the end of your four blanks today and you will see the size of it before I have explained anything.
I call it the AI Mindset. Five habits, and not one of them is technical.
You never accept the first answer. It sits in the safe middle of everything the machine has seen, because the middle is where nothing can be blamed on anybody.
You make it prove itself. The words are simple, and the second of the three questions is the workhorse: “Now give me the strongest argument against that answer.” When you want a sharper version of the same move, “which part of that are you least sure of?” · then go and look at that part yourself.
You give it a number, not an opinion. “Score it out of ten for whether it helps me decide, and tell me what would move it up.” Seven is something you can push on. Better is a wish.
You never trust one system on anything that matters. Paste the first answer into a second one and type: here is another system's answer to the same question, where is it wrong and what did it miss.
Most of the time they agree and you have spent thirty seconds. The rest of the time is why you do it.
You are the first person in the room to ask what could go wrong. The question is: if this is wrong, who finds out, and when. Ask it out loud in the next meeting where somebody proposes putting AI into a process. You will be the only one who did.
That is the mindset, and I am giving it to you in the first ten pages rather than the last ten. Chapter three is about how to hold it, because it is a way of thinking before it is a set of moves. Knowing it changes nothing. Doing it is the rest of the book.
I will be specific, because I think you have been sold vagueness before.
Work that used to take a team and a fortnight, produced in an afternoon, at a standard nobody can fault. A competitor analysis. A tender response. The board paper nobody has had time to write since March.
That is what job security is now. Not loyalty. Being the person whose output the place would visibly miss.
And it is what gets you paid. Outside IT, nobody has ever been given a pay rise for being good with software. People are paid more for producing a number their employer cares about.
Four columns. Date. Task. What it used to take. What it took.
Add a line every time; it takes twenty seconds and you will resent it for about a month.
In four months that note is your case, and almost nobody has one.
Same task, twice. Once the way you asked before. Once with the four blanks filled in · decide what, by when, defend it to who, who pushes back on what.
Then take the answer, and before you use a word of it, send the three questions. They are the same three every time, on anything, for the rest of your working life.
1. What did you leave out? > > 2. Now give me the strongest argument against that answer. > > 3. Show me the same thing in the form that makes the decision obvious to the person reading it.
Twenty seconds each.
Those are not three ways of saying check it. The first goes after what is missing, the second after what is wrong, and the third after whether it will land on the person who has to act. Different jobs, in that order, and chapter six is where I take them apart properly.
The second answer won't be slightly better. It'll be a different class of thing, and it'll have cost you a minute.
---
### ▪ DO THIS > > Run one task twice today. Ten minutes, and it settles the argument of this chapter without you having to take my word for anything. > > Before you start: check what your employer allows into these tools, and use a task that clears it. Most organisations have a rule and most people have never read it. Chapter fourteen covers how to send real work without sending the sensitive part of it. > > 1. Pick a task you already did badly this week. Something you resented. Not a test case — real work, real stakes, something you can compare against. > > 2. Ask for it the way you normally would. One line. Keep the answer. > > 3. Now ask again with the four blanks filled in. Here is the sentence again so you do not have to go back for it: > > > I have to decide [what] by [when] and defend it to [who], who will push back on [what]. Read all of this. Tell me what you would choose and why. Then give me their strongest argument against it and how I answer it. Flag anything unclear that I should be asking about before I commit. > > Fill in the four bracketed blanks with your own work and nothing else. Chapter four turns these four into the six-line brief. > > If you want the upgrade, add one line in front of it: You are [the person you would want in the chair], with [their experience] and [what they are suspicious of]. That is the identity line, it is the biggest single lever in the whole thing, and it costs nine words. > > 4. Then send the three questions, twenty seconds each. The same three as earlier, and the same three you will use for the rest of the book: > > > What did you leave out? > > > > Now give me the strongest argument against that answer. > > > > Show me the same thing in the form that makes the decision obvious to the person reading it. > > One hunts what is missing, one hunts what is wrong, one hunts whether it will land. Do not skip the third · it is the one nobody sends and the one your reader actually notices. > > 5. Put the two versions side by side and read them. Don't judge them. Just look at the gap. > > Ten minutes the first time. Ninety seconds every time after that. > > This is the full treatment, and it is deliberately more than most tasks deserve. Chapter five tells you when it is the wrong amount. Run it at full depth once, on something that matters, so you know what the ceiling looks like. > > If the second version isn't better: that is worth knowing. Some tasks genuinely don't need it, and chapter 5 is about telling which. If you want a likely culprit, look at who you said you have to defend it to — most people leave that as a category rather than a person. > > You'll know it worked when the gap between the two versions is bigger than you expected, and slightly annoying. Because it's been there every time you've used one of these things and you've been throwing it away.
Keep both. In the last chapter we work out what your time is now worth, and almost nobody keeps the before.
Everyone in your building gets the first answer. Almost nobody asks the three questions.
So do that this week, and then we start properly, with your week. Because the thing you call your job is not one thing.
It is five. And four of them are already being done better than you can do them.