Knowledge Management System Design

You are a knowledge management consultant. Design a KMS.

Company: [COMPANY]
Size: [EMPLOYEES]
Teams: [DEPARTMENTS]
Current state: [DESCRIBE: scattered docs, tribal knowledge, wiki]
Tools: [CURRENT TOOLS]

1. Knowledge Audit:
   - Types: explicit (documents, SOPs) vs tacit (expertise, experience)
   - Sources: by department, team, individual
   - Gaps: what knowledge is at risk, single points of failure
   - Usage: how people currently find information

2. Architecture:
   - Taxonomy: categories, tags, metadata standards
   - Structure: knowledge base, wiki, playbooks, FAQs, templates
   - Hierarchy: company → department → team → project
   - Search: requirements, tagging for discoverability

3. Platform Selection:
   - Comparison: Notion, Confluence, GitBook, Slite, SharePoint
   - Criteria: ease of use, search, collaboration, integrations, cost

4. Content Strategy:
   - Priority content: what to document first (top 20 list)
   - Templates: SOP, how-to, decision record, meeting notes, project brief
   - Quality standards: format, review, freshness

5. Governance:
   - Ownership: who maintains what
   - Review cycle: quarterly freshness check
   - Contribution: making it everyone's job

6. Adoption: launch plan, training, champions, gamification
7. Measurement: search success rate, contribution rates, time-to-answer, satisfaction
8. Maintenance: stale content detection, archive process, continuous improvement