We all know that the quality of our documentation and the process for getting articles ready for production are very important. Recently, we moved the technical writer position to Support Ops, with the goal of providing tech writing services for all devtools products and achieching scale. In practice, this change means that we need a new process. But before that, some context.
Until recently our approach to collaboration with technical writers was to prepare text draft and assign it to Desi, for what would often turn out to be a complete rewrite. During complete rewrite however, parts of the technical meaning could get lost, which often lead to one more iteration with the individual that is writing the article. While this approach worked when the scope was specific product or two, it won't work for the bigger organization.
With this previous experience in mind, a characteristics of process that could work at scale and reinforce positive feedback loop are:
- no bottlenecks, i.e. one person responsible for