Whenever a company grows, it also accumulates a wealth of knowledge, from processes and best practices to institutional culture.
Over time, these valuable stores of team knowledge can be scattered across the organization.
A company wiki aims to solve this problem by collecting all the information into a centralized repository, thus providing an unified and easily accessible resource for everyone.
What is a Company Wiki?
A company wiki (also known as a business wiki) is a repository of internal information. It aims to provide a single source of truth that everyone can refer to, collaborate on, or update as necessary.
The term comes from wiki, a server program that allows users to collaborate on website content. The difference is that company wikis are closed systems designed for internal use by employees, in contrast to wiki sites like Wikipedia and customer portals.
Company Wiki vs Blog: What’s the Difference?
A blog is owned by one person, or in a business context, one department. It can solicit articles for contribution by subject matter experts, but at the end of the day updating and editing falls on the owners themselves.
A wiki is designed to be crowd-sourced: everyone contributes and shares company knowledge by writing content, editing or updating it. While there may be editors in charge of proofreading and maintaining the site, all members have a say in content creation and revision.
Company Wiki vs Knowledge Base: What’s the Difference?
There are times when company wikis are used interchangeably with internal knowledge bases. However, there is a major difference between the two.
Wikis have a much more collaborative design. Contributors can submit new content or edit existing entries, and have them published instantly. Moderation comes after, when editors review the change and either approve them or roll it back to the previous version. It also uses peer review by colleagues to ensure the content or changes remain factual. This allows the wiki to build new content at a faster rate and remain up-to-date, at the potential expense of accuracy.
An internal knowledge base has stricter controls. New submissions or changes to existing entries must be reviewed first before they can take effect.
While this makes it slower, it also means the knowledge base is much more reliable and authoritative.
What are the Benefits of a Company Wiki?
Lots of tools try to be all-in-one, but then everyone is all-out confused. A company wiki deserves to always have a place in your tech stack. Here’s why:
1. Better productivity
By collecting all knowledge in a single repository, people waste less time hunting for information or seeking help from colleagues.
2. Higher job satisfaction
Employees are less likely to be frustrated when answers are just one click away. In addition, they feel more involved and relevant by being able to contribute to the wiki. A study of IBM’s internal wiki found that enjoyment was the primary driver for employee participation in the project.
3. Single source of truth
The wiki’s peer review process allows everyone to agree on a unified version and single source of truth for everything, whether it’s documents, procedures, best practices, or other job responsibilities. This enables processes to become more streamlined and promote best practices. Imagine how that changes how HR policies are accessed and where customer service answers are stored.
4. Easier onboarding
Training and recruitment are improved when onboarding materials are presented in one convenient location.
5. Faster learning
Employees learn new methods and achieve lateral growth faster when information is placed at their fingertips. Think improved and faster teamwork.
6. Valuable knowledge retention
Priceless intangibles like experiences and better ways of doing things are retained within the organization, even when employees and veteran workers go. More efficiency is achieved.
Want to bolster your existing wiki’s effectiveness? check out Wiki Best Practices: Top 10 Tips.
How do you choose the right wiki for your company?
When selecting an internal wiki software, you must remember two things: it will function as the company’s Bible or Wikipedia, and it will be used by everyone, not just a select few people or departments. Therefore, the objective is to make it as easy, painless, and convenient to use as possible.
These are the features a wiki needs to do that.
- It must have an intuitive interface and navigation.
- There must be a good search function that allows users to locate information quickly and reliably.
- Content hierarchy and tagging allow for quicker navigation.
- Easy editing and linking even by non-technical users.
- A strong access rights management
- It can be integrated with existing company software, to allow users to quickly access the wiki without leaving productivity apps.
Examples of useful company wiki integrations:
1. Slack integration
If your team communicates by Slack, you can also connect your company wiki and add pages or ask questions directly from Slack.
Here’s how it works in Tettra:
2. Microsoft Teams integration
Integrating Tettra with Microsoft Teams helps you answer repetitive questions and onboard new teammates faster. You can use the Tettrabot to search, share, and manage internal knowledge from all your channels, ensuring that your team actually uses your documentation.
Here’s how it works in Tettra:
How do you set up a company wiki?
An internal wiki represents a major project, one that calls for all members of the organization to participate and be invested in. However, the end product makes it worthwhile for everyone.
1. Prepare for the wiki project
- Get the buy-in of everyone in your organization. As the name suggests, an internal wiki is a company-wide project that relies on members’ involvement, so everyone from the top brass to the newest recruit must be sufficiently aware and hyped up.
2. Prepare for the types of content
- Create templates that everyone can use for different types of content. These can be FAQs, How to, Step by Step guides, or even Audio / Video recordings.
- Tettra provides a number of convenient templates you can use for your wiki. They are even grouped by department!
3. Gather resources
- Pinpoint the institutional knowledge that should be stored, from individual job responsibilities to methodologies, working relationships, even team values and culture.
- To streamline the process, designate project coordinators for each team and department. While everyone is expected to contribute, these coordinators are in charge of tracking the progress for their team, ensuring the content is relevant and accurate, and that all the subject matter expertise of their department is covered in the wiki.
4. Set up wiki access rights
- While wikis rely on peer review, it’s always a good idea to have editors. Assign designated reviewers, and make sure they are enthused about the project so they continually invest time moderating content.
- Configure roles and permissions based on access level or need to know, if required.
5. Populate the content
- Test the system by having the project coordinators get first crack at the wiki. Let them post their own content and edit each other’s submissions. This way they can also evaluate the wiki’s performance, moderation and change log features.
- With initial content up, invite everyone to submit their own contributions.
- Use tags and categories to make information easier to find.
- Encourage links to relevant works.
Once you’ve got the system up and running, congratulations! You now have your very own company wiki!
It’s easy to use Tettra for your business and company wiki
At Tettra, we’ve built a business wiki that is simple, smart, and connected. It will help your team share and access collective knowledge across teams or your whole company.
Tettra is an AI-powered knowledge management system that helps you curate important company information into a knowledge base, use it to answer repetitive questions in Slack and MS Teams and keep it up-to-date, organized, and complete with automation.
With Tettra, you’ll get:
- Q&A workflow to capture questions
- AI-powered knowledge base to document answers
- Knowledge management features to keep content up to date.
- Integrations with your existing tools like Slack, MS Teams, Google Drive and more to make sure your team actually uses Tettra
The sooner you start documenting, the better off your team will be. Ideally, you started documenting things from day one. But if not, there’s no better day to start than today.
Your entire team will benefit from being able to share and find the knowledge they need.