executive-writing-style

name	executive-writing-style
description	Comprehensive executive writing craft for product briefs. Decision-maker framing, persuasive structure, so what? test, tone rules, filler phrase elimination, good/bad examples, anti-repetition rules, and markdown quality. Trigger keywords: executive summary, concise writing, plain language, active voice, so what, decision-maker, persuasive.

Executive Writing Style

Use this skill to produce concise, credible, decision-grade writing for time-poor leadership.

Decision-Maker Framing

Your reader has 5 minutes and 12 other documents to read today. Every sentence must earn its place.

Design rules:

• If a paragraph does not change the reader's understanding or decision, delete it
• The reader wants to know: what, why now, what it costs, what it returns, and what you need from them
• Respect the reader's time as the scarcest resource in the organization
• Write as if the reader will stop reading the moment you waste their time

Persuasive Structure

Lead with Impact

• Start each section with the single most important point
• Supporting evidence follows the lead, not precedes it
• Never open a section with background or context — open with the conclusion

State the Purpose Early, Reinforce Late

• Executive summary states the brief's purpose: the decision requested, recommendation, planned actions, input needed, or key findings
• The closing section reinforces with specifics appropriate to its type
• The reader should know what the brief is asking of them (or informing them about) within the first 30 seconds

Structure Each Section

1. Lead sentence: the key point or finding
2. Supporting evidence: 1–3 sentences backing the lead
3. Implication: what this means for the decision (if not obvious)

Do not reverse this order. Do not bury the lead.

The "So What?" Test

After writing any paragraph, ask: "If I deleted this, would the reader's decision change?"

• If yes: keep it
• If no: delete it, or merge the one useful sentence into an adjacent paragraph
• If maybe: tighten it to one sentence and keep only the decision-relevant part

Apply this test to every paragraph in the brief. No exceptions.

The Championing Test

After passing the "so what?" test, apply a second filter: "Could my reader use this to convince their boss in 30 seconds?"

The reader must re-pitch your proposal in a meeting where you are not present. If a section only makes sense to domain experts, it fails the championing test.

• If yes: the section is championing-ready
• If no: reframe the lead sentence around a business outcome (cost, revenue, risk, customer impact) and push technical detail into supporting sentences
• If partly: extract the core business outcome into one memorable statement, keep technical depth as backup

Championing Test Examples

Fails championing test (requires domain expertise to relay):

"The modular RBAC architecture decouples permission assignment from hard-coded role checks, enabling composable admin roles across tenant, capacity, and domain scopes."

Passes championing test (non-expert can confidently repeat):

"This lets customers define exactly what each admin type can do — eliminating 200 escalation tickets per month and unblocking enterprise deals that require granular permissions."

Both describe the same work. The second version gives the reader a sentence they can say aloud in their own leadership meeting.

Readability and Flow

Executive writing must be effortless to read. The reader should never re-read a sentence to understand it.

Sentence Craft

• Target 15–20 words per sentence. Hard ceiling: 25 words. If a sentence has a comma-separated clause, it probably needs splitting.
• One idea per sentence. If a sentence contains "and" connecting two distinct thoughts, make it two sentences.
• Subject-verb-object order. Avoid inverted or nested constructions. "The team will deliver Phase 1 in Q3" not "In Q3, the delivery of Phase 1 by the team is expected."
• Active voice by default. Passive voice is acceptable only when the actor is genuinely unknown or irrelevant.

Paragraph Craft

• One point per paragraph. If a paragraph argues two things, split it. The reader should be able to summarize each paragraph in one phrase.
• 3–4 sentences maximum per paragraph. Dense paragraphs lose readers. If you need more sentences, the paragraph is trying to do too much.
• Lead sentence carries the point. Every paragraph opens with its conclusion or key claim. Supporting evidence follows. Never open with background or context.

Word Choice

• Use the simplest accurate word. "Use" not "utilize." "Start" not "initiate." "Help" not "facilitate." "Enough" not "sufficient." "Buy" not "procure."
• Replace abstractions with specifics. Not "improves efficiency" but "reduces ticket volume by 60%." Not "enhances the experience" but "cuts admin setup time from 2 hours to 15 minutes."
• Cut nominalizations. "We decided" not "a decision was made." "We recommend" not "the recommendation is." Verbs are clearer than noun phrases.

Scannability

• A reader who reads only headings and the first sentence of each paragraph should understand the full argument.
• Use bullet lists for three or more parallel items instead of inline lists.
• Use tables when comparing options, metrics, or structured data.

Tone Rules

Confident and Direct

Write with authority. The reader hired experts to make recommendations, not to hedge.

• Do: "This will reduce admin errors by 40%"
• Don't: "This could potentially help reduce admin errors"

Honest About Uncertainty

Confidence does not mean false precision. When genuinely uncertain, state the range and the reason:

