Technical Writing

I have been a technical writer for 6 years now, working for 3 companies in this capacity. I have worked on user guides, help files, marketing materials, internal ISO documents, custom templates, presentations, and CBT/WBT (Computer and Web-Based Training). Technical Writing is usually viewed by most as a very dry, logical and dull field of work; something along the lines of accounting. This is certainly not the case. It is more about problem-solving, creative use of imagery and diagrams to support text, and challenges to engage the reader.

A good document is more than just a line item on a company's sale. It can make or break the sale. A Well-written and well-understood Help File can reduce calls to a company's customer service department. A company-wide custom template can enhance internal productivity. A well-formatted Training DVD can separate your company from the competition. In short, a good Technical Writer is proficient in all these areas, and is a valuable asset to any company.

As far as technologies used, they tend to vary based on the project. For a straight user or internal manual, I may opt to use MicroSoft Word and VBA scripting to acheive the desired result, along with Adobe Photoshop, Visio, and SnagIt screen capture software to work with diagrams and imagery. From there, the final copy is usually produced in a secure or unsecure Adobe Acrobat (PDF) document, depending on the needs.

Help Files are a different story. Of late, rumor has it that RoboHelp and RoboHTML are products that will be discontinued from future use. That being the case, I am working towards learning XML as the new defacto language for help. It seems to be the direction most companies are taking. Luckily, my knowledge of HTML/XHTML proves useful in this capacity. It's an ongoing learning process.