Every engineering organization has them: the engineers who "just know" how things work. The ones who've been around since the early days. The ones you can't afford to lose.
They're not irreplaceable because of their coding skills. They're irreplaceable because of what's in their heads.
The Tribal Knowledge Problem
This is tribal knowledge, and it's both invaluable and incredibly fragile.
When that senior engineer finally takes another job—or leaves the workforce entirely—that knowledge walks out the door.
The Numbers Are Staggering
Time spent searching:
Developer onboarding:
The $750,000 Question
Here's a simple calculation that changes how you think about documentation:
For a company of 150 employees:
For avoided research tasks:
These aren't hypothetical numbers. They're from published ROI studies on knowledge management systems.
Decision Archaeology: The Hidden Time Sink
When no one knows why a system was built a certain way, engineers must excavate:
The Decision Archaeology Process
This process repeats for every engineer, every time they encounter the system.
Cumulative weeks or months of wasted effort.
The Healthcare.gov Lesson
Healthcare.gov[6]
October 2013 Launch
The root cause wasn't bad code. It was decision fragmentation:
- ×60 contracts awarded to 33 different vendors
- ×No single entity responsible for integration
- ×No documented decisions about architecture
- ×18 written warnings over 2 years—ignored
Without a central decision record, there was no way to track which warnings mattered or who was responsible for addressing them.
The Onboarding Multiplier
The Onboarding Multiplier
Every undocumented decision doesn't cost once—it costs every time:
What Documentation Saves
The ROI of documentation isn't just about efficiency. It's about risk:
The Path Forward
Capturing decisions doesn't require heavyweight processes. The best systems capture decisions in the flow of work—during the conversations where decisions naturally happen.
The goal isn't perfect documentation. It's capturing enough context that the next person doesn't have to excavate.
Your tribal knowledge isn't an asset.
It's a liability—one that walks out the door every time someone leaves.
References
- [1]Panopto (2019). Valuing Workplace Knowledge
- [2]Pew Research (2020). The pace of Boomer retirements has accelerated in the past year
- [3]McKinsey (2012). The social economy: Unlocking value and productivity through social technologies
- [4]Swarmia (2024). Measuring developer productivity: The metrics that matter
- [5]Gallup (2017). Onboarding New Employees: Maximizing Success
- [6]Dolfing, H. (2022). Case Study: Launch Failure of Healthcare.gov