I've seen companies use Confluence and Google Docs as internal documentation platforms, both worked fine. Having said that, it's not the tools which are intere

I've seen companies use Confluence and Google Docs as internal documentation platforms, both worked fine. Having said that, it's not the tools which are interesting in any discussion of documentation. The tools will cheerfully help you produce a royal mess of out of date, badly organized docs. You need to have processes in place to make the information accessible and useful. Get disciplined about requiring a canonical document for every current business process and project. That should be part of your project planning. Then have a requirement that the docs be kept up to date as things change. Basically think of it as the equivalent of devops run books/checklists, but more broadly applied. The specific tools to get there are less interesting - it can be done with a set of version controlled text files well organized on disk and searchable with grep if it comes to that.