Full disclosure: I’m one of the founders of a product that lets you create a wiki on google drive (https://kbee.app https://kbee.app). We’ve been live for over

Full disclosure: I’m one of the founders of a product that lets you create a wiki on google drive (https://kbee.app https://kbee.app). We’ve been live for over 3 months and have heard first-hand about how hard it is to get everyone in your org to contribute to your wiki. In our experience/research, what we learned was that most folks within an organization are either: a) too intimidated by the tools they need to learn/master to contribute to their company wiki or b) too limited with their bandwidth to actually go through the process of updating your wiki using the tools you’ve provided. This is usually what leads to the situations you’re talking about. Here’s what we’ve found works in terms of creating a culture of documentation where everyone feels empowered to contribute to your wiki: 1. Use a wiki product that both the technical and non-technical employees feel comfortable using. This is super important. If the least-technically savvy teammate in your organization can not successfully use and contribute to your wiki, they won’t use it. This influence will spread to other team members as well and then your wiki will quickly became stale and irrelevant 2. Set clear expectations around how you expect documentation to be formatted and presented in your wiki. This may be something a senior leader has to help enforce/kickoff. Give folks examples and scaffolding to use to create their own articles. this introduces a level of standardization and sets expectations for what is acceptable in the wiki. It also enforces a cultural expectation of how your organization treats documentation 3. Make referring to the documentation first a company-wide initiative. A great example of this is (cliché but true) how Amazon asks for one-pagers on a topic before the start of any meetings. Let me know if you have any feedback or questions. We love sharing what we've learned.