My team probably has half our knowledge in our general dev chat on Teams. Nobody even tried to use that. Same, my team probably has most of our knowledge burie

My team probably has half our knowledge in our general dev chat on Teams. Nobody even tried to use that. Same, my team probably has most of our knowledge buried among the various document repos and wikis, but it's all at varying levels of out of date between a few days and a few years. The core of the problem, I think, is that the digesting and organizing of information has to happen somewhere. If you want to make it easy to dump info for the future, then you make it low friction to write it, but because nobody's taking time to organize it, it's going to be a pain for future readers to glean useful insight from it. On the other hand, if you require the writers to organize the info and occasionally update obsolete articles, it'll be much more useful for future readers, but it'll be much harder to contribute info in the first place. IMO the next big win on this problem will be whenever someone comes up with an actually good search engine to organize this sort of team info. Stack Overflow did a great job with public info by relying on Google for search, but there isn't really an equivalent for internal info. If we have this, we can rely a bit more on automation to reduce the amount of organizing the writers need to do in order to produce usable documentation.