Tribal knowledge is the silent killer of scalability. When a critical process exists only in Marco's head, and Marco is on vacation or (worse) resigns, the company grinds to a halt.
I've seen 50-person startups where the only way to deploy was to DM Andrea on Slack. I've seen enterprise IT departments paralyzed because "the person who knew how to do it left last year."
The problem isn't a lack of documentation. The problem is that traditional documentation (company wikis, Google Docs, process manuals) is too slow to keep up with reality.
The 5-Minute Rule
I've developed an approach I call "the 5-minute rule": if operational information took you more than 5 minutes to discover or figure out, it deserves to be documented.
Not a 50-page manual. Not a formal procedure. A note. A paragraph. A checklist. The standard is: good enough that someone else can execute without calling you.
Examples:
- "How to deploy to staging" → 3 lines in a shared Obsidian note
- "Who approves expenses over €500" → one line in a README file
- "Who to ask for AWS access" → a bullet point in a Google Doc
The DOC Framework
For every operational process, I apply the DOC framework:
- Definition: what's the input, what's the output, who's responsible
- Operation: the steps to execute (max 10 bullet points)
- Context: why it's done this way, what can go wrong, who to contact
A DOC process takes half a page. It takes 2 minutes to read. It takes 5 minutes to update. And if someone leaves, anyone can pick it up.
How to Start
The worst way to tackle documentation is "this Friday we'll write everything down." It never works. Instead:
- Identify the pain points. When someone asks "how do I do X?" on Slack for the third time, that process is a candidate.
- Write while you fix. Next time you explain a process to someone, write it down immediately instead of just telling them. Time invested: 5 minutes. Time saved: 30 minutes every time someone asks.
- Use one place only. All operational documentation in one single place (Obsidian, Notion, Google Drive). If it's scattered across 5 tools, it might as well not exist.
- Cultivate the habit, not perfection. Perfect documentation doesn't exist. Good documentation is infinitely better than none.
The Real Cost of Non-Documentation
Every time a team member asks "how do I do X?" and someone explains it, the company has paid two salaries to transfer knowledge that could have been written down already.
Every time a new hire takes 3 weeks instead of 1 to become productive, the difference is undocumented processes.
Every time a key employee resigns and leaves a 3-month gap, the cost isn't just recruitment — it's the knowledge that leaves with them.
Documentation isn't bureaucracy. It's an investment with measurable returns.