Ten chapters of checking the machine.
Brief it properly. Decide the depth before you ask. Ask a different question. Make it argue against itself. Score it. Use a second one. Read the room it is aimed at.
Every one of those checks runs on material you chose, framed the way you framed it, against a standard you set.
Which means there's one participant in this whole arrangement that nothing in the book has examined yet, and it's the one holding the pen.
Your errors survive every technique in the previous ten chapters. They survive because they are upstream of all of them; you can't catch a bad question by checking the answer harder.
Start with the one that costs the most, because it is the error these tools amplify hardest and it does not feel like an error at all.
I told you to ask a different question. What I did not tell you is that when you ask again, you ask from inside the first answer's frame.
The first response you read sets the terms. It decides what the categories are, what counts as a consideration, roughly what range the numbers live in. Every subsequent question you ask is shaped by it, including the ones you believe are challenging it, because challenging something is still accepting its terms.
You have felt this without naming it. Somebody gives you a figure and every estimate you make for the next hour clusters around that figure, including the ones you arrive at by reasoning you would swear was independent.
Two defences, both cheap.
Write down what you expect before you look. One line, thirty seconds, before the first answer arrives. Now you've your own anchor to compare against, rather than inheriting theirs.
And when the first answer was substantial, start a completely fresh conversation for the second opinion rather than continuing the existing one. Not because the tool remembers. Because you do, and in a fresh window your own questions come out different. Try it once and read both. The difference will bother you.
Here is what that one line actually catches.
You are working out what it would cost to bring a piece of work back in-house from an agency. The figures below are invented to show the shape. Before you ask anything, you write:
I think in-house lands around £60k a year and the agency is about £90k, so we save thirty.
Then you ask properly, and back comes a fully-loaded cost of about £78,000 · salary plus employer costs plus tools plus the recruitment, which you had not counted.
Without the note, you read £78,000, think fair enough, still a saving, and spend the next hour refining a case built on somebody else's number.
With the note, you have a much better problem. You said sixty. It says seventy-eight. That gap is not a rounding difference · one of you is wrong about something structural, and four minutes will tell you which. It turns out you were both wrong in the same direction, because neither of you counted the two days a month you currently spend managing the agency.
Your number was worse than the machine's, and that is not the point. The point was having a number at all, because a difference is visible in a way that a single figure never is, and there is no difference unless you wrote yours down first.
You do not need to be right. You need to have committed, so that being wrong is something you can see.
Where it stops working: if you genuinely have no view, a made-up number is noise rather than an anchor. The test is whether being wrong would surprise you. If it would, write it down. If it would not, skip the note and write what you expect the second answer to say instead.
One more, and it is the other error these tools have quietly made worse.
Two hours into an approach that is not working. You know those two hours are gone and should play no part in what you do next. You feel the opposite, and the feeling usually wins, because stopping makes them wasted and carrying on means they might not have been.
Here is what changed. When starting again was expensive, sunk cost was at least an honest calculation. You were weighing two hours against a week of redoing it, and continuing was often correct. Now starting again costs four minutes.
The economics collapsed and the feeling did not move at all. Which means the pull you feel to continue is now attached to nothing, and it is the same pull, at the same strength, as when it was rational.
The question that cuts it: arriving fresh today, with no history, is this the approach I would choose?
If not, the two hours are gone either way. The only live question is whether you spend a third on top.
The most valuable thing in this chapter takes one line and almost nobody does it.
Before you send something consequential, write down what you expect to happen.
I think she comes back with two objections, one about cost, one about timing, and asks for it by Thursday.
One line, in a note, in a file you keep. Then when the reply arrives, look.
Do this twenty times and you'll have something almost nobody has: a record of how well you actually read situations. Not an impression. A record. And you'll find, as everybody does, that you are reliably good at predicting some things and reliably poor at others, and that the pattern is not the one you would have guessed.
Six lines. That is the whole thing, and each one costs eight seconds.
| Sent | I expect | What happened | | > |---|---|---|---| > | Budget paper to FD | Two objections · cost and timing. Wants it by Thursday. | Cost, yes. Timing never came up. Asked for it in two weeks. | half | > | Process change to the team | Priya pushes back, the rest go along with it | Priya was fine. Marcus raised three things in writing that evening. | wrong | > | Supplier note to ops director | He forwards it to procurement without comment | He did exactly that, within the hour | right | > | Headcount case to the board | They ask what happens if we do nothing | They asked what it costs to delay six months | half | > | Draft policy to legal | Comes back covered in changes | Came back with two, both about one clause | wrong | > | Pricing to the FD | Argues the margin, not the volume | Argued the margin | right |
Two right, two half, two wrong · and the average is the least interesting number on the page.
You read your seniors well and your peers badly. Every line involving somebody more senior is right or half right. Both outright misses are lateral · Priya, who you were braced for, and legal, who you had catastrophised. You have spent years learning to predict the people who assess you and almost none on the people beside you.
And you over-predict resistance. Three of the six expected more pushback than arrived, which is expensive rather than charming: a person expecting a fight writes defensively, and defensive writing is longer, hedged and harder to say yes to.
Neither of those is a thing anybody could have told you. It is not in a review and your manager cannot see it. It is visible only because you wrote the guess down before you knew the answer, and the guess is worthless the moment you have read the reply.
One line before you send. Eight seconds, and it is the only feedback loop you have that isn't filtered through people being polite.
Two errors, both made worse by the speed of these tools, and both cheap to defend against.
What did I expect, before I looked? Arriving fresh today, would I choose this approach?
Then one line on what you think happens next, kept somewhere you will see it again.
Under two minutes, and between them they check the one participant in this arrangement that nothing else does. You can brief perfectly, check exhaustively and score honestly, and still be confidently wrong in a way no amount of checking will reach, because every one of those checks runs on a question you chose.
---
### ▪ DO THIS > > Two questions and a prediction, before the next thing that matters. > > 1. Write your expectation before you look. One line, thirty seconds. Now you have your own number to compare against instead of inheriting theirs. > > 2. When the first answer was substantial, open a fresh window for the second opinion. Not because the tool remembers. Because you do. > > 3. Ask the fresh-start test. If I arrived today with no history, would I choose this? If no, the hours already spent are gone either way. > > 4. Then one line on what you expect to happen. She comes back with two objections, cost and timing, and asks for it by Thursday. Keep it where you will see it again. > > 5. When the reply lands, open the note. Write right or wrong and one word on why. Ten seconds, and it is the step that makes the other four worth doing. > > Under two minutes. Steps 4 and 5 take thirty seconds between them. > > When you have no time for any of it: do step 4 only. It is the one that compounds. > > You'll know it worked when your first prediction turns out wrong in a way you can name. Because that is a thing you learned about yourself that nobody could have told you.
---
Two questions and a prediction, and every one of them needs you to remember to ask.
That is the whole problem with this chapter and with the ten before it. Nothing anywhere is going to remind you.