Best Practices: Habits and the Long Arc | Writing as the Primary Interface Tutorial

This chapter distils the habits that turn writing from a task into a practice, the anti-patterns worth dropping, and the rhythm that sustains the work over a career.

Habits That Compound

Write every day

Not a literary practice; a work one. Some writing happens every day for most knowledge workers: messages, notes, updates. The question is whether you do it deliberately or accidentally.

Deliberate daily writing means: open your notes, write something, even briefly. Over a year, the habit produces a body of work and a sharpened sense for the craft.

You don't need to write essays every day. Five minutes of notes will do. The act of touching the practice daily builds the muscle.

Always draft before editing

Chapter 8 was about this. Do the drafting voice first; let it be bad; edit later. Trying to do both at once makes both worse.

This habit is small but pays back over the next ten thousand documents you'll write.

Know your primary reader

For every piece of writing: who is this for? If you can't answer, the writing will be unfocused. If you can, the writing will at least be addressed correctly.

This is a discipline, not a revelation. You already know the reader in most cases; the habit is making it explicit.

Convert rented writing to owned

Slack messages that should have been docs. Meetings that should have been memos. Conversations that should have been tickets. Over years, your ratio of durable writing to ephemeral writing should rise.

This isn't about writing more; it's about writing in the right place. A meeting discussion that never becomes a memo is work that can't compound; the knowledge dies with the meeting.

Name things deliberately

Chapter 9 was about this. The documents, tickets, projects, products you name live with those names for years. Fifteen minutes choosing a good name pays back over the life of the thing.

Ship imperfect work

Perfect is the enemy of shipped. A document that's 85% quality, out today, usually beats a 95% document out in three weeks. Most work writing doesn't need to be art; it needs to be clear and in front of the right people.

Develop the habit of shipping at "good enough, given the stakes". Reserve high-polish work for things that deserve it (public writing, high-stakes proposals). Everything else should be useful-and-out.

Review old work

Go back to things you wrote six months or a year ago. Notice:

What held up
What you'd now write differently
Patterns you didn't see at the time
Ideas worth revisiting

The review is half the value of a writing practice. Writing you never re-read is writing that doesn't compound.

Keep a commonplace book

Derived from the older habit of recording quotes, fragments, and passages in a dedicated notebook. A file or notebook where you collect:

Good sentences you read
Ideas worth holding on to
Names and frames you want to remember
Observations from your week

The commonplace book is raw material for later writing. Over years it becomes its own kind of education.

Read widely outside your domain

Most work writing improves when the writer has read widely. Not because of specific information transfer; because of exposure to varied sentence structures, argument shapes, and registers.

Writers who only read work-writing produce work-writing that reads like everyone else's. Writers who also read essays, fiction, history, poetry, bring unexpected notes to their prose.

Ask for the piece of feedback you want

Generic feedback ("what did you think?") produces generic feedback ("it's good"). Specific feedback requests produce specific feedback:

"Does the second section drag?"
"Is my recommendation clear?"
"Does the tone feel right for a public audience?"
"Is there a clearer way to explain the middle concept?"

Ask for one or two things per review. The reviewer will have energy to engage; the feedback will be actionable.

Anti-Patterns Worth Avoiding

Writing to look smart

A common failure. Sentences designed to impress rather than to transmit. Vocabulary chosen for flavour rather than precision. Arguments made for subtlety rather than clarity.

The cure: write to be useful. Imagine a reader who has a job to do, not a judgment to make.

The comprehensive document

A document that tries to cover everything. Every angle, every edge case, every historical consideration. Usually too long to read and too generic to apply.

Cut the scope. One document, one main point. Additional considerations go in follow-ups.

The stream of consciousness document

Typing as you think, unedited, sent. Common in Slack and email. The reader has to decode what you were working out; the effort has been offloaded from writer to reader.

Take an extra five minutes to organise your thinking before sending. The reader saves fifteen minutes.

The meeting disguised as a document

A document whose real point is "come talk to me about this". Often unclear and undecided, because the writer didn't want to commit before discussion.

