Day 27 · 2026.06.14

Writing & Expression: Writing for Leadership & ChangeLeading by Memo · Company Narrative · Principles · Change Story

BigCat's Writing

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.

Principle 01

Leading by Memo: Writing Instead of Ordering in Meetings

Writing as a Team's Operating System
Bezos · Decision Tool
Principle + Master's Words

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.

"We don't do PowerPoint (or any other slide-oriented) presentations at Amazon. Instead, we write narratively structured six-page memos. We silently read one at the beginning of each meeting in a kind of 'study hall.'" — Jeff Bezos, 2017 Amazon Shareholder Letter
Why It Works

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.

Slides / Bullets
points listed · logic lives in your mouth
Narrative Memo
full sentences · causation can't hide
From "persuade by presence" to "convince by argument"
Before & After
• Q3 growth slowing • Recommend more ad spend • Budget +$2M Q3 organic growth fell from 8% to 3%, mainly because Channel A's acquisition cost doubled (data in appendix). Staying with it costs us $12M GMV for the year. I recommend shifting $2M from Channel A to Channel B — B's CAC is half, but needs a 6-week ramp, so Q3 short-term numbers look worse.
"We value clear communication and want everyone aligned on the roadmap." Half our team can't name our top priority for this quarter. Until they can, every planning meeting re-litigates the same trade-offs. This memo proposes one sentence we all commit to — and the three things we stop doing because of it.
When to Use + Common Mistakes
  • ✓ Decision proposals, strategy reviews, cross-team alignment, any decision worth a paper trail
  • ✗ Not for: pure status updates, incident reports, or trivia in a small high-trust team (six pages becomes bureaucracy)
  • Mistake: piling slide bullets into paragraphs — the form changed but the broken logic remains
  • Mistake: using jargon and passive voice to mask "I'm not sure" — a good memo states costs and risks plainly
This Week's Exercise + Reflection

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?

Principle 02

The Company Narrative: A Story People Can Retell

Strategy People Can Retell
Horowitz · Org Narrative
Principle + Master's Words

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.

"A company without a story is usually a company without a strategy. The most important thing that you communicate to your employees is not strategy, mission, or vision; it's the story." — Ben Horowitz, The Hard Thing About Hard Things (2014)
Why It Works

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.

Before & After
Our mission is to be the industry-leading provider of intelligent cloud services, continuously creating value for customers. Ten years ago, every company had to build its own data center to use AI. Today we let a three-person team deploy models like a tech giant. We exist so compute is no longer a privilege of the few.
We strive to deliver world-class solutions that delight our customers and drive shareholder value. Software used to take a year and a whole team to build. We exist so one person with an idea can ship it in a weekend. Every feature we cut or keep answers to that.
When to Use + Common Mistakes
  • ✓ Strategy talks, all-hands, hiring, fundraising, onboarding, the internal basis for product trade-offs
  • ✗ Not for: execution specs or technical detail (narrative gives direction, not specifics)
  • Mistake: mistaking a "mission statement" for a narrative — if it still holds with a competitor's name swapped in, it isn't one
  • Mistake: only "how great it'll be," missing the origin and tension of "where we came from and why we must"
This Week's Exercise + Reflection

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.

Principle 03

Writing Principles: Turning a Judgment into a Reusable Rule

Turning Decisions into Reusable Rules
Dalio · Decision Capital
Principle + Master's Words

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.

"Principles are fundamental truths that serve as the foundations for behavior that gets you what you want out of life. They can be applied again and again in similar situations to help you achieve your goals." — Ray Dalio, Principles: Life and Work (2017)
Why It Works

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.

Trigger — When X + Response — Then Y
= Reusable Principle
specific · operable · sharpened by disagreement
Before & After
We are a company that values data-driven decisions. When a decision can be tested by a small experiment, run the experiment before arguing; only when the experiment costs more than the decision's risk do we decide by judgment.
We value ownership. When something is broken and it's unclear whose job it is to fix it, the person who noticed it owns it — until they've either fixed it or handed it to a named owner.
When to Use + Common Mistakes
  • ✓ Team culture docs, decision frameworks, recurring dilemmas, passing on experience to new hires
  • ✗ Not for: one-off unique situations, or exploratory phases that need flexibility (premature rules become shackles)
  • Mistake: treating a value as a principle — "we value integrity" guides no concrete action
  • Mistake: principles that only accumulate — never revisited, so the world changes while the rules stay frozen
