Writing Lean: Textual Efficiency and Sustainable Documentation Practices
"Sustainable" documentation has two meanings that turn out to be the same discipline. The first is maintainability: content you can keep accurate over years without a rewrite treadmill. The second is efficiency: prose and delivery that waste as little of the reader's attention — and the planet's compute — as possible. Both are served by the same habit: write less, reuse more, and delete ruthlessly.
Most documentation is not too short; it is bloated. Duplicated warnings, hedging preambles, and copy-pasted procedures create a maintenance liability that grows with every release. This article treats textual efficiency as a first-class engineering concern and shows how to encode it in your style guide. If you are new to the craft, our beginner's guide to technical writing covers the foundations these practices build on.
What "Sustainable Documentation" Actually Means
Sustainable documentation is content designed for a low total cost of ownership. A page is sustainable when a fact appears in exactly one place, so an update touches one file rather than fourteen. It is sustainable when its structure is predictable enough that any writer can maintain it, not just the original author. And it is sustainable when it is lean enough that readers find the answer fast and leave — a shorter support ticket queue is the truest metric of documentation health.
The opposite is documentation debt: sprawling, redundant content nobody dares to touch because the dependencies are invisible. Every duplicated sentence is a future inconsistency. Sustainability, then, is mostly about eliminating duplication and enforcing structure — which is exactly what a good technical writing style guide is designed to do.
Word Economy: Cutting Without Losing Meaning
Word economy is not writing tersely; it is removing words that carry no information. "In order to" becomes "to." "At this point in time" becomes "now." "It should be noted that the system will" becomes "the system." Nominalizations — "perform an installation of" — collapse back into verbs — "install." These edits typically shrink a draft 20–30% while making it clearer, because every removed word is one the reader no longer has to process.
The most sustainable sentence is one you did not write because a diagram or a code sample said it better. The Google developer documentation style guide repeatedly favors concision and concrete examples over prose explanation. Adopt a rule: after drafting, cut every sentence you can remove without losing meaning, then cut every word you can remove without losing the sentence. What remains is what readers actually needed.
Single-Sourcing and Content Reuse
The most powerful sustainability practice is single-sourcing: write a piece of content once and reuse it everywhere it is needed. DITA (Darwin Information Typing Architecture) formalizes this with content references (conref) and keys, letting you define a warning, a prerequisite, or a product name in one topic and pull it into many. When the fact changes, you edit one source and every output updates. Even without full DITA, docs-as-code setups achieve similar reuse through include directives, snippets, and variables.
Single-sourcing pays off most for content that repeats across audiences and formats — a safety warning that must appear in the quick start, the reference, and the PDF. The discipline is knowing what to modularize: reuse stable, self-contained chunks; do not fragment prose so finely that topics become unreadable jigsaw pieces. The goal is fewer sources of truth, not more files.
Minimalism: The Carroll Principle
Minimalism in technical writing, pioneered by John Carroll's research on the minimal manual, is the evidence-based finding that users learn faster from less. Readers are goal-driven and impatient; they skip introductions and jump to the task. Minimalist documentation front-loads action, cuts conceptual throat-clearing, supports error recovery, and lets readers start doing immediately. It is not dumbing down — it is respecting that the reader arrived with a job to finish.
Practically, minimalism means every topic earns its place. Ask of each paragraph: does the reader need this to complete the task, or is it here because the author wanted to explain? Move nice-to-know context into clearly-labeled optional sections or link it out. This overlaps with progressive disclosure, which we cover in our piece on audience-first technical communication.
The Environmental Math of Bloated Docs
The environmental angle is small per page but real at scale. Every unnecessary kilobyte of documentation is transferred, cached, and re-served millions of times across a popular product's lifetime. Unoptimized hero images, autoplaying video, and heavy client-side frameworks for what could be static HTML all consume network and compute energy on every view. Lean, static, text-first documentation is not just faster for the reader on a slow connection in a rural area — it is measurably lighter on infrastructure.
You do not need to become a carbon accountant. The same choices that make docs sustainable environmentally make them faster and cheaper: static site generation, compressed and appropriately sized images, no tracking bloat, and prose that is short because it is well-edited. Efficiency for the reader and efficiency for the grid are the same edit.
Building Efficiency Into Your Style Guide
Encode these practices as rules, not aspirations. Ban the common wordy phrases in your terminology list so a linter flags them. Mandate single-sourcing for warnings and product names. Require a maximum image weight and a static-first delivery format. Set a rule that every topic states its goal in the first sentence. When efficiency lives in the style guide, it survives staff turnover and applies to every future page automatically.
Darlo Technical Writing's Lean Documentation course teaches the full editing-for-economy workflow and includes a downloadable word-economy checklist and single-sourcing planning template. Explore the range at /courses. For deeper reading on modular writing, the Write the Docs resources are an excellent free starting point.
Word-Economy Editing Checklist
A one-page checklist of the most common wordy phrases and nominalizations to cut, plus a single-sourcing planning worksheet for lean, maintainable documentation.
What is single-sourcing in technical writing?
Single-sourcing means authoring a piece of content once and reusing it everywhere it's needed, so an update edits one source and propagates everywhere. DITA formalizes this with content references and keys; docs-as-code setups achieve it with includes, snippets, and variables.
Does minimalism mean leaving out important information?
No. Minimalism, based on John Carroll's research, means front-loading action and cutting conceptual filler so goal-driven readers succeed faster. Necessary information stays; it's the throat-clearing and nice-to-know context that gets trimmed or moved to optional sections.
How does documentation affect the environment?
Bloated docs — heavy images, autoplaying video, unnecessary frameworks — are transferred and served millions of times, consuming network and compute energy on every view. Lean, static, text-first documentation is lighter on infrastructure and faster for readers on slow connections.