Writing

What have you written that changed how someone thinks?

Writing is one of the most powerful capabilities because it develops thinking. You don't write to record finished thought — you write to discover it. Vague thought becomes precise only on the page.

The capabilities index files writing under Express. Its deepest power is in Think. Writing bridges the two: thought made precise, then made to move.

Writing solidifies; conversation dissolves. Speaking helps who's in the room. Writing helps everyone — including people who couldn't make it, future employees, and your future self.

Without Writing Skill	With Writing Skill
Ideas evaporate	Ideas compound
Meetings repeat	Decisions documented
Onboarding takes months	Knowledge transfers fast
"What did we decide?"	"Here's the doc"

AI drafts at speed and scale. Humans bring clarity of thought, voice, and judgment about what's worth saying. The thinking must come from you. The drafting doesn't have to.

This is the canonical know-how writing doctrine. Writing skills in this playbook point here.

Model

Writing is horizontal craft. It should work across business, beliefs, journeys, ventures, interfaces, agent instructions, and industry knowledge.

The Writing Capability T is the reusable model: portable craft runs across the top, while domain judgment supplies depth for a specific situation.

Portable method	Job
writing-clarity	Make prose clear, concrete, short, and source-faithful.
writing-rhetoric	Build honest arguments that earn confidence.
writing-narrative	Make true change visible through a credible story movement.

Vertical skills provide situated judgment. biz-dev-storyselling decides buyer value, proof boundaries, and commercial movement. belief-article-* decides the public argument. ux-audit-copy judges words inside an interface. They compose writing methods; writing methods do not claim their authority.

The capability improves through a living loop:

Playbook doctrine -> writing skill -> domain application -> output and proof
  -> lesson returns to the Playbook

The Playbook makes the craft teachable. Skills make it repeatable. Domain work tests it against reality. Proof sharpens what the next reader and agent learn.

