Documentation strategist is a new nomenclature for a class of technical authors who determine the plans and goals of documentation for a particular company. I did a search of the word in a couple of search engines, but I did not hit upon anything relevant. However, this does not mean that companies are not using documentation strategies.
In most companies, documentation strategies are evolved as inputs from both technical writers and their direct or indirect managers. For example, the decision not to revise a certain document to capture a new product defect is taken as a result of documentation strategy.
Why do we need documentation strategy?
Technical documentation is no longer seen as an afterthought of a product release. Good technical documentation has proved to not only reduce the volume of calls to contact centers, but also assist product support specialists in resolving customer conflicts.
Here is a good article that further explains the repercussions of cost cutting in the technical documentation field: http://www.technicalcommunicationcenter.com/2010/09/30/the-hidden-high-cost-of-cutting-down-on-documentation/
[When I was a technical resolution expert for a major computer company, I used to go to the Microsoft knowledge bases to find answers to any Windows related queries. Not only was I able to resolve my customer’s issue, but by forwarding the particular article to the customer, I ensured that he/she will not be calling again for the same issue.]
As the number of products from a particular company increase, so does the amount of documentation required to support the products. With the increase in the amount of documentation, the complexity increases.
There is a requirement to maintain consistent style and quality across all documentation of a particular company. Also, as a part of documentation strategy, one needs to look into minimalism and cost cutting.
Consider the following questions for the documentation requirements of XYZ product:
- How many document types does XYZ product need?
- How often will each document need to be revised?
- Are any or all of the documents required to be printed?
- How will the documents be delivered to the customer: online HTML, online PDF, documentation CD, etc?
- What authoring and production tools will be used in developing the documents?
- How are the documents going to be stored?
- What will be the documentation life cycle?
- Will the documents need localization?
The answers to all the above questions are decided by a documentation strategist. In essence, the decisions are taken based on cost and customer experience. A documentation strategist has liaisons with the engineering group, the legal department, the marketing group and the product support group to evolve decisions for a stable, cost saving and customer friendly documentation strategy.
Who makes a good documentation strategist?
Not just any technical writer be a documentation strategist. However, a documentation strategist must have a background in technical writing.
- Are you able to quickly analyze documentation requirements for products?
- Do you consistently think of how to make documentation processes more effective?
- Are you buried head-deep inside the products of your company or do you often do comparisons and explorations in documentation of other companies?
- Can you take decisions that can affect the whole documentation department of your company and base them upon sound logic and research?
- Are you a good communicator and not afraid to ask questions to people who might be higher up than you in the corporate ladder?
- Can you justify your decisions to the company big wigs and evolve a documentation strategy to ease not only your department but your customers?
If you answer yes to all of these questions, you are definitely on your way to becoming a document strategist. Congratulations!