This Week's Exercise + Reflection

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?

Principle 04

The Change Narrative: Carrying People Through the Messy Middle

Leading Through the Messy Middle
Kotter · Duarte Illuminate
Principle + Master's Words

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.

"The real issue is that their vision is often undercommunicated — by a factor of ten (or one hundred or even one thousand)." — John Kotter, Leading Change (1996)
Why It Works

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."

Act I Dream why we must change,
what the future looks like
Act II Leap the first
concrete step
Act III Fight doubt and chaos,
where people bail
Act IV Climb celebrate wins,
persist to the end
Duarte's Illuminate four acts — communication must reappear at the Fight
Before & After
The company has decided to go AI-first across the board. Please cooperate; we expect to finish in three months. I know many of you are thinking: our current work is already good, why change? (facing the Fight) But customer needs now shift every three months, and the old pace can't keep up. (the necessity in Dream) This month we do just one small thing — each team picks one workflow and rebuilds it with AI, then we review together. (the Leap step) I'll sync progress with you weekly. (Climb alongside)
Effective Monday, we're reorganizing into pods. Please update your calendars. I know reorgs feel like the ground moving under you — and the last one didn't go great. Here's why this one is different, what won't change, and the one thing I'm asking of you this week. I'll be in the room for questions every day at 4pm.
When to Use + Common Mistakes
  • ✓ Reorgs, strategic pivots, process change, M&A integration — any time you need people to change habits
  • ✗ Not for: pure informational changes requiring no behavior shift (e.g., an office-move notice)
  • Mistake: saying it once and assuming everyone got it — Kotter says you undercommunicated by at least tenfold
  • Mistake: painting only the Dream, never staying for the Fight — the vision is lovely, but no one helps them across the valley
This Week's Exercise + Reflection

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?

Going Deeper

Is memo culture right for every team? When does writing a memo become bureaucracy?
A memo's value is "forcing clear thought + an async record"; its cost is writing time. For high-stakes, cross-team, alignment-needing decisions, that time pays off; in a small high-trust team's daily work, forcing six pages only slows things down. The test is "reversibility and blast radius": hard-to-reverse, many-people decisions deserve a memo; quickly reversible ones, a single message will do. Form serves the weight of the decision, not the other way around.
When you don't fully believe the company narrative, how do you convey it as a middle manager?
The worst move is mechanically reciting words you don't believe — the front line sees through it and trust collapses. Better is "translate, don't transmit": find the part of the narrative you genuinely agree with, tell it in your own words close to your team's reality, and honestly flag the parts you're still working out. Leadership doesn't require pretending to be all-knowing; it requires not lying. Sincere "partial belief" is more compelling than fake "total faith."
For the same change message, when to write a memo, when to speak on stage, when to record a video?
Look at two dimensions: complexity and emotional weight. Complex, precision-needing, re-readable content — write a memo (logic that survives slow reading). Emotionally heavy, trust-building, "needs to see a human" content — go on stage or record video (tone, pauses, eyes carry what text can't). Change communication often needs both: pin the logic with a memo, then light the emotion with a live talk. Not either/or, but division of labor.
Can the English leadership-memo tradition transplant straight into a Chinese context?
The skeleton transplants; the tone needs tuning. BLUF, conclusion-first, explicit causation — these are thinking structures, language-agnostic, and Chinese benefits equally. But the near-bluntness of an English memo can feel harsh or even offensive dropped into a Chinese workplace. The reconciliation: keep the conclusion first, but leave room in wording around "costs" and "objections" — turn "this plan will fail" into "this plan has two risks I haven't thought through." Clear isn't the same as harsh; indirect isn't the same as evasive.