The Most Expensive Asset No One Puts on the Balance Sheet
Why institutional knowledge is an organizational risk, not just an IT problem.
Every organization can easily point to its tangible assets: systems, software, vendors, contracts, budgets.
And then there’s the one asset that quietly holds everything together — the one that never appears on a balance sheet. Institutional knowledge.
It lives in people’s heads. It’s the unwritten understanding of why systems were configured a certain way, how processes actually work, and which “temporary” decisions quietly became permanent. It’s the accumulated memory of tradeoffs, workarounds, exceptions, and historical context that allows an organization to function day to day.
This risk often gets labeled as an IT issue. In reality, it’s an organizational one. I’m certainly not the first to talk about institutional knowledge — what I continue to see, though, is how consistently its risk is underestimated and misclassified as “an IT problem.”
When knowledge becomes a single point of failure
Institutional knowledge rarely concentrates by design. It accumulates gradually and invisibly.
One person becomes the one who knows. Not because they were formally assigned that role — but because they were there early, fixed the problem once, or stayed when others moved on. Over time, knowledge hardens into dependency.
- “Ask Bob, he knows how that works.”
- “Jane set that up years ago, don’t change it.”
- “We’ll document it later once things calm down.”
And then one day Bob leaves. Jane retires. Someone goes on vacation during an incident. That’s when organizations discover how fragile their operations really are.
This isn’t a failure of individuals. It’s a failure of structure.
This isn’t a tooling problem
When this risk surfaces, the first instinct is often technical: new software, better monitoring, more vendors, more documentation tools.
But the root cause usually sits upstream. This is a governance and continuity problem, not a technology one.
If ownership is unclear, documentation won’t stay current. If decision rights aren’t defined, workarounds multiply. If no one is accountable for institutional knowledge, everyone assumes someone else has it covered.
Technology doesn’t create clarity. It amplifies whatever structure already exists.
Documentation is not bureaucracy
Documentation gets a bad reputation because it’s often treated as busywork — created under pressure, written once, and immediately forgotten.
But when done intentionally, documentation serves a different purpose entirely: it makes organizations less fragile. Not by documenting everything — that’s neither realistic nor useful — but by documenting the right things:
- System and process ownership.
- Decision rationale.
- Operational assumptions.
- Known risks and tradeoffs.
The goal isn’t perfection. The goal is survivability. An organization shouldn’t require a specific person to be present in order to function safely.
The quiet cost of ignoring it
The longer institutional knowledge remains undocumented, the more expensive it becomes to address. New hires take longer to onboard. Incidents take longer to resolve. Changes become riskier, slower, and more political.
Eventually, organizations stop improving systems — not because they don’t see the need, but because no one is quite sure what will break if they try. At that point, institutional knowledge stops being an asset and becomes a liability.
A simple test
If your continuity plan for a critical system is “Ask Bob,” you don’t have a plan. You have a hope. And hope is not a strategy.