mem1.wiki

Anti-patterns

Anti-pattern

The read-only wiki nobody updates

The Confluence / Notion / wiki space that everyone references and nobody edits. Drifts from reality, nobody trusts it, but it stays up because removing it feels worse than ignoring it. The default end state of most team knowledge bases.

Taxonomy
anti_patterns.governance
Severity
catastrophic
Symptom
New hires are told "everything is in the wiki", then 30 minutes later told "actually, ask in Slack". Pages have a 2023 timestamp and reference a service that was deprecated last summer. Edit history shows one author, two years ago.
Root cause
Knowledge work was capture-only. No incentive, ritual, or process owner makes editing the wiki part of finishing a task. The cost of writing is paid by the author; the cost of staleness is paid by future readers — a classic externality.
Fix
Make wiki updates a step in the workflow that produced the change. Named owner per page. Visible decay timestamps. Mass-archive unowned pages. Smaller wiki, higher trust.
First documented
2010

How it presents

Why it always wins

Three forces push every team wiki toward this failure mode:

  1. Capture is free, maintenance is expensive. Writing a page is one person’s afternoon. Keeping 200 pages truthful is permanent overhead nobody is staffed for.
  2. Tools optimise for capture. Notion, Confluence, and the rest make it trivial to start a new page and almost invisible to mark one as decayed.
  3. Removing content feels like deletion of effort. So nobody deletes; the index grows; signal-to-noise falls; trust erodes.

How real teams fix it

Why we’re calling it out here

Almost every PKM tool in the tools sectionNotion, Obsidian, Logseq, Capacities, Anytype, Roam Research — is capable of producing world-class knowledge bases and capable of becoming a graveyard. The tool choice matters far less than the governance. Choose the governance first.

Sources