Structured documentation is such a benefit toward this, and also such a controversy within teams.
Aside from the many standards for structure and the challenges of info architecture, there are a surprising number of technical writers who are hard to convince, or cannot be convinced, to write within any sort of structure or template. Either they have to be sold on it constantly, or cut loose or moved away from product docs and toward blogs or training materials.
A writer who can not only work within a structure but also can appreciate and leverage it is incredibly valuable to a docs team, and I believe the pipeline that develops candidates for technical writing doesn't prepare folks for how much weight this carries.
Aside from the many standards for structure and the challenges of info architecture, there are a surprising number of technical writers who are hard to convince, or cannot be convinced, to write within any sort of structure or template. Either they have to be sold on it constantly, or cut loose or moved away from product docs and toward blogs or training materials.
A writer who can not only work within a structure but also can appreciate and leverage it is incredibly valuable to a docs team, and I believe the pipeline that develops candidates for technical writing doesn't prepare folks for how much weight this carries.