The Internal Wiki Nobody Updates: A Field Guide to Corporate Knowledge Rotting in the Dark

Every company of a certain size has one. A vast, sprawling internal wiki that was launched with a town hall, a Slack announcement, and the phrase “single source of truth” repeated until it lost all meaning. It was going to end the chaos. No more asking the same question twice. No more tribal knowledge trapped in one person’s head. Everything documented, searchable, alive. And for about six weeks, it almost was. Then someone changed the VPN process, forgot to update the page, and the whole cathedral of institutional memory began its slow, silent decomposition into a mausoleum of half-truths that everyone consults and nobody trusts.

The Archaeology of a Dead Page

Open any long-lived corporate wiki and you are not reading documentation. You are conducting an excavation. Here is a page last edited in 2021 by someone who left in 2022, describing a tool that was deprecated in 2023, linked from an onboarding doc that new hires are still, somehow, told to read. Here is a process diagram with a footnote that says “NOTE: this is out of date, ask Priya.” Priya is on parental leave. Priya has been on parental leave, in the collective memory of this wiki, since the beginning of time.

The tragedy is that the wiki isn’t empty. It’s the opposite of empty. It’s overfull — bloated with three competing versions of the same onboarding guide, four expense policies with different dollar thresholds, and a “Getting Started” page that starts by explaining a login screen that no longer exists. The information isn’t missing. It’s just impossible to know which layer of sediment is load-bearing and which will collapse the moment you step on it. So people do the only rational thing: they ignore all of it and ask a human on Slack, which is precisely the behavior the wiki was built to eliminate.

Why Nobody Updates It (A Study in Rational Neglect)

Here’s the thing everyone gets wrong: people don’t fail to update the wiki because they’re lazy. They fail to update it because updating it is unrewarded, invisible labor that helps a stranger six months from now while costing you twenty minutes today. No manager has ever put “kept the wiki current” in a performance review. No one has ever been promoted for excellent documentation hygiene. The incentive structure points entirely, relentlessly, at doing the actual work and never, ever writing down how you did it.

This is the same organizational blind spot that produces the brand guidelines nobody follows — a beautiful, expensive document that describes an ideal nobody has time to honor. The wiki and the brand book are cousins: both are monuments to the corporate fantasy that if you write the rule down clearly enough, reality will comply. Reality does not comply. Reality is understaffed, on deadline, and has already moved the process to a new tool without telling anyone.

And so the rot compounds. Every out-of-date page teaches the workforce a small, corrosive lesson: the wiki lies. Once people learn that lesson — and they learn it fast — they stop trusting any of it, which means they stop updating any of it, because why maintain a resource nobody believes? The wiki dies not from neglect but from a self-fulfilling prophecy of distrust. It’s a knowledge base with the epistemics of a group chat.

The Rituals We Perform Instead of Fixing It

No organization admits its wiki is dead. That would require admitting that a six-figure Confluence license and eighteen months of “documentation initiatives” produced a haunted house. Instead, companies perform elaborate rituals of pretend-maintenance. There’s the quarterly “documentation sprint,” where everyone is asked to update their pages, which produces a brief flurry of edits and then eleven weeks of silence. There’s the new “wiki champion” role, assigned to a junior employee who will spend three months heroically reorganizing before quietly giving up. There’s the inevitable decision, made in a meeting, to migrate everything to a new platform — as if the problem was the software and not the fact that nobody is incentivized to write.

The migration is the purest form of denial. It takes a graveyard, exports it, imports it into a nicer graveyard, and calls it transformation. The dead pages come with. The out-of-date policies come with. Priya is still on leave, in the new system too, forever. This is the corporate equivalent of the approval chain that turns a good idea into a beige rectangle: enormous coordinated effort producing a result indistinguishable from doing nothing, but with better fonts.

What a Living Wiki Would Actually Require (And Why You Won’t Do It)

A wiki stays alive under exactly one condition: updating it has to be cheaper and more rewarded than not updating it. That means documentation written at the moment of change by the person making the change, in the flow of the work, not as a separate chore assigned to future-you who is already overbooked. It means pages that expire on purpose — that flag themselves as stale after ninety days and demand a human confirm they’re still true. It means someone senior visibly using the wiki, correcting it in public, treating it as real infrastructure rather than a compliance checkbox.

Mostly it means measuring the right thing. Companies track wiki page counts and edit volumes — numbers that go up and mean nothing, the documentation equivalent of ego KPIs that measure pride, not business. A wiki with ten thousand pages and a 40% accuracy rate is worse than a wiki with two hundred pages you can trust, because the big one costs you the time to read it and the pain of acting on a lie. Nobody measures trust. Trust doesn’t fit in a dashboard. So the dashboard says the wiki is thriving while the entire company routes around it via Slack.

You won’t fix this, and it’s worth being honest about why. Fixing it requires an organization to value maintenance over creation, invisible work over visible work, and long-term clarity over short-term velocity. Every incentive in corporate life pulls the other way. The wiki isn’t broken because your company is uniquely dysfunctional. It’s broken because it’s downstream of a culture that rewards launching things and ignores the far harder, far more valuable work of keeping them true.

Long Live the Wiki. The Wiki Is Dead.

So the internal wiki persists in its undead state — too full to delete, too rotten to trust, too expensive to admit was a mistake. It sits there accumulating pages the way an attic accumulates boxes: technically organized, functionally a hazard, consulted only in desperation. And every eighteen months someone in a leadership offsite will suggest, with the fresh optimism of a person who has never done the work, that what the company really needs is a better single source of truth.

At No Briefs Club we make gear for people who’ve read the wiki, found it wrong, and asked a human anyway. When you’re the one still keeping the real knowledge in your head because the system rewards you for exactly nothing, the Spreadsheet Sloth tee understands you on a spiritual level. And when someone announces the next migration in an all-hands, Fuck The Brief is the appropriate silent commentary. Come find your uniform in the shop — the source of truth is you, so you might as well dress like it.