Every organisation has institutional knowledge that is probably written down somewhere, in some database, exactly where the team member who needs it to complete her task can’t find it when she needs it.
And the same team member probably finds herself performing tasks repeatedly that would be made much easier if all of the information she needed was in one place.
A central organisation wiki is storage place for all of the relevant information that your entire organisation needs to do its job properly. It can encourage team collaboration, make hiring temps easier, reduce the risk of losing institutional knowledge when a key team member leaves and above all provide a more efficient way to keep track of the organisation’s information.
Having an internal wiki reduces operational risk considerably. If you are using something like Atlassian Confluence you can set permissions so users can only access and contribute to things they need to. You can therefore prevent people stumbling across sensitive Word documents or Excel spreadsheets when trawling through files accessible to all team members.
Having a central repository for all of your organisation’s information makes it far easier to conduct induction training for new team members, keep everyone on the same page and reduce the risk of information silos being formed between team members or different teams.
In this day and age, not taking advantage of tools like a central organisation wiki is risky business. If you’re running a support system and find yourself opening up Word documents when there could simply be a Wiki page with the same information, you are costing your organisation a lot of unnecessary time and money.