What is the future of technical writing? The answer is interactivity. The phenomenon of Web 2.0 has converted Web surfers into Web content providers. People don't just browse the Web anymore, they get involved. They post their photos on flickr, track their movements on twitter, interact with their friends on facebook, review books and CDs on amazon, and comment on their favorite blogs. Many of them probably blog themselves. Today's user expects to reach out to companies whose products he or she buys and uses, and they expect solutions if they have a question or a problem.
As a technical writer, how can you make your documentation more accessible to your users while adding value to your products and contributing to the Company's bottom line? Start a technical support blog. We've talked before about the advantages that blogs can offer your users and your Company. They are a great opportunity to learn what your customers think about the Company's products and what experiences they are having with them. Based on comments that you receive, you will be able to deliver solutions that you know people need, and have the chance to pass user feedback to your design and development teams. Here are the things you'll need to put in place to start your own technical writing blog.