Unlearning how to write
summary
Argues that teams must unlearn academic and business-speak and measure readability instead: average worker sees 20 IMs + 32 emails/day, so long dense writing loses attention; demonstrates editing tactics (revise before edit, hunt passive voice, flip “by” phrases) and tooling (Word proofing, Grammarly, AI simplification). Shows practical swaps—use tables/diagrams/video instead of long prose—including a case where an executive-summary + table wins a security upsell. Tracks impact with Flesch reading ease 0 → 73.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 4:39Writing in business needs change
- 7:47School shapes writing skills
- 10:37Unlearning ignoring audience
- 15:51Ditching jargon
- 18:17Improving readability
- 24:49Not relying solely on writing
- 29:01Learning from reading
- 31:07Planning and revising
- 37:47AI tools for writing
- 40:53Q&A
related talks
15mHow to Write So Others Read?
48mEmbracing Plain Language for Better Accessibility
22mHow To Write Like It's Your Job
21mAvoiding Anti-patterns in Technical Communication
55mThe Emperor Has No Docs
47mUI Text: Simplicity is Difficult
25mTechnical Writing for Developers and Engineers
29mWriting Less, Owning More: The Shift in Technical Writing