Here’s the scenario: You’re finishing up your latest HTML Help project…no more late nights or weekends…back to a “normal” 50-hour work week. That’s when the development team lead strolls into your ...

Editors Note: This Business Requirements Document, or BRD Template is one in a series of templates to help readers plan and manage communications and content management activities, resources and ...

TechWhirl is an online resource for anyone interested in the world of Content Management and Technical Communication. Experienced veterans, up-and-coming professionals, students, and leaders in the ...

Editor’s Note: The following piece by Tom Murrell on creating a t-letter for your jobs search is part of our collection of “classics”–articles that stand the test of time no matter how many ...

Editor’s Note: The following piece by Jean Hollis Weber is part of our collection of “classics”–articles that stand the test of time no matter how many technologies come and go. In recurring ...

Technical communications as a field within business communications encompasses a range of disciplines that work together to communicate complex information to those who need it to accomplish a defined ...

Editor’s Note: The following piece, by Jean Hollis Weber, is part of our collection of “classics”–articles that stand the test of time no matter how many technologies come and go. Don’t forget to ...

Technical writing is sometimes defined as simplifying the complex. Inherent in such a concise and deceptively simple definition is a whole range of skills and characteristics that address nearly every ...

Editors Note: This traditional documentation plan is one in a series of templates to help readers plan and manage communications and content management activities, resources and deliverables. We ...

Editor’s note: A slightly different version of this article originally appeared in the May 2017 issue of Intercom magazine, published by the Society for Technical Communication. I’ll never forget the ...

One common criticism of technical content heard from users is that they are only getting information they already know—and they’re not particularly interested in consuming this “obvious” content.

Nobody reads the documentation. We’ve all heard it. We have all had our work dismissed with this simple half-truth. How should we respond? If it were simply not true, the response would be easy enough ...