A new breed of technical communicator
Posted by jebehles
If Part I of Rachel Spilka’s 2009 anthology Digital Literacy for Technical Communication was intended to frighten the reader of portents of being outsourced (and presumably destitute as a result), then Part II was meant to assuage some of those fears. In fact, my concerns about managers playing the “everyone can write” card was almost directly addressed by William Hart-Davidson in chapter 5, “Content Management”:
But managers do need to recognize the following: that writing needs to assume a high status in corporate work, and be viewed as a critical means to just about every organizational end. The lingering idea that writing is somehow a “basic skill” rather than an area of strategic activity for a whole enterprise sometimes causes managers to make poor choices…. Many see these as a chance to automate or, worse, eliminate the work that writing specialists do. I hope this chapter helps to dispel that myth and prevent such decisions. (pp. 141-2)
In other words the “writer” should be so much more than a writer. Hart-Davidson’s chapter describes how a technical communicator can pivot into any number of essential job roles related to the managing of content.
Similarly, in chapter 4, “Information Design,” Michael J. Salvo and Paula Rosinski argue that to be truly digitally literate, technical communicators must understand information design and information architecture and by doing so, remain relevant and vital to their organizations. In fact, they state that technical communicators have always had a greater task than writing alone: “Effective technical communication has never been simply about writing clearly, but rather, about effectively organizing written communication for future reference and application” (p. 123).
Both chapters agree that although writing is still essential, the structure, high-level design, usability, findability, and reusability are all vital parts of content generation. Technical communicators are uniquely suited and situation ensuring all of these needs are met while anticipating potential future needs.
Salvo and Rosinski provide several reasons why technical communicators are ready to evolve from content production to information architecture and design. First, technical communicators have historically applied effective design principles regardless of context (p. 106). Second, technical communicators understand historical principles of user-centered, which can be built upon to innovate, yet still advocate for the user (p. 106).
Finally, technical communicators have ensured that good design remained a focus, even as the scope of documentation evolved from simple content writing to building full Web sites. One part of this was making sure that design was driven by context; that is, the designs developed were appropriate for the context in which they would be viewed (p. 108).
Taken together, these three points argue that technical communicators can either call upon past experience, genres, and conventions and apply them to new contexts or develop new practices and styles for these contexts, all while anticipating and meet the user’s needs. They are able to effectively straddle the documentation of the past and the information design and architecture of the future. However, Salvo and Rosinsky point out, this requires that technical communicators maintain an ever-increasing knowledge of publication contexts—in other words, they must be digitally literate and remain so.
Returning to chapter 5, Hart-Davidson tells us, “Today’s technical writer… is typically expected to… perform a host of other tasks that relate directly to the management of content and not necessarily to its creation” (p. 128). In addition to content-creation tasks like writing or designing templates, the technical communicator must also manage the documentation, how individual pieces of documentation are related, and the workflows and production models used to produce and publish content.
When considered together, Hart-Davidson and Salvo and Rosinsky’s advice offers two ways technical communicators can remain relevant in a world that—regrettably—no longer values traditional writing or editing skills. The first is to shift from creating content to developing new, modern ways of presenting information in never-before-seen contexts—or adapting preexisting genres and conventions to these contexts. Second is to manage the content in addition to creating it—and also manage all aspects of content creation.
Combined, these new modes of technical communication should lead to a new breed of technical communicators that become future proof by continually adding new value to their organizations.
This site uses Akismet to reduce spam. Learn how your comment data is processed.