The solution are text-files, automation and version-control. Write scripts which are regularly automatically export all data, configs, communication, etc. into

The solution are text-files, automation and version-control. Write scripts which are regularly automatically export all data, configs, communication, etc. into a centralized storage which is under version control with an automatic commit every day, which is also exported into a report of that day's changes. Then use grep or whatever to search it. People will not maintain knowledge bases unless you force them. So remove as much friction as possible and make as accessible as possible. Hence, the automation and textiles. It doesn't need to be plaintext, just something universal and human-readable. Could be formatted in markdown, yaml, json, be single email-files, everything you can find with simple tools and make connections with. The version-control and it's report then will allow you to follow the trail of work, to discover what was discussed and change around the same time, to find connections. And it's never wrong to have a reversible history of your stuff. And maybe along the way you can motivate people to also write some proper documentation here and there, and add some more fancy tools on-top.