A perennial question in the technical communication community is how to justify our work in financial terms that management will understand. One partial answer is to consider potential consequences of putting insufficient resources into technical documentation. What happens if the material is poorly written, or not written at all? Consequences can range from unhappy customers to wasted employee time to debilitating lawsuits—and worse. Joseph Devney uses statistics and real-life examples to illustrate some of the risks of having inadequate documentation.
Visiting Dojo Expert
Joseph Devney, M.A., is an STC Fellow and president of the Berkeley chapter. He has seen his share of bad documentation, and done his best to improve it. Joe has been a guest speaker at several STC chapters and for other organizations, and taught document design at San Francisco State University
Watch the Videos
Part 1: Risks and Consequences
Recorded: November 2014
Part 2: Stories and Examples
Recorded: May 2015
You might also be interested in...
Topic Writing Without Borders
Janice Summers, Single-Sourcing Solutions
Who Are You? (I Really Wanna Know)
Chris Hester, Red Desk Studio
Inside Out or Outside In
Liz Fraley, Single-Sourcing Solutions
Key Concepts:
best practices, content strategy, make your business case, single-sourcing
Filed under:
About the TC Dojo
At the TC Dojo, you pick the topics and we find the experts. Join our mailing list so you can attend the next one live. After all, you can't ask questions of a video.
Trackbacks/Pingbacks