I'm the founder of Slite, a tool often used for wikis, knowledge bases and other form of documentation.
We work hard on making sure that our customers have by default their documentation up to date, and an easy way to groom it when needed.
I saw in hundreds of user interviews that the way for companies to handle knowledge management was often not very shiny.
- The honeymoon of new documentation, lasting for 6 months, after which teams realise there starts to be pollution, outdated answers
- A person is the end responsible, but not the matter expert, which makes it impossible to know what to update
- End users read documents outdated, lose trust in the KB and never come back
While I believe the tool has a lot of responsibility (we actively work on it and have already released great capabilities there), I'd love to hear from others how you address (or not) this problem.
Shoot your best practices π