7 Values of Effective Tech Writing Teams
summary
Argues that the tech writer's goal is to help build products that need no documentation and lays out seven actionable values used at OutSystems and Docker: act as CEO of the docs (define vision, microcopy, in‑app help, what to document and where), know market/product/users, always ask why and apply the 80/20 rule, schedule strategic time, treat words as engineering tools (diagrams, code samples, screenshots), and coach others with guides and one‑on‑ones.
AI-written summary · about
chapters (9)
- 0:00Intro
- 0:24Skepticism
- 1:27Goals
- 8:45Know the Market
- 12:21Perfection Takes Time
- 13:35Proactive
- 14:13Designers
- 15:56Words
- 19:05Sharing Knowledge
related talks
12mWhy Work with a Tech Writer?
25mTechnical Writing for Developers and Engineers
01h 24mWriting Documentation - Practices and Theory
17mHacking Your Documentation: Who Should WTFM?
34mDocumentation Thinking Beyond the Docs: Lessons from Decision-Facing Technical Writing
46mEssentials for Building and Leading Highly Effective Development Teams
10mWriting effective documentation
20mHow to write software documentation (3 major tips)