Skip to content
Playbook
IntermediateHRPeopleOpsManager

Knowledge management strategy: making the wiki the source of truth

Most wikis die the same way — too many half-written pages, no owners, search that returns garbage. Here's the strategy: structure, ownership, freshness, and…

9 min read
On this page
60-Second Summary
  • Three layers: source of truth (policy), how-we-work (process), reference (FAQ + onboarding).
  • Every page has a named owner + review date. Unowned = decoration.
  • Stale pages get auto-flagged at 6 months; archived at 12 if not refreshed.
  • Measure search success rate, not page count.

Knowledge management isn't a tool problem — it's a discipline problem. The best wiki, unmaintained, is worse than no wiki at all because people stop trusting search results.

Three layers

LayerExamplesUpdate cadence
Source of truthPolicy, comp bands, benefits, leveling rubricQuarterly review
How we workOnboarding paths, process docs, runbooksTwice a year
ReferenceFAQs, glossary, links, decisions archiveOn change

Ownership + freshness

  • Every page has a named owner (person, not team).
  • Every page has a 'last reviewed' date.
  • Auto-flag pages unedited > 6 months.
  • Auto-archive flagged pages after 12 months if not refreshed.
  • Quarterly 'wiki gardening' day — 2 hours per team.

Search that works

  1. Page titles are search queries — 'How to request PTO', not 'PTO Policy v3.2'.
  2. First paragraph answers the question. Detail goes below.
  3. Consistent tagging (a small taxonomy beats a large free-for-all).
  4. Promote 'top hits' on the home page based on actual search volume.

What good looks like

  • Search success rate >70% (user found something they clicked).
  • Edit-to-stale ratio: more edits than newly-flagged-stale pages each month.
  • <5% duplicate-content rate for top 50 topics.
  • New-hire feedback: 'I found what I needed' >80%.
Written by Pawan Joshi.Sources cited inline.
First published 16 Jun 2026See site changelog →