$340,000 per year to maintain internal knowledge documentation

$340,000 per year to maintain internal knowledge documentation. In just one minute inside a 600-person software company:
847 Slack messages
213 emails
41 meeting recordings
19 updated spreadsheets
7 revised presentations
3 policy changes

Now imagine trying to document all of that.

Cost to properly maintain organisational knowledge? Roughly $340,000 per year in knowledge-management overhead.

In one organisation I worked with, roughly four full-time roles were effectively dedicated to keeping internal documentation and knowledge systems up to date, updating process docs, fixing broken links, reorganising folders, and archiving outdated content.

By the time knowledge was documented, parts of it were already outdated.

Here’s the brutal part: when someone actually needed information, they still just asked in Slack because finding official documentation took 8 minutes. Asking “hey has anyone dealt with this client contract issue before?” took 45 seconds.

The traditional model:
→ Event happens
→ Someone documents it
→ Someone files it properly
→ Someone maintains it
→ Everyone searches for it later
→ Half the time it's outdated anyway

In many organizations, most internal documents are rarely revisited after creation, except when someone is asked to update or archive them. Over time, repositories quietly accumulate cost while delivering diminishing value.

Multiply that across millions of documents, and you are maintaining a graveyard.

The shift happening now: stop documenting, start extracting.

Different approach: instead of maintaining wikis, let AI read everything, Slack threads, call transcripts, shared documents, and surface answers when someone asks.

In the first month, the assistant answered more than 600 questions that previously required documentation searches or colleague interruptions.

Knowledge-management effort shifted from four maintenance-focused roles to one role focused on knowledge quality and workflow integration.

Estimated annual savings: ~$255,000.

But the bigger change was not the cost.
It was behaviour.

Work patterns did not change; the system adapted to how teams already operated.

Repositories have never been the primary place where knowledge lives.
Teams ask Jim in accounting or Sarah in ops because speed matters more than completeness.

The future of knowledge management is delivering answers in context.

Everything else risks becoming expensive digital hoarding.