Skip to content

introvenk/clear-business-writing-skills / skills/improving-writing-culture

improving-writing-culture

Verified

Use when setting team writing standards, fixing a review process, or diagnosing why an organization's documents are consistently unclear.

Improving Writing Culture

Overview

Bad writing across a team usually has systemic causes. Diagnose the cause, then change one bounded thing and prove it worked. Source: Bernoff, Writing Without Bullshit, Epilogue plus the editing/review chapters.

Diagnose the cause

  • Lost editorial filters — nobody's job is to cut documents before they ship.
  • Fear — vagueness, hedging, and passive voice ("mistakes were made") are a rational response when directness gets punished. A team-wide pattern points at safety, not style.
  • Academic habits — people write to show effort and length, the way school rewarded them.

Change plan (in order)

  1. Spread the Iron Imperative. Treat the reader's time as more valuable than your own. Make that the shared standard for every doc.
  2. Recruit powerful friends, and bring them a plan. Find influential people who want better documents. Give them a concrete proposal, not a complaint.
  3. Limit scope; pick your battles. People who try to change everything change nothing. Start with one team or one document type (e.g. postmortems, status reports).
  4. Prove your worth with statistics. Measure before and after (time to read, rounds of review, questions asked, survey ratings) and report it.

Fix the review process

  • Manage reviewers. Decide up front who reviews, what each checks, and the deadline. Don't let the reviewer list grow by default.
  • Use an editor who stands in for the reader. Their job is to ask "what does the reader need?", not to add their own content.
  • Share one living document, not email attachments. Parallel copies multiply conflicting edits.
  • Feedback processes are broken. In Bernoff's survey, only about half of business writers got the editorial feedback they needed, and just 32% said their feedback process worked well (#254). Fix the process, not just the drafts.

Not from the book (useful extras)

  • Reward clarity in public: credit the postmortem that names a real cause over the one that spreads blame.
  • Leaders set the example. If leaders hedge bad news, their reports will too.

Protected writing time and focus conditions are advice for the human, not things an agent can enforce.

receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementationStars: 322kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 322kUpdated Claude CodeCodexVerifiedInstall
using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackStars: 322kUpdated Claude CodeCodexVerifiedInstall
verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysStars: 322kUpdated Claude CodeCodexVerifiedInstall