Our team struggles with outdated documentation - old version numbers, broken links, deprecated processes, old team member names, wrong orgs, worng product desc still in docs from 2022.
Can you be more specific about what documentation we're talking about? Public and customer facing product docs? Internal for developers?
You're on Confluence, which is a good start. There are apps that can help (Scroll Documents with versioning and version management), various content management apps that nag you when a page is not updated for XY months.
But tooling alone is not a universal savior.
You need to set up process and ensure that information flows from product managers to devs to writers and back. DocOps methodology is great for this - documentation is a part of the product, doc tickets are treated as any dev/QA ticket, writers are assigned to specific teams and attend all agile rituals.
In other words, you need to set up a viable documentation life cycle management routine.
We also have content owners who are responsible for preforming content audits and ensuring that content is up to date. Out product documentation is regularly updated by a team that is associated with every project. The project provides the changes that are incorporated into the product documentation and then reviewed before publishing. We use comala document management to help with the review process. We used to use better content and archiving for confluence and it had some really nice features but we do not have it due to cost saving measures. I would recommend it though.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.