Skip to content

Leadership & Communication · Meetings, writing and decisions · lesson 8 of 21 · 13 min

Writing that gets read and acted on

Busy readers skim

Most business messages are read quickly on a phone, between meetings. If the key point is buried in paragraph four, it may never be read. Clear writing respects the reader's time and gets the result you need.

Bottom line up front (BLUF)

Start with the conclusion, request or decision needed. Then provide supporting detail.

| Buried lead | BLUF | |---|---| | "Following our discussions last month about the warehouse project, and after reviewing several options with the team, considering costs and timelines, we believe that... [paragraph 3] ...so we need approval by Friday." | "Request: Please approve the extra 50,000 for the warehouse racking by Friday, so installation can start on schedule. Why: The original quote excluded seismic bracing required by the new code. Options considered: see below." |

The pyramid principle

Barbara Minto's pyramid principle structures documents with the main idea at the top, supported by a small number of key arguments, each supported by evidence. It mirrors how readers want to absorb information: answer first, then reasons.

Main point: We should launch in Saudi Arabia before the UAE.
  ├─ Reason 1: Larger addressable market for our product category
  │     └─ Evidence: market data, customer interviews
  ├─ Reason 2: Existing distribution partner ready in Riyadh
  │     └─ Evidence: signed letter of intent
  └─ Reason 3: Regulatory approval timeline is shorter for our category
        └─ Evidence: regulator guidance, adviser opinion

Techniques for clarity

  • One message per email where possible; use clear subject lines ("Decision needed by Fri: warehouse racking budget").
  • Short sentences and paragraphs. Aim for one idea per paragraph.
  • Plain language: "use" instead of "utilise"; avoid jargon or define it.
  • Active voice: "The team completed testing" rather than "Testing was completed".
  • Headings and bullets for scanning.
  • Specific numbers and dates: "by 14:00 Thursday" rather than "ASAP".
  • Make the ask explicit: what do you need, from whom, by when?

Editing checklist

[ ] Is the main point or request in the first two lines?
[ ] Would the subject line alone tell the reader what is needed?
[ ] Can any sentence be removed without losing meaning?
[ ] Are there words the reader might not know?
[ ] Are actions, owners and dates explicit?
[ ] Is the tone appropriate for the reader and the culture?
[ ] Have I checked names, numbers and attachments?

Tone and culture

Tone that seems efficient in one culture may seem abrupt in another. In many Gulf and South Asian business contexts, a courteous greeting and relationship-building line are expected before the business point; in many US contexts, brevity is valued. BLUF still works: a short courteous opening followed immediately by the key point. When in doubt, mirror the style of the person you are writing to.

Writing with AI assistants

AI tools can draft, shorten and polish messages quickly. Use them to produce a first draft or to simplify complex text, then check facts, tone and confidentiality. Do not paste sensitive information into tools your organisation has not approved, and remember that you are responsible for what you send.

Worked example

Illustrative. An analyst at a fictional bank in London sent a six-paragraph email about a data issue; the manager missed the request for approval at the end, and a regulatory report was delayed. After training, the analyst rewrote similar emails with a subject line "Approval needed today: correction to Q2 data submission", a two-line summary, and details below. Response times improved markedly.

Hands-on: BLUF template, before/after rewrite and an AI editing prompt

1. BLUF template for any message over five lines:

Subject: [Decision needed / FYI / Action] — topic — by [date]

Bottom line: [the one sentence the reader must take away, or the decision you need]
Why: [2–3 bullets with the key reasons or evidence]
What I need from you: [specific action] by [date/time]
Details (optional): [background, options considered, links]

2. Before and after (illustrative):

BEFORE: "Hi all, following on from last week's discussions and several conversations
with the vendor, I've been looking into the various options around the CRM renewal..."
(the ask appears in paragraph four)

AFTER:
Subject: Decision needed — CRM renewal — by Thursday 5 pm
Bottom line: I recommend renewing for 12 months, not 36, at the vendor's revised price.
Why: • Two alternatives are being evaluated by IT this quarter
     • The 36-month discount does not cover the switching risk
