Expertise versus Skill: The Dichotomy of a Technical Communicator
When I first began my journey to finding a master’s program that had to do with something around technical communication, I kept telling myself it was to gain more validity with my career and give me the necessary expertise that I needed. Within my role, it has always been a struggle to claim my position as a real “job” and not just something that needs to be done, for example, drafting e-mails to the rest of the organization about a particular issue that occurred in relation to technology.
But this idea of a dichotomy came up for me in a recent article I had written for another assignment. When does technical communication change from just being a skill to it being considered an expertise or career? This is often something I have contemplated, but it seems to be coming up and more and more, even in Pigg’s article on distributed work. As Pigg discussed the skills needed for technical communication, one of the problems she conjured was that “technical communicators’ expertise is threatened to be reduced to functional technological skill (p. 72).
I often ask myself what does technical communication really mean to me? Of course, this is in the context of my own work environment and experiences that I have had, but I am beginning to wonder if that question is ever attainable? As we think about the growth in technology, it wasn’t until about the last 40-50 years that modern day technology really began to shape our human culture. With this sharp increase it will only began to increase at the same rapid pace. So what is our role as technical communicators within these changes? Can we even bare to handle all aspects? As organizations continue to grow, consumers begin adapting new technologies, and distribution begins to happen in our everyday lives, the role of technical communication will become even more distributed.
In looking at my current organization there are many areas where the skillset of a technical communicator is needed but often times it is covered by a technical, or even non-technical, subject matter expert. For instance, our business analysts are often reaching out to members of our organization to gather requirements for technical projects. The work they do surely involves some type of technical communication skill but it is not something they are necessarily trained in.
I saw this Bruce Lee quote and it really seemed to tie in nicely with my article this week. As I thought about this idea of skillset versus expertise, I actually disagreed with Lee’s quote. It has to take expertise to know 10,000 different kicks versus, being able to do one really well (which is a skill in and of itself). Practice makes perfect, right?
In correlation with Pigg’s problem statement referenced earlier, I believe it is important that we distinguish between what skill and expertise mean for the field of technical communication. Otherwise, I too fear, in alignment with the work Slattery conducted (Pigg, 2014), that all technical communication roles will be subjected to a skill rather than an expertise.