I spend most of my time on this blog trying to give tips and tricks on how to improve as a technical writer. But at times, we simply need examples of what not to do. Today, we conclude the story of the worst technical writing coworker I’ve ever dealt with. Out of respect for those involved, names have been changed. Out of respect for you, everything else is told exactly as it occurred. The six-part series ends here.
Plain and simple: offices should have a standard look and feel for their documents. This gives documentation a recognizable identity and communicates to the audience that what they’re reading is updated and relevant. Ideally, this is achieved by developing and maintaining templates for office use. These templates could be for memos, procedures, meeting minutes, or any other documentation. So if you’re starting from scratch, how do you put together templates that are useful?
Here you are! My ultimate list of techcomm resources. See something I missed? Let me know in the comments! Based on your responses, I’ll be posting updates to add more of the people and sites you have to know if you’re going to be in the techcomm world.