IMO you need to keep it small and active and if you have old documentation you need to have the courage to delete it, or at least move it to some archived knowl

IMO you need to keep it small and active and if you have old documentation you need to have the courage to delete it, or at least move it to some archived knowledge base that doesn't pollute the search space of whatever you're using. The way knowledge bases die is they get cluttered up with irrelevant information from years ago which someone wants to cling to because somewhere in the mountains of useless information there might be that one gem which they cannot fathom throwing away, even though they don't know what it is. There's a really common perceptual distortion here where people dramatically overvalue that one piece of information they might throw away vs. the corrosive effect of all the information which is crap (and the enormous effort required to sift through every single piece of information and one-by-one search for that gem and rescue it rather than just bulk tossing away things that are in areas which never get touched). Which is not talking about the system which is ten years old which was documented five years ago, which every year is super critical to understand how to maintain it or whatever. But you know where that documentation is at because it saves your ass relatively repetitively. It is everything else that was written 5+ years ago that you've never once looked at which is the problem.