Business Writing For Leaders

Read runtime and advisory rules before applying this skill. Other Foreman layers and the catalog are in ../../content/, relative to this SKILL.md.

Business Writing for Leaders

DELETE KEY. The most powerful writing tool a leader possesses is subtraction. Every unnecessary word dilutes authority. Every jargon-laden sentence signals that the writer is performing competence rather than demonstrating it. Every buried lead -- the critical information hidden in paragraph three -- is a tax on the reader's time and goodwill. Yet leaders write more words each year, to more people, through more channels, with less editing and less consideration for the person on the receiving end. The average executive sends and receives over 120 emails per day. The ones that get read, understood, and acted upon share a common trait: their authors wrote for the reader, not for themselves.

Researchers and practitioners writing across a decade of HBR publications converge on a conclusion that should embarrass anyone who has ever used the phrase "synergistic value proposition" in an email: good business writing is simple, clear, human, and structured around what the reader needs to know, not what the writer wants to say.

The Framework

Leadership writing rests on four principles. They are deceptively simple. Executing all four simultaneously, under time pressure, with multiple audiences, is considerably harder than any writing guide admits.

Principle 1: Write for the Reader

The discipline begins with a shift in orientation. Before writing a sentence, answer three questions:

• What does the reader need to know? Not what you want to tell them. What they need.
• What questions will they have? Anticipate and address them in order of likely importance.
• How much time will they give this? Assume less than you hope. Probably less than you think.

Respect for the reader's time is not a courtesy; it is a structural requirement. Put the most important information first. The reader who stops after the first paragraph should still have the essential message. The reader who continues should find supporting detail, not repetition.

Picture your audience as intelligent novices: smart, capable of grasping complex ideas, but not fluent in your department's acronyms, your industry's jargon, or your project's internal shorthand. Define technical terms on first use. Avoid abbreviations unless they are universally understood. The test is whether someone outside your team would understand every sentence without a glossary.

Principle 2: Lead with Clarity

Three structural practices separate clear writing from unclear writing:

Get to the point. Lead with your core idea. Provide context to support it. Cut everything else. The common failure is inversion: context first, supporting detail second, the actual point last. By the time the reader reaches it, attention has dissipated.

Use topic sentences that forecast. The first sentence of each paragraph should tell the reader what the paragraph is about -- not merely describe a detail. Compare: "I met with the client in Berlin" (descriptive, no signal) versus "My meeting with the Berlin client focused on plans for future growth" (forecasting, contextual). The second sentence earns the reader's continued attention by promising relevance.

Use active voice. "Juan improved the project's results" is clear. "The project's results were improved" is evasive -- it hides agency, removes accountability, and requires more words to say less. Passive voice has legitimate uses (when the actor is unknown or deliberately unimportant), but it should be a conscious choice, not a default.

Principle 3: Keep It Simple

Overblown language does not signal intelligence. It signals insecurity. The writer who uses "leverage" when they mean "use," "ideate" when they mean "think," or "robust solution" when they mean "good answer" is not communicating -- they are decorating.

Practical simplification:

• Use short, familiar words. "Begin" rather than "commence." "End" rather than "terminate." "Use" rather than "utilise."
• Use short sentences. If a sentence contains more than one idea, it should probably be two sentences.
• Use short paragraphs. A paragraph crammed with four ideas forces the reader to parse structure and content simultaneously. One idea per paragraph. Two at most.
• Use formatting as a tool. Headings, bullet points, bold text, and numbered lists allow readers to scan for relevance. Most business writing will be read on a phone, possibly while the reader is walking, eating, or sitting in another meeting. Write for that reality, not for the undivided attention you wish you had.

Principle 4: Sound Human

The gap between how leaders write and how leaders speak is, in most organisations, unnecessarily wide. Written communication that sounds like it was produced by a committee -- or by a language model prompted to "sound professional" -- creates distance where connection is needed.

Three practices:

• Use first person. "I recommend" and "We accomplished" are personal and direct. "The company achieved" and "It has been determined" are bureaucratic and evasive. Readers trust people. They distrust institutions that refuse to identify a human behind the words.
• Start sentences with verbs and conjunctions. "Get the report to me by Friday." "But that approach has a flaw." "And here is why it matters." These constructions mirror natural speech patterns and create momentum. They are grammatically correct despite what certain style guides claim.
• Read aloud. The most reliable test of whether writing sounds human: say it out loud. If a sentence sounds awkward spoken, it will sound awkward read. If a phrase would never leave your mouth in conversation, it should not appear in your writing.

Prompts

Prompt 1 -- Writing Audit:

Here is a piece of business writing I recently sent: [paste the full text]. Audit it against four principles: reader orientation, clarity of structure, simplicity of language, and human voice. For each principle, score it on a 5-point scale and provide specific examples of where it succeeds and fails. Then rewrite the weakest sections.

