Writing is the leadership multiplier

Everything else a leader does has a range limit.

A conversation reaches the people in it. A meeting reaches the calendar invite.

And even the best explanation you've ever given decays as it gets retold, until by the third retelling it's a different claim with your name still attached to it.

A document doesn't decay.

It reaches the engineer who joins in fourteen months. The team in another timezone. The person deciding something at 4pm on a Friday who'd otherwise have guessed.

That's the multiplier. It's also why writing is the one place I'm maximally formal, inside an otherwise pretty informal operating style.

Mandatory before major decisions

For anything irreversible there's a document, and it exists before the meeting rather than after it.

Six pages of prose. Not slides.

Circulated in advance, or read in silence at the start of the meeting, which I prefer, because "read in advance" quietly means "skimmed on the way in."

The reason isn't record-keeping. It's that writing forces the thinking to finish.

You can hold a vague idea in your head indefinitely and it feels perfectly solid. Try to write the paragraph explaining why the second option is worse and you'll discover, about halfway through, that you don't actually know.

That discovery is the entire value. And it happens at your desk instead of in front of eight people.

It also changes who gets heard.

A meeting rewards fast talkers and people who think out loud. A document rewards whoever thought hardest, which is a far better selection criterion for a decision you can't undo.

The careful engineer who needs a day to form a view gets a day.

And it removes the two-week tail.

Decisions made verbally get re-explained repeatedly, drift with each telling, then get relitigated by people who weren't there. A written decision is a thing you point at.

Bullet points don't do this.

Prose forces you to connect the claims, and the connections are exactly where the reasoning either holds or doesn't. That's the whole argument for the format, and it's why "just make it a deck" defeats the purpose.

The documents worth writing

Not everything deserves a document. Here's the short list that repays the effort many times over.

The decision memo, described above. Context, options, recommendation, what would change your mind.

The one-page strategy. What we're doing this period, why, and what we're deliberately not doing.

That last section is what makes it useful. Every organisation has ten visible problems, and naming the ones you're leaving alone is what lets everybody else stop worrying about them.

The written update. Weekly or monthly, depending on the audience.

What shipped, what's stuck, what I need, what I'm worried about. Short. Boring by design.

The architecture decision record, covered in its own lesson, and different from a decision memo in that it's written to be read by a stranger in two years.

The postmortem, also its own subject, and the most-read document in most engineering organisations because it's the only honest account of how the system behaves.

That's five.

Nearly everything else written inside companies is a status report that could have been a link, or a policy nobody reads until they're already in trouble.

Write so it can be disagreed with

Most internal documents are written to be approved, and it shows.

Hedged claims. No numbers. Every objection pre-softened until there's nothing left to push against.

A document that can't be disagreed with can't be improved. It also can't be believed, because a reader who can't find the weak point assumes it's hidden rather than absent.

So make the claims specific enough to be wrong.

Not "this will improve performance." Instead: "this should take p95 from 800ms to under 300ms, and if it doesn't get under 500ms it wasn't worth doing."

Put the strongest counterargument in the document, in its strongest form, and answer it.

If you can't answer it, you've learned something before the meeting instead of during it.

And say what would change your mind.

That single line does more for a document's credibility than anything else in it, because it shows you've imagined being wrong.

Introducing this to a company that doesn't do it

Don't announce a writing culture. Announcements produce compliance documents. Worst kind there is.

Start by doing it yourself, for one decision, and run the meeting differently. Hand out the document, twenty minutes of silence, then discussion.

People find the silence uncomfortable exactly once. Then most of them notice the conversation afterwards was better than usual.

Then do it again. The practice spreads by demonstration, or it doesn't spread at all.

Expect two objections, and take both seriously.

"This is slow" is true. The answer is that it's reserved for decisions where slow is correct, and you aren't asking for it on the reversible ones.

"Not everyone writes well" is also true, and it matters more, because a writing-first culture can quietly disadvantage people still learning the language or people who think in other formats. Which means giving feedback on drafts is part of the job, and judging the thinking rather than the prose is a discipline you have to hold on purpose.

Keeping documents alive

The default fate of a document is to become archaeology. Technically present, quietly wrong, still being cited by somebody who has no idea it's stale.

Three habits keep the important ones alive.

Each has an owner, named in the document. Each has a last-reviewed date, visible at the top. And the small number that are genuinely load-bearing get reviewed on a schedule, where the outcome can legitimately be "this is obsolete, archived."

Archiving is the part nobody does.

A document that no longer describes reality should be marked as such, loudly, rather than left there to mislead somebody. And if what changed is the whole premise, deleting beats editing.

The habit worth building

Write the thing you're about to explain for the third time.

That's the trigger.

If you've given the same explanation to three different people, it's a document. Writing it takes forty minutes and saves you the fourth through fortieth explanations.

Most of my genuinely useful documents started exactly that way, and none of them started as an attempt to write something important.