Every message at work is read by somebody deciding whether to do something, and they decide before the second line. Ivo schedules engineers for a firm that services commercial kitchens in Ljubljana, and he needs a purchase order raised before Thursday. His first attempt runs to 87 words and never says so.
Subject: Update on the Vodnik job. Following on from the site visit last month there have been a number of developments on the Vodnik job that I wanted to bring you up to speed on. The client has confirmed the extraction unit specification and the supplier has come back with revised pricing, which is broadly in line with what was budgeted, although there are some changes to the lead time. Given the situation with lead times over the summer it would be good to get things moving on this if at all possible.
Nothing in that is false and none of it is lazy. It fails because Petra in the finance office reads the subject line, sees a status report, and files it to read properly later, which is a category that does not exist. The subject line carries the ask and the date, not the topic. Here is the same message at 55 words.
Subject: Purchase order for the Vodnik extraction unit, needed by Thursday. Petra, please raise the purchase order for the Vodnik extraction unit, 4,180 euro, by Thursday. After Thursday the supplier's quote expires and the next slot in their build queue is March. The quote and the client's signed specification are attached. If anything is missing, tell me which and it will be with you today.
Four slots, and they are always in this order. The first line names the person, the thing, and the day. The second line says what happens if the day passes, which is the only part that makes a deadline other than a preference. Then whatever is needed to act, attached rather than described. And the last line makes the cheapest reply the useful one: Petra can now answer in four words, and the reply Ivo wants is more convenient for her than silence is.
The rule underneath the slots is a counting rule. One message, one ask, or the easier one gets answered. A note that asks Petra to raise the order and also to confirm the invoicing address for a different site gets the address, because answering the address takes eleven seconds and raising the order takes a form. Two asks is two messages, and the one that has to wait is the smaller one.
Listening is the half that changes what you write next
Petra writes back that finance cannot raise anything above 4,000 euro without a second signature and Ivo's first instinct is to explain the deadline again, harder. The move that works is older and duller: say the constraint back in their words before answering it. Naming the second signature out loud does two things at once. It proves the sentence was read, so Petra stops defending it, and it moves the conversation onto the real question, which is who signs and when they are next at a desk.
Most repeated arguments at work are two people restating a position because neither has heard the other say it back. The version of this that costs nothing is a single clause at the front of a reply, and the version that costs a week is the meeting called to resolve a disagreement that was never about the thing being disagreed over.
The stall is writing to sound competent
Here is where people stop, and it is nearly invisible because it looks like effort. Ivo's first attempt was written to demonstrate that the Vodnik job is under control. It leads with the site visit because that is where the work was, it hedges the pricing because that is honest, and it closes softly because a direct request from a scheduler to a finance office feels like an overstep. Every one of those instincts is about how Ivo appears, and none of them is about what Petra does next.
The tell is on the page and takes five seconds to find. Read your own draft and mark the word where the ask starts. If it is past the first line, the message was written to be read by somebody assessing you rather than by somebody acting. That is also why the fix feels rude for about a fortnight before it starts feeling like competence, and why nobody makes it without deciding to.
The order runs on undo, and the visible half comes last
The principle underneath the order is how much can be taken back. A draft can be fixed before anybody sees it, which makes the documents your job is actually judged on the cheapest place to learn the four slots, and it is where most of the job turns out to live anyway. Then the half of communication nobody trains, because it is the only one that changes what the message is about rather than how well it is put, and a clear message answering a question nobody asked is the more expensive of the two failures. Saying it clearly, out loud, to people is the same discipline with the undo taken away, manageable after the written version and brutal before it.
The three that need all of the above are the three people reach for first. A room, a screen, and fifteen minutes is where nearly everybody starts, and a deck built by somebody who cannot yet write a line naming a decision is a well made way of not deciding anything. Making them worth the hours they cost stands on that same line, because the line is the agenda. Changing what someone decides is the listening move under pressure, run on the objection rather than on the argument. And the situations that ruin otherwise good jobs comes last because it needs every one of the others and forgives none of them.
The order
The route nearly everybody takes, turns included
The way is not straight, and the doubling back is the content: each turn is where the thing learned last stopped being enough.
- 01Start at presentingIt looks like the skill and it is the one with a course
- 02Turn back to writingThe deck was fine. The page sent before it was not
- 03Turn back again, to listeningThe writing was clear and kept answering the wrong question
- 04Forward to meetingsNow the agenda line can be written, because the decision has a name
- 05Forward to persuasionThe objection goes first, in the other person's words
- 06Arrive at the difficult conversationThe reason for all of it, and last for a reason
The straight version of this route exists and almost nobody walks it. Reading the two turns as failures is the mistake.
What to open in 2026
Suggestion mode in Google Docs, or Track Changes in Word, is where a document that more than one person cares about should live. Both replaced the file emailed back and forth with a date in the filename, and the reason to care is not tidiness: a comment is attached to a sentence, so a disagreement stays next to the thing being disagreed with instead of arriving as a separate paragraph of feeling. Google Docs is free with an account and Word for the web is free with a Microsoft account.
A model that drafts is the change since 2023, and for this subject the useful direction is backwards. Paste your own draft and ask what is being requested and by when. If it cannot find the ask in one line, Petra will not either, and that is a mechanical answer to a question that used to need a patient colleague who was usually busy. It drafts a competent first version of anything, and every major assistant covers that on a free tier. What it will not do is decide the message should not be sent.
Meeting transcription is now automatic in Teams, Meet and Zoom, captions free in Meet and saved transcripts depending on the plan, and it replaced the person taking notes instead of taking part. It did not replace minutes, and treating it as though it had is the current version of an old mistake: nobody reads four thousand words of dialogue, so the decision and the owner still have to be written down by somebody who was listening.
Where this topic touches the others
This is the topic every other one is delivered through, which is why it is worth reading before the ones that look more senior. Getting work done through other people is entirely made of sentences like Ivo's, said out loud and with more at stake. The weekly note on delivering something by a date, with other people is the same four slots with a date in the second one. The volume problem, which is the one nobody's advice about clarity solves, belongs to getting your own work done, reliably, and for anybody doing all this in a second language the English that decides whether you get the role teaches the phrasing rather than assuming it. All of it sits under running work, getting paid, and the software it happens in.
There is a failure none of this touches, and it is the ordinary one: the message is right and no reply comes. Ivo's second attempt is a good message, and Petra has 90 unread and a second signature to chase; the ask went in on Tuesday and the build slot goes in March either way. Everything on this page improves the odds on one message and none of it makes a person answer. Whether that is even a communication problem is a page nobody has written.