Strategy buried in slides is forgotten; orders given in meetings leave no trace. A senior leader's real leverage is writing — a memo that has been thought through, a narrative people can retell, a set of principles others can inherit, all of which work for you when you're not in the room. This week: how to lead with words, from Bezos's six-page memo to Dalio's principles to the story that carries people through the valley of change.
The scarcest leadership skill isn't running meetings — it's writing. A well-structured memo forces you to turn vague intuition into a checkable argument, so that the best idea wins, not the loudest voice.
Slides hide broken logic behind bullets — nobody knows whether the link between point two and point three is "because" or "but." Full sentences and paragraphs have nowhere to hide: verbs must land, causation must be explicit, gaps show on the page. So writing a memo is a device that forces thinking. For a leader it has a second value: a good memo works in your absence — asynchronous, forwardable, archivable, far more reliable than the memory of a meeting.
Take the one thing you plan to "verbally pitch" in a meeting next week and rewrite it as a one-page memo: conclusion first, then reasons, data, costs, recommendation.
Reflection: When you get stuck writing, is it really a prose problem — or have you not yet figured out what you're arguing for?
Strategy written in a deck is forgotten; strategy turned into a story, everyone can retell. A company narrative isn't a slogan — it's a causal chain: where we came from, what changed in the world, why we must do this, and how the world will differ once we succeed.
Brains don't retain a parallel list of strategic points, but they remember a story. The first job of narrative is alignment: when thousands of people converge on the same answer to "why do we exist," coordination friction drops sharply. The second job is a filter: any project that doesn't serve the narrative should be cut. Amazon's "Earth's most customer-centric company," Tesla's "accelerate the world's transition to sustainable energy" — one sentence governs countless concrete trade-offs. But the narrative must be true: a fabricated story gets spotted instantly on the front line.
Write your team's or product's narrative in four sentences: where we came from → what changed → why we must do this → how things will differ once we succeed. Hand it to someone outside the group and ask if they can retell it accurately.
Reflection: Does your current mission statement still hold with a competitor's name swapped in? If so, it isn't a narrative yet — just boilerplate.
A leader makes judgments daily, but most scatter to the wind. Ray Dalio's method: each time you meet a class of problem, write down "how I should handle this" as a principle — a general if-then. On paper, it can be tested, inherited, and shared by the team.
Personal intuition doesn't scale; a written principle does. A good one has two parts: a trigger situation + a response ("when X, then Y"). It distills a one-off experience into a reusable rule — you don't judge from scratch each time, and the team can act on the same logic in your absence. The key is specificity: abstract values ("we value candor") can't guide action; an operable principle ("raise disagreements to someone's face, never behind their back, and always with an alternative") can.
Recall one judgment you made this week and write it as a principle: "When ____, then ____." Then ask: will it still hold next time? Send it to the team and see if it sparks disagreement — disagreement is exactly the chance to sharpen it.
Reflection: The line you most often repeat to your reports — shouldn't it already be written down as a principle, sparing you the re-telling?
Change fails mostly not because the plan is wrong, but because communication falls short. No one abandons a familiar present because of one deck. The job of a change narrative is to pull people, again and again, from "the safety of now" toward "the necessity of next" — and to walk with them through the messy, doubting, want-to-turn-back valley in the middle.
In Illuminate, Duarte maps the change journey as four acts: Dream (paint the vision) → Leap (encourage the jump) → Fight (stay through resistance and chaos) → Climb (celebrate small wins, persist). Most leaders deliver only the Dream and assume communication is done — but people are most likely to bail in the Fight. A real change narrative reappears at the low point: acknowledge that the hardship is real, give the next concrete small step, and make people believe "just a bit further and we're there."
Take a change you're driving and write its four acts: Dream / Leap / Fight / Climb, one sentence each. Focus on the Fight: how will you stay with the team through the middle of doubt?
Reflection: Last time you communicated a change, did you say it once and leave — or did you really repeat it tenfold, reappearing at the low point?