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.

This is Part 1 of a two-part series:

  • Part 1: Risks and Consequences (this page)
  • Part 2: Stories and Examples (Coming in January!)


  • TC Dojo Open Session
  • Date: 6 October 2014, 9 AM Pacific/US
  • Audience: All
  • Cost: Free

About the Visiting Dojo Master

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 Video

Slides are not available

Get useful tips and valuable resources every month

Join the thousands who know just how much we share.

Powered by ConvertKit
%d bloggers like this: