Just Write Click

Technical writing with Continuous Integration and docs-as-code

  • JustWriteClick
  • Contact
  • Books by Anne Gentle
  • Introducing Docs Like Code
You are here: Home / techpubs / How many roles can a documentation expert have in a company?

January 8, 2009 by annegentle

How many roles can a documentation expert have in a company?

How many roles can a documentation expert have in a company?

Harjot Dhodi asked, “What is the difference in the role of: Document Architect, Template Designer, Writer, Technical Editor, and Production Editor? Can a person be told to handle all these roles?” I’ll try to examine these roles one at a time, and then answer the final question last.

Document Architect – Typically this person has a “big picture” view of the documentation and how to organize it to fit the user’s needs. This role involves organizing, dictating what topics will be written, structuring the overall deliverables (especially if there are multiple deliverables such as online help and printed documentation). I would say this role is for a more experienced person who has been with the company a while and knows the business needs for the documentation.

Template Designer – This person knows the documentation tools well enough so that they can maintain and design templates used over and over for consistent documentation while authoring so that the out put look and feel is the same over and over. For example, the role would involve designing FrameMaker templates for books and chapters and styles for the authors to use while writing.

Writer – This person creates the content. They should be familiar with using the templates and the style guide for the company.

Technical Editor – This person reviews the content and may also maintain the style guide. Some times the term “technical” in an editor role means they will check the documents for consistency with the product and technical accuracy throughout the document. Grammar and style rules checking is also part of the responsibilities of this role.

Production Editor – This phrase is less familiar to me. I would imagine that this person reviews output for any errors and does link checking for online deliverables. I suppose it really depends on what deliverables are produced. The Production Editor may need to check CDs to ensure the documentation deliverable operates correctly on the CD. There could be a lot of editing and testing and checking on certain production deliverables.

Can a person be told to handle all these roles ?

I think one experienced person could handle all these roles, and a single person could learn one role at a time and just keep adding each role to their abilities. In my company we do not have separate editors so we must review each other’s content. We all write content, we all edit content, and we have a document architect and production editor who is most familiar with the content and production tool.

Does this help answer questions about documentation roles? I’d love to hear feedback from my blog readers as well – what have I missed or what additional roles might there be placed upon one person?

Related

Filed Under: techpubs Tagged With: architect, designer, documentation, editor, production, technical publications, template, writer

More reading

Bubble graph showing sources of developer support data

I’ve been thinking a lot about developer support at Cisco recently, especially for the way the world works today with multiple cloud providers. This post is a re-publish of my talk from over five years ago, but the techniques and tools for listening and helping others are still true today. At Rackspace, we watched several […]

Cisco DevNet is our developer program for outreach, education, and tools for developers at Cisco. From the beginning, the team has had a vision for how to run a developer program. Customers are first, and the team implements what Cisco customers need for automation, configuration, and deployment of our various offerings. Plus, the DevNet team […]

I had a great talk with Ellis Pratt of Cherryleaf Technical Writing consulting last week. Here are the show notes, full of links to all the topics we covered. Podcasts are great fun to listen to and participate in, if a bit nerve-wracking to think on your feet and make sure you answer questions succinctly […]

At the beginning of this year, I worked hard to summarize my thoughts on API documentation, continuous publishing, and technical accuracy for developer documentation. The result is an article on InfoQ.com, edited by Deepak Nadig, who also was forward-thinking in having me speak to a few teams at Intuit about API documentation coupled with code. Always […]

Recently on Just Write Click

  • A Flight of Static Site Generators: Sampling the Best for Documentation
  • Try a GPT about “Docs Like Code” to ask questions
  • Discipline and Diplomacy: Docs in the Open
  • Let’s Find Out: When Do Static Site Generators Do Rendering?
  • GitHub for Managing Tech Docs

Just Write Click in your Inbox

Enter your email address to subscribe to Just Write Click and receive notifications of new posts by email.

Read More

  • Privacy Policy
  • About Anne Gentle, developer experience expert
  • Books by Anne Gentle
    • Conversation and Community
    • Docs Like Code, a Book for Developers and Tech Writers
  • Woman in Tech Speaker Profile
  • Contact

Books

  • JustWriteClick
  • Contact
  • Books by Anne Gentle
  • Introducing Docs Like Code

Copyright © 2025 · WordPress · Log in