Correct work that nobody can act on isn't half a win. It is indistinguishable from not having done it.
Watch somebody the moment they understand something.
They pause. Their breathing changes. Their head tilts slightly, as though the information arrived from an angle they were not facing. And then some version of the word wow comes out of them, usually quietly, often to nobody.
I have watched that happen a lot now, and I can tell you exactly what it isn't. It isn't the moment they received good information. They received that a few seconds earlier and it did nothing.
It is the moment they could see it.
That gap, between correct and visible, is where most careers quietly stall. You did the work. You checked it, you scored it, you used two systems and read the disagreement. Then you put it in nine paragraphs of prose and sent it at 6pm, and the person who had to act on it skimmed the first two and made the decision they were already going to make.
Which is the sentence at the top of this chapter, arriving on your own work.
Your instinct, once you get good at the checking, is to add more. More caveats, more context, more of the reasoning that made you confident; you are proud of the reasoning. It cost you something.
The person receiving it does not want your reasoning. They want to run their own decision on top of your work, and every extra paragraph is a tax on their ability to do that.
So the last pass on anything isn't another check; it is: show me this differently.
Make it a table. Make it a chart. Make it five bullets and a recommendation. Explain it for somebody with ninety seconds who has to choose.
And do that with the same tool you did everything else with, because it's genuinely good at this and it takes one sentence. Give me this as a table with the decision in the left column. Turn this into something a person could read in sixty seconds. What is the one chart that would make this obvious?
You will find the answer was often a table all along, and you had written it as prose because prose is what you were taught to produce.
Here is what that one sentence does. The same work reaching the same conclusion, written by the same person, ninety seconds apart.
What you wrote:
Following our review of the three shortlisted suppliers, we have considered pricing, implementation timelines and support arrangements. Supplier A offers the lowest headline cost but their implementation window of sixteen weeks would take us past the Q3 deadline, and their support is business-hours only. Supplier B is approximately 12 per cent more expensive but can implement within nine weeks and offers extended support hours, although their contract terms include an annual uplift clause which is currently uncapped. Supplier C sits between the two on cost and timeline but has the strongest support offering, and is the only one of the three able to provide a named account manager. On balance we would suggest that Supplier C represents the most appropriate option, subject to further clarification of their pricing structure. > > (129 words. Everything in it is true.)
What you send:
Recommendation: Supplier C · the only one that hits Q3 with support we can hold somebody to. > > | Verdict | | Cost | Live by | The one thing to watch | > |---|---|---|---|---| > | Take it | C | +6% | Week 10 | Pricing structure unclear. One question, answer by Friday | > | Rule out | A | Lowest | Week 16 · misses Q3 | The timeline kills it. Nothing else about A matters | > | Hold as second | B | +12% | Week 9 | Uncapped annual uplift | > > All three costs and A's and B's dates are taken from the quotes. C's week 10 is their own estimate and I have not verified it · if it slips a fortnight we are where A already is. > > If you want A anyway: the Q3 date moves. That is the trade.
Read the two again and notice what actually changed, because it was not the writing.
The prose hides the decision inside a paragraph of considerations. The table puts the thing that kills supplier A in bold, in the column where it belongs, where you cannot read past it. On balance we would suggest became Recommendation: Supplier C, and the uncapped uplift stops being a subordinate clause buried thirty words into a sentence about something else — which is where the second most dangerous fact on the page had been sitting.
And the last line is the one that gets you invited back. If you want A anyway, the Q3 date moves. You have pre-answered the pushback and handed the decision back to the person whose decision it is, without pretending you do not have a view. Nothing in the prose version does that, and it is not because the writer did not know it. It is because prose has nowhere to put it.
Identical facts, and about ninety seconds of extra work.
There is a thing every manager knows in principle and forgets in practice. People take information in differently.
Some will listen to a five-minute summary before a meeting and arrive fully briefed. Some want a page they can read and mark up. Some won't understand anything until they've sat with the thing themselves and turned it over.
You aren't going to know which one you've got, and asking is awkward.
So the version you produce should survive all three. A short spoken summary, a page that stands alone, and the underlying detail available for the person who wants to dig. That sounds like three times the work. It is one extra instruction, because the material already exists and you're only asking for it in another shape.
The cost is about ninety seconds. The difference in whether it lands is total.
Now the part that builds something you cannot buy, which is a reputation for being reliable.
On client work, every figure we publish carries a colour. Green means verified against the primary source. Amber means desk research, plausible, unverified. Grey means open, we don't know.
Three colours, next to the numbers, on the face of the document.
One of the tabs on a recent piece of work is entirely amber, and it says so at the top.
Read that again, because it is the whole idea. A page of work that announces, before you read a word of it, that none of it has been verified.
Every instinct says that's a bad look. It is the opposite. The client now knows exactly which parts they can take to their board and which parts need another week, and they learned that in one second instead of finding out in the meeting.
And here is the thing that surprised me. The amber page made the green pages more believable, not less. If you're willing to mark your own work amber, your green means something. A document where everything is presented with equal confidence tells the reader nothing about any of it, and a careful reader knows that, so they discount all of it evenly.
You don't need colours. You need the habit. This figure is from the filing. This one is an estimate. This one I couldn't confirm. Say it in the document, not in the meeting when somebody asks.
That sentence is what your senior people have been waiting years for somebody to say.
One practical thing that will otherwise undo all of the above.
Charts sent as inline data, embedded directly in the message, are the technically elegant way to do it. They also fail to render in some of the most widely used mail clients, which means a proportion of your readers open a considered visual and see a blank space or a broken icon, and draw the obvious conclusion about the person who sent it.
Attach them as ordinary image files instead. Duller, and it works everywhere.
The general rule is worth more than the specific fix. A visual that does not display is worse than no visual, because it's not neutral. It is evidence of carelessness, arriving in place of your argument.
So look at it. Send it to yourself. Open it on a phone. That is thirty seconds against the alternative, which is a senior person's first impression of your work being a grey box with a question mark in it.
Here is the part people resist, and it's the highest-return thing in this chapter.
When you work out how to do something well, give away the method.
Not the output. The method. The exact instruction you used, the check that caught the error, the way you got it into a table that made the decision obvious. Send it to the person who has the same problem. Put it where your team can find it. Show somebody in ten minutes what took you two weeks.
The instinct against this is real and I understand it. If the method is what makes you valuable, giving it away spends the thing that makes you valuable.
That instinct is wrong, and it's wrong for a specific reason.
The method is not the scarce thing. It is a paragraph. Anyone can copy it and most people won't use it, because the hard part was never the instruction, it was the judgement about when to apply it and the discipline to act on a bad score.
What you actually get for giving it away is this. You become the person who made three other people better at their job, and that's a fundamentally different thing to be than the person who produced good work. One of them is an employee with strong output. The other is somebody whose departure would cost the organisation something it cannot easily replace.
There is also a quieter effect. Teaching it forces you to understand it. The first time you explain your checking process to somebody who asks why, you'll find the two steps you do out of habit and cannot justify. Keep one. Drop the other.
People hear give away the method and picture running a session, so let me be exact about the size of this, because the version that works is much smaller than the version people imagine and never happens.
It is one message, to one person, about one thing they already have a problem with.
You mentioned the board pack takes you two days. This is the instruction I use on mine, paste it under whatever you've drafted. The bit that does the work is the last line · without it you get a lecture instead of a question. > > Score this out of 100 across five dimensions: hook, audience, proof, emotion, call to action. 95 and above is exceptional and rare, most first drafts land between 76 and 88, score accordingly. For each one give the score, one sentence on why, and one fix. Then rank the fixes by how many points each would gain. For anything under 82, give me one question that would fix it, maximum twenty words, no preamble.
That is it. That is the whole act of generosity, and it takes about ninety seconds to send.
Now watch the three things that come back, because none of them is the one people expect.
The first is that they use it and it does not work the way it did for you, and they tell you so. They ran it on a technical document and the emotion dimension came back as noise, because nobody has a feeling about a network diagram. That is not them failing. That is your method being tested against a case you did not have, and the correct response is to change the dimensions for that kind of work, which you now know to do and would never have found alone.
The second is that they add something. They started putting the threshold at the top of the instruction rather than in their head, because they kept forgetting it. That is better than what you were doing. Take it.
And the third is the one that changes your position. Somebody they work with asks where they got it. Your method is now travelling without you in the room, attached to your name, doing work in a part of the building you have never been in. You did not do anything to make that happen and you could not have made it happen deliberately.
The version that fails, and I want to name it so you avoid it, is the one where you explain the whole system. You send four paragraphs of context about why checking matters, the person reads none of it, and nothing changes. Give one technique, on their own real task, with the actual words to type. Not a description of the words. The words.
Somebody who can copy and paste something in ninety seconds will try it. Somebody who has to understand your philosophy first will mean to try it, and will not.
The common failure here is not producing too little. It is producing a great deal and never asking whether any of it worked.
Charts, one-pagers, colour-coded tables, provenance markings · a year of them, and no record anywhere of whether a single one made a team decide faster, or better, or at all.
Volume is easy to count and impact is not, so people count the one that is easy and call it evidence. It is not evidence. It is activity.
The whole correction is one habit: when something you made visibly changed a decision, write down what it was. Three lines a month. In a year you will have the thing almost nobody has, which is a record of your own work landing.
Three passes, and the whole thing takes under five minutes.
Show it differently. Give me this as a table, with the decision in the left column. Read both versions and keep the one that a busy person could act on.
Mark your confidence. Go through the numbers and label them. Verified, estimated, unknown. Put the labels in the document. If a whole section is unverified, say so at the top of it.
Give the method to one person. Not the output. The instruction that produced it, and the check that caught something.
Do those three on your next piece of work and something will happen that has probably not happened to you before. Somebody will act on your work in the meeting rather than taking it away to think about.
That is the difference. Not being right more often. Being usable.
And once that starts happening regularly, once you're the person whose work gets acted on and whose method other people are using, you'll have a problem you've never had before.
---
### ▪ DO THIS > > Four passes on the next consequential thing you finish. > > 1. Show it differently. Give me this as a table, with the decision in the left column. Read both versions. Keep the one a busy person could act on. > > 2. Mark every number. Verified, estimated, unknown. Put the labels in the document, not in your head. > > 3. If a whole section is unverified, say so at the top of it. This is the step that feels wrong and is worth the most. > > 4. Give the method to one person. Not the output. The instruction you typed, and the check that caught something. > > Under five minutes if you noted your sources as you went. If you didn't, pass 2 is the work. Budget an hour the first time. > > When marking your own work unverified feels like weakness: it does the opposite. A document that admits which parts are soft makes its firm parts believable. One that presents everything with equal confidence tells the reader nothing about any of it, and careful readers discount all of it evenly. > > The signal to watch for: people acting on your work in the meeting rather than taking it away. Treat that as the sign it landed, and start keeping a record of when it happens.
---
You will have evidence. And you'll have to decide what to do with it, because nobody is going to walk up and offer you the conversation.