Library
Smart Brevity: The Power of Saying More with Less · 4 of 13
Smart Brevity: The Power of Saying More with Less
business CRITICAL

Implementation Playbook

Smart Brevity: The Power of Saying More with Less Jim VandeHei, Mike Allen, Roy Schwartz
workflow smart-brevity-score ABCH pre-writing editing axioms axios-hq

Key Principle

Smart Brevity is not a style preference — it is a timed, repeatable workflow built on four guiding principles: Authority (be the expert, or find one), Brevity (stay short, not shallow), Clarity (style text for impact), and Humanity (write like you speak). The workflow converts those principles into five sequential steps with strict time limits designed to train intuition, not just compliance. A final ACH review (Accurate, Cohesive, Human) catches what brevity pressure predictably erodes. The framework applies to most written communication — emails, newsletters, internal memos, presentations — and scales from individual discipline to organizational norm through tools like Axios HQ. (Chapter 2, 3, 5, 10, 11)

Why This Matters

Without a forcing function, most writers use the act of writing to discover what they mean — externalizing confusion rather than resolving it. The reader receives the confusion. Pre-writing clarity is the ceiling of reader clarity: if the writer cannot name the single takeaway before writing, the reader has zero chance of understanding it. This is a hard ceiling, not a soft correlation. Every downstream technique (cutting words, rewriting ledes) works only after this precondition is met.

At the organizational level, communication dysfunction compounds at scale. Inconsistent formatting, bloated updates, and low engagement erode team alignment. GRAIL's ad-hoc internal emails were opened by fewer than one-third of recipients (~33% open rate). After replacing them with a structured Smart Brevity newsletter, open rates rose to ~90%. The 3x improvement required no change in headcount or budget — only format, cadence, and brevity. Individual Smart Brevity practice is a prerequisite; organizational adoption is the actual goal.

Good Examples

Pre-Writing Sequence (5 steps): Before typing a single word — (1) name one target reader; (2) name one takeaway; (3) say it conversationally, out loud; (4) draft it in under 12 words, declarative, jargon-free; (5) stop when done. The hardest step is 5. Stopping feels like leaving value on the table; it is the opposite.

The Timed Workflow in action: A Step 3 "before/after" from the book — Weak: "We continue to closely monitor the impact of COVID, and we are writing today to provide an update on our plans for the rest of the year." Strong: "Everyone will have the option—but not the requirement—to work from home for the rest of 2021." The strong version adds distinct new information; it does not restate the headline.

Axios HQ's Living History feature: Every Smart Brevity update is automatically stored as a retrievable record. New team members can reconstruct organizational history through the archive — faster onboarding, shared language, institutional continuity. Internal newsletters are not just one-time broadcasts; they are durable knowledge artifacts.

Counterpoints

Smart Jazz without mastery: Intentional deviation from the Core 4 structure is valid only after the formula is fully internalized. Invoking "Smart Jazz" as cover for laziness — skipping the tease, padding the lede, omitting "Why it matters" — is the primary failure mode. Jazz without music theory is noise.

Brevity without humanity: Brevity pressure accumulates through editing; personality is the most easily sacrificed element. The ACH checklist's HUMAN step exists precisely because brevity is the active force and humanity is what gets eroded by it. "If your communication feels curt or overly cut, you've gone too far."

Expertise buries the lead — systematically: Subject-matter experts bury leads not out of bad writing but because comprehensive context feels like professional obligation. The fix is the "Ask the Author" technique: ask the report writer directly what's the most interesting thing about this. Their verbal answer is almost always the lede their written version suppressed. Conversation bypasses the completeness reflex that formal writing triggers.

Key Quotes

"Think of Smart Brevity as a straitjacket on your worst instincts or habits in communication. It's a way to clean up and frame your thinking — then deliver it with punch." — VandeHei, Allen & Schwartz, Chapter 2

"Smart Brevity is music theory — it gives you logic and elegance. But that magnificent architecture leaves room for . . . jazz." — VandeHei, Allen & Schwartz, Chapter 3

"Smart Brevity is empowering. If you follow this book's precepts—starting with the importance of honing your idea before you begin typing—you'll be able to communicate with authority and impact." — VandeHei, Allen & Schwartz, Chapter 11

"They don't have spare time to search for information to remain connected to the company's broader priorities and culture—they need information delivered succinctly and predictably." — VandeHei, Allen & Schwartz, Chapter 10

Rules of Thumb

  • Name your one target reader and your one takeaway before opening a blank document.
  • Speak the message aloud before writing it — spoken conversation activates social feedback loops that writing removes.
  • Write headlines in 6 words or fewer, with clear, specific, conversational words; check on a mobile screen for truncation.
  • The opening sentence must add distinct new information — not restate the headline. This is the most commonly violated rule.
  • Bold "Why it matters:" immediately after the opening sentence; write one sentence explaining significance as bluntly as possible.
  • Use custom Axioms (not just "Why it matters") to make the format feel owned: "The bottom line:", "By the numbers:", "What's next:".
  • Apply the final ACH check in order — Accurate (verify no detail was lost), Cohesive (restore any transitional phrases), Human (restore voice and personality last, as this is the most important step).
  • Use Analytics (open rates, timing data) to close the feedback loop writing alone cannot close.
  • Give new team members months of back-issues as onboarding — the archive is institutional memory, not just a broadcast history.

Related References