wiki@rnd

Team wiki is the first small project I'd like to have for the team. Although it doesn't get well maintained eventually, I still think it was a must-have.

The biggest hurdle to a successful internal wiki for a 20 person team is creating a culture of documentation. So if I were to give you the shortest answer, it would your executive team’s favorite solution. Getting leadership to use the wiki, especially early on, will set the precedent that everyone else should be sharing too. (https://www.quora.com/What-are-the-best-internal-wiki-solutions-for-a-20-person-startup-Why)

What should be put on the team wiki?

• all the usual problems

Which features are must-haves for the team wiki?

• simple to use

• support to search the keywords (almost-match)

• support edits and comments (and control who edited what)

• support multiple groups

Other good quotes:

• Smart - The problems with wikis is the information in them goes out of date. Modern wikis have smart automation built into them that help you keep your pages updated with notifications from AI or your teammates, and will also help you keep organized with archive suggestions.

• Connected - You want your wiki connected to all your other tools you use to communicate and collaborate. That means you want it hooked up to your chat tool (Slack, Microsoft Teams, etc) and your departmental level collaboration tools like Github, Zendesk, Salesforce, HubSpot, etc. Ideally you can embed content from those pay-per-user systems that silo your information to that department into your wiki pages to share cross-functionally. The content should also automatically update so you don’t have to update it in two places.