Commit in writing. If you need to discuss, state your current view explicitly and ask for challenge. "I think we should do X; tell me if I'm wrong" beats "some thoughts on whether to do X".

Permanent placeholders

"TBD", "TODO", "figure out later" that never get figured out. Over time, placeholders calcify into the document.

Either resolve them before shipping or flag them loudly ("unresolved question, blocks decision by Friday"). Quiet placeholders are worse than missing sections.

Tone as posture

Affecting a voice you don't have. Too-formal language when your actual register is warmer. Too-casual when the stakes demand formality. Corporate patter when your own voice is sharper.

Your voice is a competitive advantage. Write closer to how you actually talk and think. Adjust the register where context demands, but don't abandon yourself.

Over-optimising short writing

The hour you spent polishing the opening sentence of a Slack message. The agonising over one word in a ticket title.

Some short writing deserves care (product names, taglines, public headlines). Most doesn't. A rough heuristic: time spent should scale with number of readers times stakes. A Slack message to one colleague doesn't merit the attention a public launch tagline does.

Hiding behind AI

Letting AI write and shipping without editing. The output is fine; it's also indistinct. Over time, a pattern of AI-default writing becomes a tell, and readers notice.

Use AI as a multiplier on your voice, not a replacement.

The Monthly Writing Audit

Once a month, ten minutes:

What did I write this month? Rough list
What was high-impact? Things that influenced decisions, onboarded people, or compounded
What was low-impact? Things that didn't need to be written, or didn't need to be that long
What would I do differently? Specific, not general
Is my corpus searchable? Could I find X from this month in six months?

If the audit reveals that most of your writing is low-impact, shift. Write less, with more care. If it reveals that you're writing little high-impact work, ask what you're avoiding.

The Yearly Reflection

Once a year, a longer reflection:

What are the through-lines of my writing this year?
What topics did I keep coming back to?
What improved; what didn't?
What do I want to develop next year?

These reflections are themselves writing. They compound: last year's reflection informs this year's priorities. Over five years, you have a record of your own development that most people don't.

Signals of a Healthy Practice

You write daily, deliberately
Your corpus is growing and searchable
You re-read old work occasionally
Your short writing (names, titles, labels) gets the attention it deserves
You ship imperfect work often and polish rarely when it matters
You notice your own patterns over time
You can articulate your voice, at least roughly

Signals of a Stalled Practice

Writing feels like a chore, always
You can't find things you wrote a month ago
Every document feels like starting from scratch
You re-write the same patterns endlessly without templating them
You haven't read your old work in months
Your writing all sounds the same regardless of audience
You know your writing is weak but haven't invested in improving it

Stalls are fixable. Usually the fix is smaller than you'd expect: picking one habit from this chapter and sticking with it for a month.

The Long Arc

Writing is a craft with a decade-long arc. Most of the compounding happens between year 3 and year 10, if you keep going.

Year 1: the habit takes hold, your corpus starts
Year 2: you develop patterns, templates, voice
Year 3: your writing is noticeably better than the 95th percentile of non-writers
Year 5: you can articulate your style, refuse work that doesn't suit, and work faster
Year 10: the craft is a permanent part of how you think

None of this is guaranteed. It requires sustained attention. It rewards it.

The people who show up the longest have the most compounded skill. That's not fair; it's just true.

One Last Argument

Writing is not a neutral activity. It shapes what you can think, which shapes what you can do. The person who writes a memo a week about their work knows their work differently than the person who doesn't. Over years, these are different people.

The stakes of writing as the primary interface aren't just operational. They're intellectual. A writing practice is, in the honest sense, a thinking practice. Investing in it is investing in the kind of mind you'll have ten years from now.

That's the real argument for writing as the primary interface: not that it's efficient (though it is), but that it's transformative. The work you put in to becoming a better writer comes back as a clearer thinker.

Where to Go From Here

Pick one habit from this chapter and commit for 30 days
Audit your current writing practice: what's missing? What's excess?
Pick one piece of your recent writing and apply chapters 03, 07, and 08 to revise it
Read On Writing Well, The Sense of Style, or Writing Tools (or all three, over time)
Publish something, even privately
Come back to this tutorial in a year; both you and the practice will have changed