On Writing
Leaders & Managers
DropRegion · Lessons from On Writing · Stephen King

What Leaders and Managers Can Learn from On Writing

Marcus reread the performance review he'd drafted for a struggling report and winced. Three paragraphs in, he still hadn't said the actual problem: missed deadlines were hurting the team. Instead he'd written about "opportunities for growth" and "areas of alignment," phrases that let him avoid the uncomfortable part while feeling like he'd done his job. He imagined his report reading this and understanding nothing actionable. So he deleted it and started again: "You've missed three deadlines this quarter. Here's what needs to change, and here's how I'll support it." It felt blunter than he was used to writing. It also felt, for the first time, like something the person could actually act on.

01 · The Book in One Minute

The whole book, compressed

01Strip Your Emails And Feedback
02Protect A Consistent Block
03Read Your Team's And Peers'
04Your Own Hard Experiences As

This edition works through 4 core lessons — take them one at a time, not all at once.

02 · Where Are You Now?

What's different for your conditions

Tap whichever ones sound like you. Nothing here is sent or saved — it's just for your own noticing.

Your writing carries authority, so vague or hedged language doesn't just confuse people — it leaves them guessing what you actually want.
Much of your writing (reviews, feedback, difficult emails) is written under time pressure and social discomfort, which pushes you toward softening language that obscures the point.
You write far more often reactively — replying to a crisis, an escalation, an urgent request — than by choice, so protected writing time competes directly with your calendar.
Your team reads your emails and documents as models of how to communicate, whether you intend that or not.
You rarely get direct feedback on your own writing once you're in a leadership role, so bad habits compound unchecked for years, and the same email often has to satisfy several audiences at once — your team, your peers, your own manager — which tempts you toward a blurry middle ground that serves none of them well.

0 of 5 selected

03 · Core Lessons

The core lessons, applied to you

Strip Your Emails And Feedback

Strip your emails and feedback down to honest, plain language

The idea
What it looks like

A manager avoiding a hard conversation writes a review full of qualifiers — "somewhat inconsistent," "could potentially improve" — that let both writer and reader off the hook. The employee leaves the meeting unsure whether there's actually a problem, and the issue resurfaces next quarter unchanged.

Try this

Before sending any piece of difficult feedback, find the one sentence that states the actual issue and the one sentence that states the actual ask. Put those first, then cut every hedge word — "somewhat," "kind of," "maybe" — from what surrounds them.

Protect A Consistent Block

Protect a consistent block of time for writing that matters

The idea
What it looks like

A leader only writes team updates or strategy memos in the gaps between meetings, so the writing is rushed, inconsistent in tone, and often skipped in a busy week, leaving the team to guess at priorities from whatever fragments reach them.

Try this

Block a fixed, recurring 30-minute slot — before your first meeting, say — for the writing that shapes how your team understands direction: the weekly update, the project memo, the note that sets expectations. Treat that block as non-negotiable as a client meeting.

Read Your Team's And Peers'

Read your team's and peers' writing as management education

The idea
What it looks like

Leaders read other managers' emails and documents only for content, never noticing why one manager's updates get read carefully while another's get skimmed, so they never learn what actually earns attention on a busy team.

Try this

Pick three emails or documents from leaders you find genuinely clear and three you find frustrating to read. Identify the specific sentence-level habits — length, structure, directness — that separate them, then check your own next memo against that list.

Your Own Hard Experiences As

Your own hard experiences as a manager are material, but craft decides if they land

The idea

The mistakes you've made leading people — the layoff handled badly, the feedback given too late — are legitimate material for mentoring others and for your own writing about leadership. But sharing that experience helps a reader only when it's told with the same clarity and discipline you'd bring to a status report, not as an unstructured confession that leaves the lesson buried.

When the clusters compete

Protected writing time can feel like a luxury when an urgent email needs an instant reply, and plain, direct language can feel risky when a hard conversation tempts you toward softening it. Reading other people's management writing critically takes time too, time that competes with both of those habits on any given week. Resist trading one for the other by treating them as unequal in urgency, not importance. Use your protected block for the writing that sets direction and expectations, let urgency shorten a reactive message rather than making it vaguer, and save critical reading for a slower moment when you can actually absorb what you notice.

04 · Choose Your Priority

Name one thing, honestly

Which recent piece of feedback or direction you gave would your team have understood faster if you'd cut it by half?


Good. Now look back at the "Try this" line under whichever lesson feels most connected to what you just wrote, and treat that as this week's actual assignment — not all 4 at once.

05 · Put It Into Practice

The practices from this edition

Before sending any piece of difficult feedback, find the one sentence that states the actual issue and the one sentence that states the actual ask. Put those first, then cut every hedge word — "somewhat," "kind of," "maybe" — from what surrounds them.
Block a fixed, recurring 30-minute slot — before your first meeting, say — for the writing that shapes how your team understands direction: the weekly update, the project memo, the note that sets expectations. Treat that block as non-negotiable as a client meeting.
Pick three emails or documents from leaders you find genuinely clear and three you find frustrating to read. Identify the specific sentence-level habits — length, structure, directness — that separate them, then check your own next memo against that list.

0 of 3 selected

06 · Small Experiment

Run this for seven days

Pick three emails or documents from leaders you find genuinely clear and three you find frustrating to read. Identify the specific sentence-level habits — length, structure, directness — that separate them, then check your own next memo against that list.

07 · Remember This
If you remember only 4 things
01Strip Your Emails And Feedback. Strip your emails and feedback down to honest, plain language
02Protect A Consistent Block. Protect a consistent block of time for writing that matters
03Read Your Team's And Peers'. Read your team's and peers' writing as management education
04Your Own Hard Experiences As. The mistakes you've made leading people — the layoff handled badly, the feedback given too late — are legitimate material for mentoring others and for your own writing about leadership.
08 · Your Next Step

What will you do differently because you read this?

For the fuller argument behind writing plainly and on a fixed schedule, the original source is worth the time: Stephen King's book goes further than any summary can.