The one idea
Write for the reader's decision, not for your own effort.
You know the whole story. You lived it. So you naturally write it in the order you experienced it: context, then complication, then what you concluded, then what you want.
Your reader does not want the story. They want to know one thing: what does this mean for me, and what do I have to do? Every sentence before that answer is a toll they pay.
So put the answer first. Then explain. Anyone who needs the reasoning will read on. Anyone who does not can act immediately — and that is the whole point.
Say what you want in the first line. Explain afterwards.
Bottom line up front. Subject line states the ask. First sentence states the action and the deadline. Background goes below, where it can be skipped.
Plain-language guidance calls this "the most important information first" — an inverted pyramid. It optimises for a reader who stops reading at an unknown point, which is the realistic model of a working inbox.
The mental model
Before you write anything, answer four questions. If you cannot, you are not ready to write — you are still thinking, and the message will show it.
| Question | If you skip it |
|---|---|
| Who decides or acts? | You send it to five people and nobody owns it |
| What exactly must they do? | They reply "noted" and do nothing |
| By when? | It slides until it is urgent |
| What happens if they don't? | They deprioritise it correctly, because you gave them no reason not to |
That last one is the one people leave out. "Please approve by Friday" is weaker than "Please approve by Friday — after that the vendor's quote expires and we re-tender." The second is not more aggressive. It is more useful.
Cutting words that carry no information
Some words do real work. Others are throat-clearing — noise you make while warming up to the point. Cut them and nothing is lost.
| Cut this | Because |
|---|---|
| "I hope this email finds you well" | It carries no information and everyone skips it |
| "I was just wondering if you could possibly" | Four hedges around a normal request |
| "As per our discussion" / "Please do the needful" | Says nothing about which discussion or which need |
| "Kindly revert" | Means "reply". Say reply |
| "At the earliest" | Not a deadline. Give a date |
| "It has come to my notice that" | You noticed. Say the thing |
| "In order to" | "To" |
| "Due to the fact that" | "Because" |
There is a real fear underneath the padding: that being direct sounds rude. It does not. Padding does not make you polite — a clear request plus "thanks" is polite, and takes eight seconds to read instead of forty.
Before and after
Before (127 words):
Dear Sir,
I hope this email finds you in the best of health. I wanted to bring to your kind notice regarding the vendor issue which we had discussed in last week's meeting. As you are aware, the vendor had committed to delivering the units by the 20th, however due to certain unforeseen circumstances at their end, the same has been delayed. In this regard, it would be helpful if we could possibly look into extending the purchase order validity, as otherwise there may be some issues going forward. Kindly do the needful at your earliest convenience.
Thanking you, Ravi
After (61 words):
Subject: Approval needed by Thu 4pm — extend PO 4471 to 15 Oct
Hi Meera,
I need your approval to extend PO 4471 by three weeks, to 15 October. Can you approve by Thursday 4pm?
The vendor has slipped delivery from 20 September to 8 October. Their quote expires Friday; if we miss it we have to re-tender, which adds about a month.
Happy to walk through it if easier.
Ravi
Nothing was lost. The subject line alone now tells Meera what she must do and when — which means she can act from her phone, in a lift, without opening anything.
Before:
Hi team, just wanted to check in on the status of the report and see if there's anything pending from my side or if anyone needs anything, please let me know, thanks!
Nobody replies to this, because nobody was asked anything. "The team" is not a person and "anything pending" is not a question.
After:
Hi Anjali — two things before I close the draft:
- Can you confirm the Q3 headcount figure is 214? I have two versions.
- Do you want the regional split in the appendix or the main body?
If I don't hear by tomorrow noon I'll use 214 and put the split in the appendix, and we can adjust later.
Thanks!
One named person. Two answerable questions. And a default, so silence still produces progress instead of a stall.
That last trick — state what you will do if they do not reply — is worth more than any other line in this lesson. It converts a blocked task into a moving one, and it is completely non-confrontational.
The procedure
Turning a draft into something that gets acted on
1 of 7Write the messy version first. Get it all out, badly, in whatever order it comes. Do not edit while drafting. You are only finding out what you think.
Try this
Rewrite this so the reader can act from the first two lines. Aim for under 70 words.
Hello Sir/Madam, Greetings for the day. This is with reference to the training session which was scheduled. I would like to inform you that I had tried reaching out to the concerned team multiple times but there was no response received from their end. Since the participants are waiting and the hall booking is also there, it would be great if some clarity can be provided regarding the same at the earliest so that we can proceed accordingly.
Your challenge
Level 3 · IndependentFind a message you actually sent in the last two weeks that got no reply, or got a reply asking what you meant.
Rewrite it under these rules, and count words before and after:
- The subject line names the action and the deadline.
- The first sentence contains the ask and the date.
- One named owner per action item.
- A stated consequence or a stated default if nobody responds.
- At least 30% shorter.
You have succeeded when you can hand the rewrite to someone who knows nothing about the situation and they can tell you, in five seconds, who has to do what by when.
What people usually get wrong
- Burying the ask under the background. You explain first because you feel you must justify yourself. The reader reads top-down and gives up before the point.
- "ASAP", "at the earliest", "urgently". These are feelings, not deadlines. Everyone's ASAP is different, so nothing is scheduled.
- Writing to a group. Diffusion of responsibility is real: address five people and each assumes another will handle it.
- Asking three questions in one paragraph. You will get an answer to one. Number them on separate lines.
- Formality as a substitute for clarity. "Kindly do the needful at the earliest" sounds respectful and communicates nothing. It forces the reader to reconstruct your request.
- Apologising for writing. "Sorry to bother you" primes the reader to treat your message as a bother.
- Editing while drafting. You end up polishing sentences you were going to delete.
How someone experienced does it
Experienced writers decide the reply they want before they write a word. Not the topic — the literal reply. "Approved." "Yes, Thursday works." "Use 214." Then they write the shortest message that makes that exact reply easy to type. It is a startling constraint, and it eliminates most bad drafts before they exist.
They also write for the forward. Any message worth sending will be forwarded to someone with no context, usually with no explanation attached. So the message has to survive alone: names spelled out, no unexplained "as discussed", no pronouns pointing at things only you and the recipient remember.
And they know the tell for a message that should not be an email at all. If you have rewritten it three times and it still feels wrong, the content is usually something that needs a conversation — a disagreement, bad news, or anything where tone will be misread. The right move then is not a better paragraph. It is a ten-minute call, followed by a short email confirming what you agreed.
When not to use this
Bottom-line-first is wrong in a few real situations:
- Genuinely bad news to one person. Leading with "your project is cancelled" in line one is accurate and cruel. One sentence of context first, then the news plainly. Still no burying it in paragraph four.
- Persuading someone who currently disagrees. If your conclusion is one they will reject on sight, they will stop reading at line one. Lead with the shared problem, then the conclusion. This is a narrow exception — most people invoke it far too often.
- A first approach to someone senior outside your organisation. A line establishing who you are and why you are writing earns the right to the ask. One line, not a paragraph.
Why 'plain' writing is not 'dumbed down'
Plain language guidance is often misread as "use small words". It is not about vocabulary. It is about structure and reader effort.
The specific mechanisms it targets: information ordered by the writer's process instead of the reader's need; long sentences that hold several ideas in suspension; passive constructions that hide who must act ("the form should be submitted" — by whom?); and abstract nouns standing in for verbs ("perform an assessment of" rather than "assess").
A technical reader benefits from this as much as a lay reader. Precision is untouched — you can still write "the RBI circular of 6 April requires payment data to be stored in India". What goes is the effort of extracting the meaning.
Prove it
Keep a "before and after" pair. Your original message, and your rewrite.
Then do one more thing: send the rewrite for real, and note how long the reply took compared with your usual. That number is the only evidence that matters, and once you have seen it once you will not go back.
Keep learning this
Paste this into any AI assistant. It turns the assistant into a tutor that tests you instead of just answering you.
Act as an experienced practitioner who is good at teaching. I have just learned rewriting a work message so the ask and deadline come first. Assume I am intelligent but relatively new to this — treat me as beginner level. Work through this in order, and wait for my reply at each step: 1. Ask me 5 questions that test whether I actually understood rewriting a work message so the ask and deadline come first. Do not reveal the answers yet. 2. After I answer, tell me which parts I got right, which I got wrong, and which I only half-understand. Explain only what I misunderstood — do not re-teach what I already know. 3. Give me one practical challenge based on something I could genuinely encounter at work or in daily life. Do not solve it for me. 4. Evaluate my solution the way an experienced person would judge it, including what a professional would have done differently. 5. Tell me what to learn next, and why that comes next. 6. Give me trustworthy sources for deeper study — prefer official documentation, primary research or standards bodies over blogs and videos. Rules for you: no buzzwords. No motivational filler. Say "I'm not certain" when you are not certain, and tell me which parts of your answer I should verify myself. Clearly separate facts from your recommendations and your opinions.
Become independent at this
Use this when you want a path from where you are to actually good, with checkpoints you can test yourself against.
I want to become independently capable at writing messages that get acted on — not permanently dependent on AI, tutorials or step-by-step guides. Design a progression for me with five stages: Beginner, Guided practice, Independent practice, Real-world application, Professional level. For each stage tell me: - what I must know - what I must be able to do without help - the mistakes people make at this stage - one practical challenge - one real project that would prove I reached this stage - one way I can test myself honestly Then tell me the signals that I am ready to move to the next stage, and the signals that I have skipped ahead too early. Keep the theory to the minimum I actually need. Focus on ability I can transfer to situations you and I have not discussed.