You can answer a message perfectly and still lose the room. Nothing in the previous nine chapters will save you from it, because every one of them made you better at producing and none of them made you better at aiming.
A message arrives. Four lines, polite, asking for something specific.
You answer what it asks. You answer it well, quickly, and completely.
And it lands badly, or it lands nowhere, and you spend the next fortnight wondering what you got wrong, because on any reading of the words in front of you, you got nothing wrong at all.
You answered the message. You didn't read the room.
Aiming is where the value is, in a way that has nothing to do with the tools and everything to do with what you now have time to notice.
Under any request there are three things stacked, and the message contains one of them.
What they said. The literal ask, available to everybody.
What they actually want. Usually adjacent, occasionally the opposite. Somebody asking for a comprehensive comparison of five options frequently wants permission to choose the one they have already chosen. Somebody asking you to review something often wants it defended, not improved.
Why they want it. Almost never about the task. Wanting to look competent, wanting not to be blamed, wanting it settled so it stops occupying their week, wanting to be seen to have handled it by somebody two levels up who appears nowhere in the message.
Can you send me the figures for last quarter is a request for figures. Underneath it is usually I have to defend something on Thursday.
Send the figures and you have completed a task. Send them with the one line that anticipates Thursday and you have done something else, and the difference in how you are seen is nothing like proportional to the effort.
The move is a question you ask yourself, not them. What will this person have to do next, and what will make that easier? You do not have to be right about the third layer, only to have considered that it exists · at which point your output stops answering a task and starts answering a situation.
That is where the returned hour goes, and almost nobody spends it there.
Every request arrives carrying a stated urgency. Every situation has a real one. The two are frequently different, and the gap tells you almost everything.
Stated far above real means somebody is manufacturing pressure · a supplier at the end of their quarter, a manager passing on a panic they never examined. Do not let their urgency become yours.
The reverse is rarer and more useful. Real above stated means somebody is under pressure they will not admit to: understated language, a favour that would take three days. Noticing that is worth more than replying quickest.
Two questions settle it. What actually happens if this is late? And who is applying the pressure, and what is happening in their week? If nobody can answer the first, that is a question to ask rather than a licence to slip. Ask it in writing, and let the answer set the date.
The person who wrote to you is rarely the only person who matters, and they're quite often not the one who decides.
Before anything consequential goes out, spend a couple of minutes on the people who are not in the message.
Two things about each of them. How much do they influence the outcome, and how likely are they to agree with where this is going.
It is an old management grid and I didn't invent it. Two axes, in your head, thirty seconds.
The useful part is what falls out of it. Somebody with high influence who is likely to disagree is the single most important person in your work and they aren't on the email. Your output has to survive them. Not persuade them necessarily, but at minimum not hand them the easy objection.
Somebody with high influence who agrees is your route, and most people never think to use them.
And somebody with strong opinions and no influence will absorb an unlimited amount of your time if you let them, and the reason they get it is that they're the loudest voice in the thread.
The most common way careers stall on this is producing work that's correct, well-received by the person who asked, and quietly killed by somebody two rooms away who was never consulted and didn't have to be.
There is a practical version of all this and it's one line.
Tell it who this is for. Not the topic. The person.
And don't describe them in categories. Categories produce writing for an average, and the average reader doesn't exist.
The best version of this instruction I've used is one line:
You are writing for a board member scanning this on their phone at 6am.
Look at what that does. It gives a person. Someone senior, busy, accountable. A place — a phone, which kills your three-line paragraphs before you write them. A time. 6am, before coffee, before the day has started going wrong. And a constraint. Scanning, not reading, so anything requiring a second pass is already lost.
Four facts, fourteen words, and every one of them changes the output.
Compare it to write this for executives, which is what almost everybody types, and which describes a demographic rather than a moment.
So build your own. Not for the finance team. For the finance director who has already had this pitch twice and did not like it either time, reading between meetings. Not for a customer. For someone who has been let down by a supplier before and is looking for the reason to say no.
A person, a place, a time, and one thing that's true of them right now: a worry, or a constraint like scanning, not reading. Write it once for the three people you produce work for most, and reuse it for a year.
This is the single highest-return sentence you can add to any instruction, and the reason it works is that without it, the thing is writing for an average of everybody, which is a person who doesn't exist.
And there's a diagnostic that costs nothing. When something comes back and feels subtly wrong and you can't say why, ask it who it assumed the reader was.
The answer is often the entire explanation. It has been writing for a general business audience while you needed something for one sceptical finance director who has heard this pitch twice before; you have found the fault in one question, without re-reading a word.
There is a stronger version of this and it turns on one word.
Most people, when they think about the other side, ask what might they think about this? That produces a polite paragraph of speculation, written from your chair, about a person who isn't in the room.
Change the instruction from imagine to be.
You are now [that person] receiving this. Answer as them, in their voice. Where do you push back, and what do you ask for that I have not given you?
Not what would she think. Be her and answer.
The difference in what comes back isn't small, and it is the same difference you get from a good role-play in a training room versus a discussion about the role-play. One produces observations. The other produces an objection in her register, phrased as she might phrase it.
Here is the difference on one paragraph, and it is the clearest demonstration in this chapter.
You have written a recommendation to move three sites onto one supplier. It is well argued and the saving is real. You are sending it to a regional manager who has run her site her own way for nine years.
Ask what she might think and you will get a paragraph about concerns over local control, worries about service levels during transition, and a wish for existing relationships to be respected. Not wrong. Written from your chair, about a category of person, containing nothing you had not already suspected, and no use to you on a Tuesday.
Change one word. Not imagine her. Be her:
You are Angela, regional manager at the Northampton site for nine years. You are reading a proposal to consolidate your supplier into a national contract. Answer as her, in her voice. Where do you push back, and what do you ask for that I have not given you?
Right. Who do I ring at four o'clock on a Friday when a delivery hasn't turned up? Because at the moment I ring Dave and Dave sorts it, and I've got nine years of Dave. Your paper says “national account management” and I've been on the end of national account management before · it means a ticket number and a callback on Monday. > > And what happens in the first six weeks? You've costed the saving from month one. I've done three of these and month one is always the worst month of the year. Who is covering that, me or you? > > One more. You've got the saving as a total across three sites. What's it worth on mine? Because if the answer is that Northampton gets slightly worse service so that two other sites get cheaper, say so and I'll live with it. Don't tell me it's better for everyone when I can see it isn't.
Those are three specific things, in a register, that you can answer before she asks. The first one is a name and a phone number and it costs you an email to find out. The second is a line in the paper about the transition period. The third is the one that would have killed the whole thing in the meeting, and it would have killed it in front of other people.
Be precise about what that's worth, because it's easy to overclaim. It is still a guess. The machine has never met Angela. Every word of that is invented from a role and nine years and a consolidation, and the real Angela may care about none of it.
But you now have three questions to take to her, which is a completely different object from a paragraph of speculation. Its job is to hand you the question you take to her, not the answer you take into the room.
Do it for the person who decides, and then again for whoever loses something if this goes ahead. Because the second one is where the real resistance lives, and they are almost never the one you were writing to.
Then do the thing that makes it real: take the sharpest objection to an actual human and ask whether it lands. A guess you've tested is worth more than a guess you've rehearsed.
I use this on competitors as well. Not how might they respond to this, but be each of them in turn and answer. What they say back is frequently something I had genuinely not considered, and it arrives in about ninety seconds.
One more, and it's the one that catches the errors nothing else does.
Before anything goes out, put it in front of a different lens and ask a question that isn't about quality. Ask whether it makes sense in that person's world.
This is not proofreading and it isn't fact-checking. It is the question of whether a claim that's internally consistent is plausible in the reality the recipient actually lives in.
I have caught output claiming a sector was booming in a place where the situation on the ground made that impossible. Nothing in the text was wrong. Every sentence was defensible. It simply couldn't be true for anyone who knew the place, and sending it would have told that reader, in one line, that we didn't.
That is a category of error no amount of checking the work against itself will find, because the work is consistent; it is only wrong from outside.
So the last question before sending is not is this right. It is: would the person receiving this recognise their own world in it?
The word makes it sound like a gift somebody either has or hasn't, and that is the wrong word. Intuition is what we call a process once we have forgotten the steps in it.
Watch anybody who is genuinely good at this and they are not sensing anything. They are running a short list, fast, mostly without noticing they are doing it.
Who else will see this. What has already been decided. What the sender is afraid of. What happens to them if this turns out to be wrong.
Four things, every one of them knowable, not one of them mystical. And that matters to you for a specific reason: a list can be learned and a gift cannot. If reading a room really were intuition, you would either have it or you would not, and this chapter would be a waste of your afternoon.
A list gives you one other thing, which is a way of being wrong usefully. You cannot check whether your feeling about somebody was right. You can check, every time, whether you asked who else would see it.
One warning before the list, because this is where the discipline usually dies.
People keep a record of what they produced and almost never of how it landed. The document is in a folder. Whether it worked is in nobody's file.
Which means the half of your work most dependent on judgement · the half that faces other people · is the half you have the least evidence about, and it stays that way for an entire career unless somebody decides otherwise.
You already have the fix from chapter eleven. One line before you send, on what you expect to happen. It costs eight seconds and it is the only way this ever becomes something you get better at rather than something you have opinions about.
Before the next consequential thing you send.
What will this person have to do next? Who else decides, and would they object? Is the urgency theirs, or is it real? Would they recognise their own world in this?
Four questions, about three minutes, no tools required.
Most people never ask any of them, which is why most work is technically correct and lands with a sound like nothing at all.
You now have the time to ask them. That is what the time you got back was for.
Which accounts for the machine, and the work, and the person receiving it.
It leaves exactly one participant in this arrangement unexamined, and it's the one who has been choosing every question in the book so far.
---
### ▪ DO THIS > > Aim the next consequential thing you send at one named person, starting before you write a word of it. > > 1. Write the reader in one line. A person, a place, a time, and one thing true of them right now — a worry or a constraint. For the finance director who has heard this twice, reading between meetings, worried it lands on her budget. Not “for the finance team”. > > 2. Put that line at the top of your instruction. Before the task, not after. > > 3. Now write the draft. Then be them. Paste it back with: > > > You are now [that person] receiving this. Answer as them, in their voice. Where do you push back, and what do you ask for that I have not given you? > > Then run it again as whoever loses something if this goes ahead. That one is where the resistance lives. > > 4. Answer their objection inside the draft, before they raise it. That single move is what senior people notice. And if the objection matters, put it to the real person before the meeting rather than after. > > 5. Last check, and it is not about the words. In a fresh window, with no history: would a [their role] in [their situation] recognise their own world in this? A thing can be internally perfect and impossible for anyone who actually knows the situation. > > Steps 1 and 2 take ninety seconds. Step 3 costs a round-trip and step 4 costs a rewrite. Budget ten minutes the first time and five after that. > > When you cannot name the reader: you have found the real problem, and no amount of rewriting will fix it. Go and ask who this is for. > > The signal to watch for: people acting on your work in the meeting rather than taking it away to think about. Treat that as the sign you aimed well, and start keeping a record of when it happens.