A short defense of writing things down.

Meetings are useful until everyone leaves with a different memory of what happened.

Decks are useful until the decision gets spread across fourteen slides and three appendix pages.

Slack is useful until the person who remembers the thread leaves the company.

This is the ordinary failure mode of modern work. Teams talk constantly. They present constantly. They react constantly. Then six weeks later, nobody can find the decision.

Writing things down sounds obvious. It also sounds slow. That is why teams skip it.

The problem is not that people dislike writing. The problem is that writing creates commitment. A meeting can keep ambiguity alive. A deck can frame ambiguity beautifully. A document has a harder time hiding it.

That is why written deliverables matter.

A good written artifact forces the author to make choices. What is the actual decision? What changed? What evidence matters? What risk remains? Who owns the next move? If the answer is not clear in writing, it probably was not clear in the room.

That does not mean every thought needs a document. Nobody needs a memo for picking a button label. Writing becomes waste when it is used to decorate small decisions or create procedural cover for work everyone already understands.

But consequential work needs a record.

The record matters because organizations forget. People change roles. Sponsors leave. Priorities move. The same argument returns under a new name. Without a written artifact, the company has to re-litigate the decision from memory.

Memory is not a system.

There is another benefit that does not get enough attention: writing lowers the political temperature.

In a live conversation, disagreement can look like personal resistance. A stakeholder challenges a point, someone defends their team, and the room starts managing tone instead of substance. A written artifact gives the disagreement somewhere else to land. The sentence is wrong. The assumption is weak. The risk is understated. The decision is too soft. That kind of critique is easier to use because it is aimed at the work, not the person speaking.

Writing also exposes fake alignment. A room can nod. A document cannot nod back. When the decision is written plainly, people have to react to the actual commitment. That is where the useful objections appear. The team discovers whether it agreed on the same thing or merely agreed to stop talking.

This is why I distrust deliverables that exist only as presentation material. Slides can be excellent when the job is narration. They are weaker when the job is commitment. A slide can imply the decision. A memo has to state it.

The best written artifacts are not long. They are sharp.

A one-page decision memo can end a two-month swirl. A short scope note can prevent a month of quiet drift. A weekly status memo can surface the one risk that should not wait for the steering committee. A launch brief can force product, engineering, marketing, sales, and support to agree on what is actually happening.

Writing also changes the meeting that follows it. If everyone reads the memo first, the room can argue about the decision instead of discovering the topic. That is a better use of senior people's time.

This is especially true in diagnostic work. A diagnostic engagement should not end with a mood. It should end with a written call: build, kill, or redirect. The memo is not paperwork. It is the product.

The same principle applies in longer senior consulting or fractional work. The value is not only the advice given in meetings. The value is the memo trail that lets the client see how decisions were made, what tradeoffs were accepted, and what assumptions need to be revisited.

Writing is not enough by itself. Some work has to happen live. Sensitive feedback often needs a conversation. Tradeoffs sometimes need a room full of people. Relationships are not built through documents alone.

The mistake is treating that as an argument against writing.

The right artifact does not replace the conversation. It improves it. It gives the conversation a spine.

The discipline is not volume. It is not more pages, more templates, or more documentation theater. The discipline is matching the artifact to the cost of being misunderstood.

If misunderstanding would be cheap, talk it through and move on.

If misunderstanding would cost a quarter, write it down.

That is not a documentation preference. It is a risk control.