Anne Janzer—author of Writing to Be Understood—shares how technical writers can make their technical writing more interesting. We discuss where technical writers may currently miss the mark in their writing, how technical writers can use cognitive science to make their writing more interesting, and small steps technical writers can take today to begin applying the concepts.
Tech Writer Advocacy and Managing Write the Docs with Swapnil Ogale
Documentarians for Diplomacy: Bringing the Mirth with Kat Stoica Ostenfeld
Marrying skillsets and existential googling with Caity Cronkhite
How to Infiltrate a Hackathon in Iowa with Philip Kiely
A Fond Farewell (Yet Warm Welcome!)
Skill #36: Creating Usability Tests for Your Organization
Skill #35: Understanding Basic Design Principles
Skill #34: Crowdsourcing Technical Communication
Skill #33: Getting Started with Open Data
Skill #32: Understanding Translation and Localization
Skilll #31: Choosing the Right Knowledge Base Software for Your Organization
Skill #30: Landing a Tech Writing Internship
Skill #29: Understanding Your Reader (as a Whole)
Skill #28: Researching as a Tech Writer
Skill #27: Contributing to GitHub
Skill #26: Getting Started in API Documentation
Skill #25: Nudging Users to Action Through Contextual Help
Finding Your Content DNA
Skill #23: Transitioning into Tech Writing from Very-Much-Not Tech Writing
Skill #22: Using Your Detective Skills as a Technical Writer
Create your
podcast in
minutes
It is Free
The Commercial Edge: Unleash the Power of People
The emPOWERed Half Hour
Reaching your Goals
Insights@work
The Ken Coleman Show
The Cardone Zone
The Wall Street Skinny