Prompt 2 -- Email Rewrite:

I need to send this email: [describe the situation, the audience, and the key message]. Draft it in under 150 words, leading with the core message, using active voice, avoiding jargon, and sounding like a human wrote it. Then provide a version for a different audience: [describe the second audience].

Prompt 3 -- Announcement Draft:

I need to announce [describe the news -- positive or negative] to [describe the audience]. The key facts are: [list]. The likely questions are: [list]. Draft an announcement that leads with the most important information, anticipates reader questions, uses simple language, and maintains an honest, human tone. Keep it under 250 words.

Prompt 4 -- Jargon Elimination:

Here is a document filled with jargon and corporate language: [paste text]. Rewrite every sentence using the simplest possible language without losing meaning. Flag any instances where jargon was actually doing useful work (i.e., a technical term that has no simpler equivalent) and keep those.

Use Cases

Validation-Stage Founder Writing an Investor Update A founder sends monthly investor updates that consistently go unread. An audit reveals the problem: updates open with three paragraphs of context before reaching the key metrics. Investors, who receive dozens of portfolio updates per month, stop reading after paragraph one. The rewrite leads with a three-line summary (revenue, burn, key milestone), follows with a five-bullet section on progress and challenges, and closes with a specific ask. Open rates double. Response rates triple. The content did not change -- the structure did.

Growth-Stage VP Sending a Restructuring Email A VP of Operations needs to announce a team restructuring that will affect 40 people. The first draft, reviewed against the four principles, is 800 words, opens with corporate preamble ("As we continue to evolve our organisational capabilities..."), buries the actual changes in paragraph four, and uses passive voice throughout ("roles will be affected" -- by whom?). The rewrite opens with the change ("Effective March 1, Teams A and B will merge under [Name]"), explains the reasoning in two sentences, details what this means for each person's role in a bulleted list, and closes with a specific invitation: "I will hold office hours on Thursday and Friday to answer your questions directly." Active voice. Human tone. Half the length.

Anti-Patterns

1. Writing to Impress, Not to Communicate. The leader who uses complex vocabulary and elaborate sentence structures to signal intelligence. The reader does not conclude "this person is brilliant." The reader concludes "this person made me work harder than necessary to understand a simple point." Sophistication in writing is the ability to make complex ideas simple, not simple ideas complex.

2. The Reply-All Essay. Responding to a two-line question with a 500-word treatise. Match the length and formality of your response to the communication that prompted it. Escalating register signals that you are performing, not communicating.

3. Editing by Addition. Reviewing a draft and making it longer. In nearly every case, the most productive edit is deletion. Remove the sentence that repeats the previous one. Remove the paragraph that qualifies a point the reader did not need qualified. Remove the adjective that adds nothing.

4. Template Dependence. Using the same format for every communication regardless of audience, context, or message. A team update, an investor email, and a disciplinary notice require different structures, different tones, and different lengths. Templates are a starting point, not a destination.

5. Delegating Voice. Having someone else write communications that carry the leader's name without reviewing them for tone and voice. Readers develop a model of who the leader is through their writing. Inconsistency between spoken and written voice -- or between one email and the next -- erodes trust.

By Stage

Output Template

markdownCopy code
# Communication Draft: [Subject]

## Pre-Writing Check
- Reader: [who will read this]
- Reader's primary question: [what they need to know]
- Reader's available attention: [how much time they will give this]
- Required action: [what the reader should do after reading]

## Draft
[The communication, structured with the core message first, supporting detail second, and a clear call to action]

## Self-Audit
- [ ] Core message in the first two sentences
- [ ] Active voice throughout (passive voice used only deliberately)
- [ ] No unexplained jargon or acronyms
- [ ] Every paragraph begins with a topic sentence
- [ ] Read aloud -- sounds human
- [ ] Length appropriate to the audience and channel

Related Skills

• Writing with Purpose -- Defines the foundational technique for determining what to say and why before drafting, which directly supports the leader's principle of writing for the reader.
• Clarity and Concision -- Provides the sentence-level editing techniques that operationalise Principle 3's mandate to keep it simple and cut unnecessary words.
• Tone and Engagement -- Addresses the tonal calibration that makes Principle 4 actionable: sounding human without losing authority across different audiences.
• Persuasion and Influence -- Writing is a persuasion medium; the principles of reading the room and establishing authority organically apply in written form as much as in spoken interaction.
• Psychological Safety in Practice -- How leaders write about mistakes, setbacks, and difficult news directly affects whether team members feel safe to surface problems.
• Storytelling for Leaders -- Narrative techniques transform announcements and updates from information dumps into compelling communications that land with readers.