I was surfing through a client’s website today trying to re-familiarize myself with some content for an upcoming project. They have approached me about re-writing some web content, updating some articles, and writing some new material to support new products and marketing initiatives. It was interesting to see the differences in writing styles, conceptual approach, depth and perspective between several different documents related to similar products and technologies. Some were obviously written some time ago, and described older technologies as if they were on the cutting edge. Unfortunately there was no indication of when the articles were written, who wrote them, exactly who they were written for, or their specific purpose. Obviously, several different writers created the documents, and I would guess that some were engineers, others were marketing people, and at least one was a technical writer. (I know that because I wrote some of them.)
A couple of thoughts struck me as I worked my way through these documents. This client believes strongly in information-based marketing. They provide value to their customers by supporting their products with lots of online information (as well as great telephone support according to testimonials from satisfied customers). Their plan to update the information shows that they have recognized that the content must be up-to-date and consistent in style, focus, and technical level. On the other hand, their products connect to legacy equipment, so their documentation must provide historical information and perspective. The upshot of this is that most of the older information does not go out of date but it must be consistent in style and format with the more recent content to present a professional face to their customers.
This led me to several general conclusions, some of which may apply to you:
It’s important to clarify the purposes and goals of your online document library. For each document updated or created, you need to ask yourself several questions. Is this document primarily a marketing document? Is it a technical support document? Is it educational/informational? Is it procedural? The answers to these questions will determine the perspective, depth and format. It will also help determine who is responsible for the content.
You need to have a clear and complete in-house style guide to ensure consistency. Engineers and technologists are intelligent, skilled and competent at their field of expertise. But not all of them are great communicators, and if you give six of them the task of creating a document you will have six different document styles and structures. The same holds true for sales and marketing people. Often, even if the final documentation is created by a technical writer, a lot of the early content may be produced by an engineer or marketing person. A standardized, in-house style guide will help you to start from the right place and reduce the amount of editing needed later.
You need to create an environment that supports ongoing updating of your documentation. Probably every organization that uses documentation has this challenge. It may be possible to just archive documents that support discontinued products, but the documentation supporting current products should be up to date and consistent. The idea that you will put a “push” on updating the old stuff and then you will be done just isn’t realistic. There will always be tweaks and updates to do.
You need to include a competent technical communicator. Whether you maintain an ongoing working relationship with a freelancer, or employ a full time tech writer, you need the consistent input and expertise that comes from someone who creates documentation professionally. It’s not just expertise; it’s a matter of focus and perspective. Your engineering personnel will ensure the technical content is correct, and your marketing people will watch for a consistent marketing message. Your technical writer will focus on making sure the final product is clear, consistent, and effective.
Sphere: Related Content