A Lighthouse in the Fog
Beyond Single Sourcing by William Hart-Davidson was a breath of fresh air for the topic of technical writers. Whether you are thinking about a career in technical writing, wary of your current job safety, or bored because you are stuck updating product bulletins for a conglomerate, Davidson creates an outline for the future. Granted theory is almost always shinier when it is discussed, the author lays out logical and plausible applications for expanding roles and responsibilities for technical communicators.
Davidson’s message stirred passion inside of me… my pupils dilated, my heart rate increased and my mind raced. I love an “idea-person” and the author is just that. In a world which can seem mostly cloudy, an economy that is only improving on TV, and a society where negativity is just easier, Davidson is the warm glow of a family room fireplace on a cold winter’s night. He neatly displays his vision on Table 5.1 (p136) which he organized into three rows: text-making, creation and management of information, and design and management of workflows and production models.
The first row of text-making relates to creating an environment for a company’s information to thrive and grow. The technical writer can create support processes such as templates, guidelines, and usability confirmation to help foster growth in the informational environment. The second row of the table describes how the technical writer is involved in the life cycle of the information. They are responsible for the quality, accessibility, and the upkeep of the information’s environment. The third row deals with how human interaction and the information’s environment coexist. Having intimate knowledge of the information and its environment puts the technical writer in a unique position to refine work processes, improve workflow, and develop training materials.
Davidson has presented three intertwined objectives for identifying, developing, and managing a company’s information. Each have a number of possible job titles attached to them and all of them relate to how a technical writer views, interprets, and creates information. A growing question among companies in a “net profit era” is “what does a technical writer do?”. Individually, that is a question each person must answer themselves. However, Davidson offers a clear idea of what technical writers are capable of. Personally, I would not consider myself a “glass half-full” or “glass-half empty” person, but rather a “the glass isn’t big enough” kind of guy… and Davidson fills me up.