Overcoming the Plight of Lone Writers
summary
Survey shows 34% of respondents work as lone writers, so the concrete fixes matter: build a company style guide, a public process document, and a tracking sheet for every request; adopt tools that actually get used—Airtable/Google Sheets, Trello/Jira, Draw.io for flows, GitBook for publishing, Grammarly for copy—and contribute or use Good Docs Project templates to avoid blank‑page anxiety. Templates plus community feedback measurably cut review cycles and make solo documentation sustainable.
AI-written summary · about
chapters (17)
- 0:00Introduction
- 5:30Lone Writers
- 6:30Reasons for being a lone writer
- 8:15Why dont companies hire technical writers
- 10:55Benefits of being in a team
- 13:30Benefits of being a lone writer
- 17:30Tools to manage your work
- 18:40Create your own style guide
- 19:45Define a process
- 20:35The power of commentaries
- 21:05Good Docs Project
- 23:45Take Aways
- 25:25Tools and Processes
- 29:05Writing Style Guides
- 31:35Reviews
- 33:05Grammarly
- 34:05Do you miss being in a team
related talks
44mFrom Me to Us: Building a docs team from the ground up
35mEngage or Die: Four Techniques for Writing Indispensible Docs
36mThe Invisible Work: What It Takes to Be the First (and Only) Tech Writer on the Team
38mSeven habits of increasingly technical technical writers
41mLevel Up: Onboarding that enables writers to thrive
50mDocs leadership: How to become a stronger leader for your team
31m7 Essential Tips for the Enlightened Tech Writer
39mBeyond Words: Strategies for Leveling Up Your Tech Writing Career