What I need: Approve or reject by Thursday 5 pm; silence = I'll escalate Friday.

3. AI editing prompt (edit your own draft; keep confidential data out of unapproved tools):

Edit this message for a busy senior reader. Put the bottom line first, cut it by
at least 30% without losing facts, use plain British English, keep my tone
[friendly/formal], and list any claims that need a source. Do not add facts.
[paste draft]

Then read the AI version aloud once. If it sounds like nobody you know, put your voice back in.

Common mistakes

  • Burying the request.
  • Long, dense paragraphs.
  • Several unrelated topics in one message.
  • Vague deadlines.
  • Reply-all to large groups for one-to-one matters.

Quick self-check

Take the last important email you sent. Rewrite its first two lines in BLUF format and compare. Would the reader have acted faster on the new version?

Writing for different formats

Chat messages should be even shorter: one point, one ask. Reports and proposals need an executive summary of no more than a page, followed by sections that each answer one question. Slides should carry headlines, not paragraphs. Whatever the format, apply the same test: can the reader find the main point and the required action within seconds?

Video lecture: Writing that gets read and acted on

Lecture coming soon · 13 chapters · about 8 minutes. Read the full transcript below.

  1. Clear writing
  2. Why it matters
  3. BLUF and the pyramid
  4. The newspaper test
  5. Clarity techniques
  6. Worked example 1: Mehwish (illustrative)
  7. Worked example 2: Rashid in Dubai (illustrative)
  8. Tone and culture
  9. Different formats
  10. Watch me: BLUF rewrite + AI edit
  11. Measuring success
  12. Common mistakes
  13. Recap and try this now

Lecture transcript

Clear writing

Here's an uncomfortable truth. Most of the people who receive your emails, chat messages and documents won't read them fully. They'll skim the first line or two, decide whether it matters, and move on. If your key point is in paragraph four, it may as well not exist. In this lecture you'll learn how to write for skimmers: bottom line up front, the pyramid principle, practical techniques for clarity, how tone shifts across cultures, and how to use AI assistants to edit without losing your voice. By the end, you'll rewrite one real message.

Why it matters

Why does this matter? Because most work now happens in writing. Email, chat, tickets, documents and proposals. Remote and hybrid teams depend on it even more. Unclear writing costs time: follow-up questions, misunderstandings, and decisions made on the wrong assumption. Clear writing is also a signal of clear thinking. Senior people notice who can explain a complex issue in a few lines. That's often who gets trusted with the next big piece of work.

BLUF and the pyramid

Here's the concept. BLUF, bottom line up front, comes from military writing. Put the conclusion, recommendation or request first, then the supporting reasons, then the detail. The pyramid principle, developed by Barbara Minto, formalises this: start with the main point, group supporting arguments beneath it, and support each with evidence. Here's the key idea. Write in the order the reader needs, not the order you discovered things. Your discovery journey is interesting to you. Your reader wants the destination.

The newspaper test

Here's an analogy. Think of a newspaper story. The headline tells you what happened. The first paragraph tells you who, what, where and when. Each later paragraph adds detail you can skip if you're busy. Editors call it the inverted pyramid, and it's designed for readers who might stop at any moment. Your emails should work the same way. If your reader stops after the subject line, do they know what you need? After the first sentence, do they know the answer?

Clarity techniques

Now some techniques for clarity. Use a subject line that says what kind of message this is and when a response is needed, like decision needed, CRM renewal, by Thursday. Keep sentences short, and use one idea per paragraph. Prefer plain words: use rather than utilise, help rather than facilitate. Use the active voice: the team missed the deadline, rather than the deadline was missed. Use bullets for lists, and bold sparingly for the one thing people mustn't miss. And make the ask specific: what you need, from whom, by when.

Worked example 1: Mehwish (illustrative)

