Clear Writing Principles
Clear writing: one idea per sentence avoiding compound complexity, active voice with subject doing action, concrete nouns over abstractions, short sentences.
Welcome to the complete index of every article in our Professional Writing Documentation collection on When Notes Fly. This page lists all 13 articles in the section, organized alphabetically for easy reference. Each piece is researched, written by hand, and grounded in academic sources, professional practice, or empirical data. Whether you are diving into Professional Writing Documentation for the first time or returning to find a specific article, the index below gives you direct access to the full collection within Work Skills.
If you are new to Professional Writing Documentation, we recommend starting with the foundational explainers and definitions before moving on to specific case studies, applied frameworks, and deeper analytical pieces. Articles are written for thoughtful readers who want substance over summary, with clear explanations of how ideas connect, where they come from, and why they matter. Use this index as a navigational map: skim the titles, read the short summaries, and click through to the pieces that draw your interest. Each article also links to related material so you can follow a thread of ideas across our entire Work Skills library.
Clear writing: one idea per sentence avoiding compound complexity, active voice with subject doing action, concrete nouns over abstractions, short sentences.
Documentation debt: Docs lag behind reality when code changes but docs don't. Accumulates through rushed features, team turnover, and neglected maintenance.
Documentation systems: wikis for collaborative linked knowledge, README hierarchy from project to file level, and docs-as-code with version control.
Editing for precision eliminates ambiguity: Remove weasel words (seems, might, perhaps), specify quantities (many → 73%), clarify pronouns (it, this, that).
Clear writing principles backed by research: Flesch reading ease, plain language, the Pyramid Principle, George Orwell's 6 rules, and the specific habits that make writing clearer.
Knowledge writing captures expertise: explicit knowledge with documented steps and procedures, plus tacit knowledge including context and judgment calls.
Writing structure guides readers: Top-down starts with conclusion, bottom-up builds to conclusion, chronological follows time order, problem-solution format.
Technical documentation types: API docs (endpoints, parameters, examples), user guides (workflows, screenshots), architecture docs (system design, decisions).
Knowledge management is how organizations capture, share, and preserve what they know. Learn about Nonaka's SECI model, tacit vs explicit knowledge, and wikis vs documentation.
Technical writing translates complex information into clear, usable documentation. Learn what technical writers do, key frameworks like Divio, tools, salary data, and career paths.
Common writing mistakes: burying the lead with main point last, passive voice obscuring actor, jargon overload, and vague pronouns like it or this.
Writing for clarity: Short sentences with one idea each, familiar simple words, active voice where subject acts, concrete examples illustrating abstractions.
Writing for decision-makers: lead with recommendation, provide supporting evidence, quantify impact, address risks, specify next steps and timeline.
« Back to Professional Writing Documentation · All Work Skills Articles · Home