Internal Wikis
Internal wikis are collaborative web-based platforms that serve as central repositories for storing, organising, and sharing information within an organisation. They empower autonomous teams to collectively document knowledge, processes, and best practices, facilitating communication and collaboration across different departments and projects.
Purpose
Wikis provide a single source of truth for essential information, reducing redundancy and ensuring everyone has access to the latest updates. The ability to collectively edit and contribute to content fosters knowledge sharing and promotes collective ownership of information.
Format
| Format | Description |
|---|---|
| Project Pages | Dedicated pages for documenting specific projects, outlining goals, procedures, and relevant resources. |
| Team Playbooks | Centralised repositories for team-specific processes, best practices, and troubleshooting guides. |
| Knowledge Base Articles | In-depth explanations of technical concepts, internal tools, and frequently asked questions. |
| Meeting Notes and Agendas | Collaborative spaces for capturing meeting discussions, decisions, and action items. |
| Resource Libraries | Centralised storage for shared documents, code snippets, and other relevant materials. |
Anti-patterns
- Outdated Content: Not regularly updating the wiki leads to obsolete information, reducing its usefulness.
- Poor organisation: A lack of structure or categorisation makes it difficult for users to find information.
- Limited Accessibility: Restricting access too much can hinder the sharing and growth of knowledge within the organisation.
- Lack of Engagement: Failing to encourage contributions from all team members can result in a wiki that reflects only a narrow perspective.
- Over-Complexity: Making the wiki too complicated to navigate or edit can deter users from contributing or using it as a resource.