A simple worked example. Mehwish, a project coordinator in Karachi, needs her manager to approve an extra freelancer. Her first draft begins: Hi, hope you're well. As you know, we've been having a busy few weeks, and there have been a few challenges. The ask is at the bottom. She rewrites it. Subject: approval needed, one extra freelancer, by Wednesday. First line: I'd like approval to hire one freelancer for three weeks at the agreed day rate to keep the client launch on time. Then three bullets of reasons. Her manager approves it in four minutes.

Worked example 2: Rashid in Dubai (illustrative)

Now a realistic business scenario, illustrative. At a consumer goods company in Dubai, the regional marketing lead, Rashid, sends a monthly performance report to the country managers. It's twelve pages. Almost nobody replies, and the same questions keep coming up in meetings. He restructures it. Page one is a BLUF summary: three things that changed, one decision needed from each country, and a traffic-light table. The detail moves to an appendix. Replies go from almost none to most of the country managers within a week, and the monthly meeting drops by thirty minutes.

Tone and culture

Tone and culture matter too. In some workplaces, especially in parts of South Asia and the Gulf, a warmer opening and more courtesy are expected, and a message that starts with the ask can feel abrupt. In many UK and US workplaces, brevity is read as respect. You don't have to choose between clarity and courtesy. A one-line greeting followed by the bottom line works almost everywhere. Also consider readers working in a second language: shorter sentences, fewer idioms, and no sarcasm, which rarely survives in writing.

Different formats

Different formats need different shapes. In chat, lead with the point in one message rather than five fragments, and never send just hi, then wait for a reply. Say what you need in the first message. In email, the subject line does half the work. In a document or proposal, add a short executive summary at the top, headings that say something, like costs rise in quarter three, rather than costs, and an appendix for the detail. And for anything sensitive or emotional, writing is usually the wrong format altogether. Pick up the phone or book a call, then confirm in writing.

Watch me: BLUF rewrite + AI edit

Watch me do it. I take an illustrative draft about a CRM renewal where the ask sits in paragraph four. First, I write the bottom line: I recommend renewing for twelve months, not thirty-six. Then three reasons. Then the ask: approve or reject by Thursday at five. I paste the draft into an AI assistant with the editing prompt from the lesson: bottom line first, cut by thirty per cent, plain British English, no new facts. It shortens it well, but it adds a claim about pricing I never made. I delete that line. Then I read it aloud and put back one phrase that sounds like me.

Measuring success

How do you measure clear writing? Look at the responses. Fewer follow-up questions. Faster replies to decision requests. Decisions made on the first round, not the third. You can also test yourself before sending: could someone who reads only the subject and first sentence act correctly? And every so often, ask a trusted colleague to read one of your messages and tell you, in one sentence, what you're asking for. If their sentence doesn't match yours, rewrite.

Common mistakes

Common mistakes. Burying the ask. Vague subject lines like quick question or update. Long paragraphs covering five topics. Jargon and acronyms the reader doesn't know. Passive voice that hides who's responsible. Writing in anger and sending immediately. Copying the whole company when three people need it. And pasting AI-generated text without checking it, which can add facts you never said and a voice that sounds like nobody.

Recap and try this now

Let's recap. Readers skim, so put the bottom line up front. Structure with the pyramid: main point, reasons, evidence. Use clear subject lines, short sentences, plain words, active voice and a specific ask. Adapt warmth to culture but keep the bottom line clear. Use AI to edit, then check facts and put your voice back. Your try this now: take one message you need to send today, rewrite it with the BLUF template in the lesson, and notice how quickly you get a response. Next, we'll look at how groups make better decisions.

Key takeaways

  • Put the conclusion, request or decision first (BLUF).
  • Structure longer documents with the pyramid principle: main point, key reasons, evidence.
  • Use short paragraphs, plain language, active voice, headings and explicit asks with dates.
  • Adapt tone to culture; use AI drafts responsibly and check facts and confidentiality.

Try it

Rewrite three recent emails or messages using BLUF and the editing checklist. Ask a colleague which versions they would prefer to receive.