Technical communication - Category Home
Technical communication - Topics
Is documentation a cost center or does it cut support tickets?
Who reads the manual before calling support?
What does a docs-as-code pipeline change for a writing team?
How do you write instructions for a user who skips every step?
Why does a word-for-word translated manual still confuse users?
How do you test whether a manual actually works?
Why documentation rots faster than the code it describes
How do you onboard a developer into a codebase nobody documented
Dishwasher salt is not an upsell and the manual buries the reason
How much of a support call is caused by confusing wording?
Who decides which error messages a user is allowed to see?
Why do API docs go stale within weeks of a release?
What does a technical writer actually do all day?
Why is the safety warning on page 42 and not on page one?
Every combined outline ends up with a catch-all section for entries that will not fit
Why do safety sign standards differ between industries?
Bandwidth means three different numbers depending on who is asking
Why do warning symbols fail in cultures that read them differently?
Glossary entries for platform rarely survive contact with two industries
Translating a technology glossary breaks on terms with no equivalent in the target language
A glossary of technology needs dated entries because meanings drift within a decade
Technical writers are the first role cut and the last one missed