Leadership · Communication · Decision-Making

Think in Writing: The Executive's Most Underused Tool

October 2, 20269 min read

Handwritten pages of a decision memo spread across a dark walnut desk with a fountain pen resting on them, lit by warm amber lamplight against deep charcoal and navy shadows, cinematic dark editorial photography.

Most senior leaders think out loud, decide in meetings, and communicate in fragments. Writing before deciding is the cheapest upgrade to executive judgment available — and almost nobody in the building does it.

Watch a senior team make a real decision and you'll notice something: almost none of the thinking is written down. It happens out loud — in the meeting, in the hallway after the meeting, in a Slack thread that evaporates by Friday. Everyone speaks in fragments, the most fluent voice in the room becomes the frame, and at the end someone 'aligns' on a direction nobody could state in two consecutive sentences. Then people wonder why execution drifts. There's a tool that fixes most of this, it costs nothing, and it's sitting unused on virtually every executive's desk: the blank page. Writing is not a communication skill bolted onto leadership. Done properly, it's the sharpest thinking tool a senior leader has.

The problem with thinking out loud is that speech is fluent before it's accurate. Talk about a decision for ten minutes and you'll produce something that sounds reasoned — complete sentences, confident transitions, a strong finish — because conversation rewards momentum, not rigor. Gaps in the logic hide inside the flow. Writing removes the hiding places. To put an argument on paper you have to decide what comes first, what depends on what, and what you're actually claiming — and the moment you do, the hand-waving you could perform in a meeting becomes visible as hand-waving. This is why so many leaders secretly avoid writing about their hard decisions. The page doesn't nod along.

"I have made this longer than usual because I have not had time to make it short."— Blaise Pascal

A memo is a decision-forcing function

The most valuable version of this practice is deliberately narrow: a one-page decision memo, written before the meeting where the decision gets made. Its purpose isn't documentation — it's to force the writer past the point where verbal reasoning lets you stop. A useful one has a ruthless structure:

  • The decision, in one sentence, at the top. Not the background, not the options — the actual call. If you can't write that sentence, you haven't decided anything yet, and the meeting will be where you discover that.
  • What this decision says no to. Every real trade has a loser. Naming it in writing — the other initiative that gets slower, the team that absorbs the cost — converts a vague priority into an owned consequence.
  • The strongest counterargument, stated fairly. Not a strawman you can knock over in a sentence, but the case a smart skeptic would make. If you can't write it convincingly, you haven't understood your own decision's risk.
  • What would change our mind. The condition or evidence that should reverse the call. This single line is what separates a decision from a mood.
  • Who owns it, and by when. A name and a date. Anything else is a discussion.

Notice what this does to the meeting that follows. If the memo is read in the first ten minutes — silently, in the room, which is the only way anyone actually reads pre-reads — the meeting stops being a performance of positions and becomes a critique of a fixed object. People argue with sentences on a page rather than with each other, the quiet expert with the best objection gets equal footing with the loudest voice, and the decision lands with a written rationale anyone can consult six months later. You'll also start catching something valuable in yourself: the decisions you keep postponing writing are usually the ones you already know are troubled.

Why this scales when nothing else does

Individual clarity is only half the payoff. Organizations don't scale decisions through meetings — meetings scale presence, and presence stops scaling the moment you add a second timezone or a third leadership layer. Written decisions scale across time, distance, and turnover. A new executive inheriting a portfolio can read twelve decision memos and understand the reasoning, not just the outcomes. A team in another region can act on the rationale instead of waiting for a follow-up call. And when circumstances change, you can revisit the actual argument you made rather than a memory of it that everyone has quietly rewritten. The companies that decide well at scale are almost never the ones with the best meetings. They're the ones with the best paper trail of thinking.

The physiology of an overloaded mind

There's also a bluntly biological reason writing works when talking doesn't. Working memory holds only a handful of items at once, and a stressed executive's version holds fewer — which is why a hard problem can feel like it's circling without landing. You loop the same three considerations, lose the fourth, and start again. Putting the loop on paper offloads it: the page holds everything at once so your prefrontal machinery can do the only thing it's actually good at — finding relationships between things — instead of just trying not to drop them. This is also why writing about a decision late at night rarely goes well and writing about it after rest feels like a different brain. The tool is free; the capacity to use it is not.

Building the habit without becoming a writer

The usual objection is 'I'm not a writer,' which misunderstands the exercise. This isn't prose and nobody is grading it. It's a thinking protocol, and it can be installed with almost no ceremony:

  • Start with one decision a week. Pick the single call you'd most hate to get wrong, and write the one-page memo before any meeting about it. Ten or fifteen minutes is enough.
  • Write before you talk. The memo's value comes from being first. If you've already argued your position in a meeting, you're no longer thinking on paper — you're defending in writing.
  • Read memos in the meeting, not before it. Ten silent minutes at the top of the agenda beats pre-reads nobody opens, and it puts every reader on the same page — literally.
  • Archive decisions with their date and reasoning. Six months later you can audit your own judgment instead of reconstructing it, which is the fastest way to improve it.
  • Keep the bar at one page. Length is where the discipline goes to die. If it needs two pages, you're probably writing two decisions.

One caution: don't let this become a bureaucratic gate. The memo exists to sharpen a decision, not to slow one down — some calls genuinely are reversible, cheap, and best made in five minutes on a walk. Apply the discipline where the stakes and ambiguity are high enough to deserve it, and let the rest of the organization move fast. A leader who demands written rationale for everything has built a new meeting with extra steps.

What you'll find, a quarter into the practice, is that the benefits compound quietly. Your meetings shorten because the thinking arrived on paper. Your decisions improve because weak reasoning died in private instead of in public. Your team starts writing their own memos — not because you mandated it, but because they watched what it did for yours. Thinking in writing won't make you a better leader by itself. But it makes visible, every single week, exactly where your reasoning is thin — and no leader who sees that clearly keeps thinking the same way.

Two earlier pieces pair naturally with this one: the strategic no covers the trades a written decision should name, and making high-stakes decisions under uncertainty covers the judgment side of the calls that deserve a memo. And if the decisions piling up all trace back to one overloaded person, that's the core problem we untangle in founder and executive coaching.

Read next

The Strategic No: Why Focus Is a Leadership Decision, Not a Slogan →