We add value! Don’t outsource technical communication!
I was struck by R. Stanley Dicks’ article (chapter 2 in Spilka’s book), particularly how technical communicators must always be defending their role in the company. I can see how sometimes management can wonder what “technical communication” really is, especially when it touches so many other aspects of a company–why can’t technical communication fold into the other departments and eliminate the formal technical communication job title?
This has happened, with technical communication splitting into two general tracks, “design and programming of information databases and the other focused on providing content for these databases” (Carliner, ch 1 in Spilkea’s book, p 29). User Experience experts, information design, documentation divas, information technology, all have cuttings from technical communication. So why not eliminate the formal technical communication discipline when it’s grafted into all aspects of a company already?
In my opinion, no. we need technical communicators–we need us! While there are aspects of technical communication in other disciplines, technical communicators have the vision and distance from one particular area to consider the implications of audience. We are the users’ advocate first and foremost, and our whole goal is to see how we can get and retain users. While IT and other areas greatly contribute to this end goal, it’s in the company’s interest to keep technical communicators around, and in house to successfully reach as many audiences as possible. Back in Dicks’ article, he writes that the workers with the most value are those that “analyze, synthesize, combine, rearrange, develop, design, and deliver information to specific audiences for specific purposes” (p. 54). That’s how technical communicators add value.