Tools and Workflow: Editors, Notes, Templates
Tools Follow Practice, Not the Other Way Around
A common mistake: buying into an elaborate tool setup before developing the writing practice that justifies it. The new note-taking app, the fancy editor, the graph-database-for-knowledge. Usually these produce a week of enthusiasm followed by abandoned files.
Tools serve a practice. If the practice isn't there, the tools don't substitute.
Start with the simplest possible tools and grow only when you feel the lack. Most people overestimate what tools can give them and underestimate what consistency can.
The Writing Environment
Where do you actually write?
Three options, with tradeoffs:
Plain text editor
VS Code, Sublime Text, Neovim, or a basic text editor. Files on disk. Markdown for structure.
Pros: full control, no vendor lock-in, works offline, searchable via grep, survives any software change.
Cons: no collaboration, fewer "nice-to-haves" out of the box, requires some technical literacy.
Suits: engineers, writers comfortable with plain text, anyone serious about long-term ownership.
Document editor
Google Docs, Notion, Microsoft Word, Dropbox Paper. Cloud-based, collaborative, polished.
Pros: easy to share, real-time collaboration, rich formatting, good for team writing.
Cons: vendor-dependent, slower than plain text, sometimes clunky for long documents, harder to own the corpus.
Suits: team documents, anything requiring collaboration, non-technical writers.
Dedicated writing app
Scrivener, Ulysses, iA Writer, Obsidian. Designed specifically for writing.
Pros: distraction-free, good typography, often support Markdown under the hood.
Cons: another dependency, learning curve, sometimes silo your files.
Suits: writers who feel that generic tools get in the way.
The meta-answer
Most people benefit from two environments:
- A team/collaborative surface (Google Docs, Notion) for shared work
- A personal surface (plain text, Obsidian, whatever) for private writing
Trying to use one for both usually compromises. Team surfaces are too social for private thinking; personal surfaces don't collaborate well.
Notes
Notes are your most important private writing tool. They're where writing-as-thinking happens.
Minimum viable notes
A folder of text files works. Plus a search tool (ripgrep, grep, your editor's built-in search). That's it.
You don't need more to start. Many professional writers work this way for their whole careers.
Atomic notes
A popular discipline: one idea per file. Short files. Hundreds or thousands over time. Each file has a title describing its contents.
The benefit: notes compose. You can link between them. You can re-use ideas without copying them. You build a personal encyclopedia.
Tools that support this: Obsidian, Roam Research, Logseq, Notion's database features, plain-text with wiki-style links.
The discipline is more important than the tool. A year of daily notes in plain text is more valuable than a month of Obsidian enthusiasm.
Zettelkasten
The classic atomic-notes methodology, popularised by Niklas Luhmann. Each note gets a unique identifier; notes link to related notes; a "map of content" note points to clusters.
Some people swear by this. Others find it over-elaborate. Worth a shallow investigation; adopt deeply only if it genuinely suits how you think.
Templates
Templates for recurring document types save time and improve consistency.
Templates to build
- PR description: sections for what, why, test plan, out-of-scope
- Design doc: summary, context, proposal, alternatives, rollout
- Meeting notes: attendees, decisions, action items, open questions
- Weekly update: done, doing, blockers
- Bug report: summary, repro, expected, actual, environment
- Feature proposal: problem, solution, alternatives, success metric
- Postmortem: what happened, timeline, root cause, action items
Template discipline
Templates are starting points. Delete sections that don't apply. Add sections when needed. A template you always follow rigidly is a template that's wrong some of the time.
If you find yourself deleting the same template section repeatedly, cut it. If you find yourself adding the same section repeatedly, add it to the template.
The Daily Rhythm
Writing is a practice. Practices benefit from rhythm.
Morning writing
Many writers produce best first thing in the morning, before meetings, email, and other cognitive load. An hour of clean attention.
Not everyone's wired for this. But if you're stuck and haven't tried it, try it. The productivity difference between morning and afternoon writing is meaningful for many people.
Batching
Batch similar writing tasks. Write five Slack updates in a row instead of interspersed. Draft three tickets in one sitting. Reply to email in 30-minute windows rather than constantly.
Switching contexts between writing tasks burns time. Batching stays in one mode.
The shut-down ritual
At the end of a writing session, especially one that's going to continue later:
- Leave a note for your future self: where you are, what's next
- Don't end mid-sentence unless you want to come back to that sentence
- Park the cursor where the next work starts
A small ritual that saves the re-entry tax of "where was I?".
Version Control for Writing
For important long-term writing, version control:
- Git for plain-text writers (commit your drafts; revert if you lose something)
- Google Docs' version history for collaborative docs
- Tools like Versions or Obsidian's built-in sync + backup
Mostly, version control is a recovery tool. You rarely need it; when you do, you really do.
Collaboration Tools
When writing with others:
Real-time (Google Docs, Notion)
Multiple people typing in the same document simultaneously. Good for rapid iteration, brainstorming, shared editing. Bad for deep focus.
Async review (PR review, email, Google Docs comments)
One author, multiple reviewers. Better for polished output. Less chaotic than real-time.
Version control (Git + Markdown)
For writing that doubles as code or that needs a clean history. Reviews happen as PRs. Changes are discrete and attributable.
The meta-rule
Match the tool to the work:
- Brainstorm: real-time
- Draft: solo, in whichever tool is fastest
- Review: async, with comments
- Ship: the place the final work lives
Trying to do all four in one tool produces compromise for each.
AI in the Workflow
Chapter 6 covered writing for AI. Some workflow-level patterns:
The draft-edit split
Use AI for first drafts. Edit heavily yourself. The AI drafts fast; your editing is where the value lives.
The prompt library
Save working prompts. Tag them by task. Re-use rather than re-inventing.
The review partner
Paste a draft; ask the AI for specific critique. "Where is this unclear?" "What assumptions am I making?" "Cut this to 500 words."
What to avoid
Don't let AI write the final version. Your voice is a competitive advantage; AI-default voice isn't. Use AI for speed, not for final output.
Knowledge Management Briefly
A related but distinct discipline: managing what you've read, noted, and thought over time.
The basic setup
- A place for notes (daily journal, ideas, reading notes)
- A search tool
- An occasional review habit (weekly, monthly)
The elaborate setup
Personal Knowledge Management systems (Obsidian with plugins, Roam, Logseq, Tana). Graph links, backlinks, daily notes, templates, scripts.
These can be powerful or performative. The test: does the system produce more output? More insight? Or does it mostly produce more maintenance of itself?
Chapter 11 goes deeper on writing over the long run.
The Tool Tax
A warning about spending too much time on tools:
Some writers spend more time configuring their note-taking system than using it. This is usually procrastination disguised as productivity.
Signs:
- You're trying new tools more than once a quarter
- Most of your writing time is setup, not output
- You have elaborate templates and very few filled-in instances
- Your "system" is complicated enough to explain to people
The cure: pick a system. Use it for six months. Don't change tools in that window unless they actively break.
Backups and Longevity
Your writing is valuable. Back it up.
- Plain text is the most durable format. It will open in any era
- Two copies minimum. Local and cloud, or two clouds, or whatever
- Periodic exports if you use a proprietary tool
The worst-case scenario: your note-taking app goes out of business or corrupts your data. Mitigate by keeping your data portable and backed up.
A Realistic Tool Stack
A reasonable setup for someone writing seriously:
- Personal notes: Obsidian, or plain text + grep, or Notion
- Team docs: Google Docs or Notion
- Code / technical writing: Git + Markdown
- Quick capture: phone notes app synced to the main system
- Read later: Instapaper, Readwise, or similar
- Templates: whatever your main writing tool supports
- Backup: iCloud, Dropbox, or Git remotes
This is unglamorous. That's appropriate. Most writing infrastructure doesn't need to be fancy to work.
Common Pitfalls
"I need a better tool." Usually not. You need a better habit. Tools rarely produce output that habit didn't already want to produce
"My system is complex because my thinking is." Sometimes. Usually the system is complex because you've been building the system instead of using it
"I'll set this up properly first." Setup becomes the work. Start with something minimal. Upgrade only when the minimal version visibly fails
"Different tools for different jobs." Good in theory; expensive in switching costs. Aim for one primary tool per broad purpose, not five specialised ones
"The right editor will make me productive." Productivity is 80% practice and 20% tool. Investing heavily in the tool before the practice is backwards
Next Steps
Continue to 11-writing-at-scale.md for managing years of written output as a compounding asset.