Not just anyone, with any background, or any training, can do a fine job of programming. Programmers know this, but then why is it that they think that anyone picked off the street can do documentation?
Gerald Weinberg
Technical communication is the bridge that arches from product engineers to customers. This bridge is built by people called technical writers. They are the ones who design, create and deliver product documentation in various media formats: paper, help systems, web sites, graphics, etc. Typically technical writers work as part of the development team and their work is often underestimated or invisible – until the final release date, when the product appears fully packed and ready to be shipped or downloaded by the customer. It is a myth that “customers don’t read documentation”. They do. But they turn to technical documentation out of need to learn something specific and when they have a problem to solve. And if they can’t find to do that, you can be sure the support center will receive a lot of calls from unhappy customers. On the other hand – the right documentation delivered in the right form and at the right place – can make the difference between a successful, working product and a failure to deliver on promises.