• Do: "We estimate 30–50% reduction based on the admin-roles review; the range reflects limited pilot data"
• Don't: "This might potentially reduce errors by some amount"

The combination of confidence and honest bounds is the hallmark of credible executive writing.

No Hedging Without Reason

Eliminate these words unless genuine uncertainty exists AND is explained:

• "might", "could potentially", "it is possible that"
• "may help", "should be able to", "we believe"

If uncertainty is real, state it directly: "We lack data on X; our estimate assumes Y."

Psychological Risk Reduction in Tone

Stakeholders face consequences you do not. They are measured on business outcomes and team perception. Your tone must make approving your proposal feel safe.

• Lead with outcomes the reader is measured on: cost reduction, revenue, customer satisfaction, risk mitigation
• Avoid language that requires the reader to become a domain expert to defend the proposal
• Frame recommendations so saying "yes" feels lower-risk than saying "no"
• Make the cost of inaction concrete and personal to the stakeholder's metrics

BAD (creates psychological risk — reader cannot defend this):

"The proposed solution implements a composable RBAC layer with inheritance semantics across container hierarchies."

GOOD (reduces psychological risk — reader can confidently approve):

"This gives enterprise customers the admin controls they've been requesting, reduces support tickets by 60-80%, and removes a blocker cited in three renewal negotiations."

Filler Phrase Blacklist

Delete these phrases on sight. They add zero information:

• "It is important to note that..."
• "It should be mentioned that..."
• "In today's rapidly evolving landscape..."
• "As we all know..."
• "It goes without saying..."
• "At the end of the day..."
• "Moving forward..."
• "In order to..."
• "The fact of the matter is..."
• "Needless to say..."
• "For all intents and purposes..."

If the sentence still makes sense without the phrase, the phrase was filler.

Buzzword Inflation

Say what you mean in plain language. Inflated language signals that the writer has nothing specific to say.

Inflated (avoid)	Plain (prefer)
"accelerated digital transformation enablement"	"faster"
"synergistic cross-functional alignment"	"teams working together"
"leverage our core competencies"	"use what we are good at"
"paradigm shift in operational excellence"	"a better process"
"holistic end-to-end solution"	"a complete solution"

AI-ism Cleanup

AI-generated prose carries recognizable verbal tics. The goal is not to hide that a document was drafted with AI — it is to make the text read the way a sharp human author would actually write it. Remove the noise that a careful writer would never have added. These tics are the single most common edit reviewers make by hand, so catch them before the draft ships.

What counts as an AI-ism

1. Inflated transition adverbs and connective filler. Drop or replace: "moreover," "furthermore," "additionally," "notably," "importantly," "crucially," "fundamentally," "ultimately," "essentially," "indeed." Most can be deleted outright; the sentence stands without them.

2. The "X isn't just Y, it's Z" construction. "This isn't just a feature, it's a platform." "It's not about speed, it's about trust." This antithesis template is the most recognizable AI tell. Rewrite as a direct claim: "This is a platform," or state both points plainly without the not-just scaffolding.

3. Rule-of-three padding. Reflexive triples where two items (or one) carry the meaning: "robust, scalable, and future-proof." Keep only the words that are true and load-bearing. Do not manufacture a third adjective for cadence.

4. Hedged significance claims. "plays a key role in," "serves as a critical component," "is a powerful tool for," "stands as a testament to," "underscores the importance of." Replace with the concrete thing it does.

5. Empty engagement scaffolding. "It's worth noting that," "It's important to understand that," "As we navigate," "In an era of," "When it comes to," "At its core." Delete the wrapper and keep the payload.

6. Symmetrical wrap-up sentences. Closings that restate the section in balanced clauses ("By combining X with Y, the team can achieve Z while ensuring W"). Cut them — the document is short enough that the reader remembers.

7. Over-signposting. "Let's explore," "In this section we will," "Having established X, we now turn to Y." Briefs are read, not narrated. Remove the tour-guide voice.

8. Promotional intensifiers. "seamless," "robust," "cutting-edge," "game-changing," "best-in-class," "unlock," "empower," "elevate," "harness," "leverage" (as a verb), "supercharge." Use a specific, literal verb or claim instead. (See also Buzzword Inflation above.)

9. Writer-scaffolding and meta-commentary (recognize the class)

The single unifying tell behind most AI-isms: a sentence that serves the writer's internal narration instead of the reader's need. It narrates the writing, labels or announces what a passage is about, or editorializes on why something matters or how it was designed — instead of stating the fact and letting it stand. This is what Joseph Williams (Style: Lessons in Clarity and Grace) calls metadiscourse: writing about your writing. Learn to recognize the category, not a fixed list of phrases; strip new variants the same way you strip classic AI-isms when a reviewer simply says "remove the AI-isms" with no samples.

Apply four questions to each sentence:

1. Reader-value or writer-narration? Does it inform the reader, or describe the surrounding text? If it talks about the writing, cut it and keep the payload.
2. Is it a content-label / announcement? Does it caption the point the next sentence already makes? Delete the label; keep the payload.
3. Is it significance/design meta-commentary? Does it assert that something matters / is important / is deliberate, instead of showing the concrete consequence? Replace with the outcome itself.
4. Is the contrast emphasis-only? Keep "X, not Y" only when the reader genuinely needs the rejected alternative to understand the claim (e.g. "this brief describes scope, not a specification"); cut it when the positive statement already stands alone.

If a sentence trips question 1, 2, 3, or 4, it is in the class — regardless of its exact wording. Generalize: new phrasings you have never seen still belong to the class when they trip these questions.

Illustrative, not exhaustive — recognize the class, do not grep for these strings: "What the customer gets:", "The publish step is deliberately simple.", "and that is the point", "This matters because…", "the value of this is…", "the benefit is…", "and this is explicit", "to be clear", "to be explicit", reflexive "explicitly / notably / clearly", "a different posture from…", and bare "X, not Y / rather than Y" used purely for emphasis.

Why these rules

These edits cite established plain-language authority, not personal taste — so the category (not the phrase list) is the durable rule:

• Strunk & White, The Elements of Style — "Omit needless words"; "Put statements in positive form" (the basis for cutting emphasis-only "not Y" contrast and significance meta-commentary).
• Orwell, Politics and the English Language — "If it is possible to cut a word out, always cut it out"; never let phrasing perform thoughtfulness in place of meaning.
• U.S. Federal Plain Language Guidelines (plainlanguage.gov) — write for the reader; cut words the reader does not need; do not announce what you are about to say.
• Williams, Style: Lessons in Clarity and Grace — cut metadiscourse (writing about your writing). This is the scholarly name for the writer-scaffolding class above and the strongest anchor for the general heuristic.

The naturalness test

Read each sentence aloud. Ask: "Would a busy human expert actually write this, or does it sound like it's performing thoughtfulness?" If it performs rather than informs, rewrite it as the plainest true version of the point. A human author writing fast and well produces asymmetric, specific, occasionally blunt sentences — not balanced, hedged, adjective-padded ones.

Before / after

AI-ism-laden:

"It's important to note that this isn't just an incremental improvement — it's a fundamental shift. By leveraging a robust, scalable, and seamless architecture, the team can unlock powerful new capabilities while ensuring long-term maintainability."

Cleaned:

"This replaces the architecture, not patches it. The new design removes the per-item permission checks that block enterprise rollout, and it reuses the existing OneLake identity model — so there is no new permission primitive to maintain."

The cleaned version is longer in commitment and shorter in adjectives. It says what changed and why it matters, with zero scaffolding.

Good vs. Bad Writing Examples

Example 1: Problem Description

BAD (template fill-in tone):

"The Problem Statement section describes the challenges faced by administrators in the current environment. It is important to note that the existing role-based access control system presents several significant pain points that impact operational efficiency and user satisfaction."

GOOD (executive memo tone):

"Administrators today have two choices: grant full access or grant none. This forces 340 active admins to either over-provision permissions — creating audit failures — or under-provision them, generating 200+ escalation tickets per month."

Why the good version works: it leads with the specific problem, gives concrete numbers, and shows the consequence. No filler, no abstraction.

Example 2: Confidence and Bounds

BAD (hedging without reason):

"This solution could potentially help address some of the challenges that administrators might face when managing permissions in the system."

GOOD (confident with honest bounds):

"This solution eliminates the binary permission model. Based on the February 2026 admin-roles review, we project a 60–80% reduction in escalation tickets within 90 days of rollout."

Why the good version works: it states what the solution does, cites the evidence source, gives a specific range, and sets a timeline. The reader can evaluate and decide.

Anti-Repetition Rules

Title, Summary, and Problem Are Three Different Things

• Title: names the product in one line
• Executive Summary: arcs the full story (problem → solution → impact → ask) in 3–5 sentences
• Problem Statement: deep-dives into the pain with evidence and specifics

These are not three versions of the same content. Each goes one level deeper.

Cross-Section Repetition

• If you wrote it in one section, do not write it again in another
• Brief forward or back references are acceptable: "As noted in the problem section..." (one sentence max)
• Restating the same content in different words is not acceptable
• No "in conclusion" or "to summarize" paragraphs within the body — the document is short enough that the reader remembers

Markdown Quality

Clean formatting reflects professional quality. Sloppy markdown signals sloppy thinking.

• Blank lines before and after every heading
• Consistent - list markers throughout
• No trailing whitespace
• Proper heading hierarchy (H1 → H2 → H3, no skipped levels)
• No inline HTML
• No multiple consecutive blank lines