Writing does three things: it creates clarity (precise words force precise thought), it builds comprehension (structure frees the reader's working memory for learning), and it persuades (moves people to act). This doc teaches the first two. Persuasion belongs to Selling.

Purpose & Audience

Before writing a word, answer three questions:

• What do I want the reader to think, feel, or do after reading this?
• Is every section clearly relevant to that purpose and this specific audience?
• Is the main point obvious in the first screen?

If you can't answer all three, you're not ready to write. You're ready to think.

Structure & Flow

• Does the piece have a clear beginning, middle, and end?
• Does each paragraph focus on one idea, with a topic sentence?
• Is the order of ideas logical, with smooth transitions between paragraphs?

The test: read the first sentence of every paragraph. Does the argument hold?

Clarity And Incompressibility

Cut This	Write This
"in order to"	"to"
"due to the fact that"	"because"
"at this point in time"	"now"
"it is important that"	(delete)
"basically"	(delete)

Use short, concrete sentences and strong verbs. Prefer plain words when they carry the same meaning. Cut filler, repetition, and ornament.

Then test every sentence, section, example, and model: remove it unless its loss changes understanding, truth, action, safety, or navigation. This is incompressibility, not minimal word count.

Hemingway's omission practice is a useful clarity heuristic: know the subject, state the truest supported sentence, and leave out what the reader does not need. Documentation has a harder boundary than literary prose. Never omit evidence, confidence, qualifications, context, safety, canonical terms, or the next action when their loss could change a decision.

The Pre-Send Clarity Check

After the meaning is settled, use this DO-CONFIRM checklist before you send or publish. It is a final pause, not a substitute for thinking, research, or editorial judgment.

Purpose: Make the message smaller, clearer, and easier to act on. Keep the reader focused on the idea, not the wording.

• GATE — Lead with the point. Can the reader find the main message and why it matters without searching?
• GATE — Preserve necessary truth. Did the edit keep evidence, uncertainty, qualifications, context, safety, and the next action?
• PROMPT — Make the structure visible. Do the headings, sequence, or opening sentences show where the message is going?
• PROMPT — Prefer the simpler expression. Can a shorter sentence, plainer word, or concrete verb carry the same meaning?
• PROMPT — Remove noise. Which words, repetitions, ornaments, or digressions can disappear without loss?
• PROMPT — Protect useful complexity. Does every remaining difficult idea help the reader understand, decide, or act?
• GATE — Name the movement. Is the decision, action, or better question the reader should take away explicit?

Every sentence must earn its place.

This does not mean every sentence must be short. Keep a sentence when removing it would damage understanding, truth, action, safety, or navigation.

Run the final pass:

1. Read it once for meaning.
2. Cut once for clarity.
3. Read it again for truth and action.
4. If it says the same necessary thing more clearly, send it.

Comprehension

Experts forget what it's like not to know. This is the curse of knowledge — the expert can no longer retrieve the state in which they didn't understand. The reader arrives without your context. Writing bridges that gap, or it doesn't.

The diagnostic: explain it to a smart 12-year-old. Not to talk down — to be precise. If you cannot, you haven't finished thinking. [source: Feynman technique]

Every reader arrives with a fixed working-memory budget [source: Sweller, Cognitive Load Theory]. Burn it on complexity and they drop. Spend it on learning and they grow. Three dials control the budget:

1. Intrinsic load — the inherent complexity of what you're teaching. Sequence familiar to unfamiliar. New concepts on old scaffolding. Start where they are, not where you are. [heuristic]
2. Extraneous load — noise the reader must filter before learning anything: jargon, passive voice, buried structure, meandering paragraphs. Every word that doesn't earn its place is extraneous load. Cut it. What remains goes to learning.
3. Germane load — the productive effort of forming new schemas. This is the goal. Every structural choice either frees working memory for germane work or burns it on the other two.

The test: if the reader must re-read a sentence to parse it, they paid extraneous when they could have paid germane.

The learning arc — sequence is invisible when it works. Stall the reader and the arc failed. Move simple to complex, concept to application [heuristic]:

• Hook — why this matters before what it is
• Foundation — one concept per section, no more
• Build — layer complexity on what they now know
• Visual — diagrams that carry weight words can't
• Application — worked examples, not abstract principles
• Elaboration — further reading and open questions for the reader who wants to go further

The paragraph formula — one claim per paragraph, no hedges. Then evidence: a number, an example, a story. Then the so-what: connect to the reader's world.

Generalisations without examples are useless. Examples without generalisations are pointless. Marry both.

Voice & Tone

• Does it sound like a real person speaking, not a corporate memo or academic robot?
• Is the tone appropriate for the reader — expert, friend, executive, newcomer?
• Where it fits, do you speak directly using "you" and clear calls to action?

The read-aloud test catches what the eye misses. If you wouldn't say it to someone's face, rewrite it.

Sentence Craft

Weak	Strong
"The feature was shipped by team"	"The team shipped it"
"Made a decision to proceed"	"Decided"
"Is very important"	"Matters"
"Seems to basically indicate"	"Shows"

• Active voice over passive — the subject does the thing
• Vary sentence openings and lengths to avoid monotony
• Strong, specific verbs — not weak ones propped up by adverbs
• Related words kept close together so the sentence parses easily

Evidence & Examples

• For each key claim, give a concrete example, image, or evidence
• Show rather than tell — "Revenue dropped 40%" not "things went badly"
• Anticipate and briefly address obvious questions a smart reader would have

Claims without evidence are opinions. Opinions without authority are noise.

Polish

• Grammar, spelling, and punctuation clean enough that nothing distracts
• Technical terms used correctly and consistently throughout
• Others' ideas clearly distinguished and credited
• Final pass: cut at least a few more words that don't earn their keep

Core Patterns

• Rewriting is writing — First drafts capture. Rewrites clarify. The only kind of writing is rewriting.
• Headlines carry weight — Specific, value-driven, compelling. More people read the headline than the body copy.
• Timing — Now is often wrong. Sleep on it before sending. Let it filter through the sieve of time.
• Publish before perfect — Feedback teaches more than revision. Ship, learn, rewrite.

Failure Modes

Perfectionism. Writing as procrastination. Polishing instead of publishing.

Mistaking eloquence for clarity. The best writing is the writing that ships.

By Archetype

Archetype	Writing Style
Philosopher	Writes to think — clarity emerges through the act
Engineer	Writes to document and scale — systems over stories
Dreamer	Writes to inspire — vision into words
Coach	Writes to unlock — questions that open doors

Context

• Skills — operational methods that turn writing doctrine into repeatable agent behaviour
• Critical Thinking — Writing develops thinking; the page is where thought becomes precise
• Storytelling — Writing with narrative arc
• Selling — When writing serves persuasion
• Reading — The input side of writing
• Presenting — Writing for the spoken word
• Async Communication — Where writing discipline lives
• Writing Tools — AI amplification at 70%
• applies-to Checklists — design a brief pause-point control without turning the checklist into the whole writing procedure

Questions

Changes my mind: If clearer structure and language do not improve a real reader's understanding or action, this doctrine is optimizing prose rather than useful communication.

Next question: Which real document should provide the next before-and-after comprehension test?

If writing solidifies and conversation dissolves — what did you lose last week because you said it instead of writing it?

• Hemingway cut ruthlessly. The Learning Architect sequenced carefully. Both built comprehension. Which discipline do you resist — and what would change if you adopted it for 30 days?
• Where in your work does quality still depend on verbal explanation that a well-written document would make unnecessary?
• What's the most important thing you know that you haven't written down — and who loses when you don't?