Business Process Expert·7 min read
The resignation test
Imagine your best employee resigns tomorrow. Not in two weeks - tomorrow. Can the team keep running every process they own? If the answer is no, you have an undocumented process problem.
This is not hypothetical. A viral thread with nearly 6,000 upvotes described exactly this: a manager asked the team to document all their processes. Employees immediately suspected layoffs. But the real trigger was simpler - the manager realized that when the senior person went on vacation, nobody could do their job.
The bus factor
The bus factor is the number of people who would need to be hit by a bus (or quit, or get sick) before a process stops working. If your bus factor is 1 - one person holds all the knowledge - you have a single point of failure in your organization.
Process documentation raises the bus factor. When the knowledge is in a diagram, not in someone's head, anyone can pick it up.
"I worked with a company where the head of finance retired after 30 years. The month-end close process lived entirely in her head. It took the replacement 6 months to figure it out. One BPMN diagram could have prevented that."
Five triggers that make documentation urgent
1. Someone quit and knowledge walked out the door
The most common trigger. Suddenly nobody knows how the monthly reconciliation works, who to call when the supplier invoice is wrong, or why the spreadsheet has that one formula.
2. You are hiring fast
Each new hire asks the same questions. Without documentation, senior people spend 20% of their time explaining instead of doing. Documentation scales onboarding.
3. You failed an audit
The auditor asked to see your processes. You showed them a 3-year-old Word document nobody has read since it was written. Documentation that is not current is not documentation.
4. You are about to automate
The automation team needs to understand the process before writing code. If the process is in someone's head, the automation will encode assumptions, not reality.
5. The same mistake happened three times
When different people make the same error, the process is unclear. Documentation with decision criteria and exception paths prevents repeat failures.
Documentation is not bureaucracy
The objection is always the same: we do not have time to document. But the alternative is worse: spending 3x the time explaining things verbally, fixing mistakes caused by unclear processes, and rebuilding knowledge from scratch when people leave.
A good process map takes 2-3 hours to create. It saves hundreds of hours over its lifetime. The ROI is not even close.
Where to start
- 1.Pick the process with the highest bus factor risk. Which process depends most on one person? Start there.
- 2.Map it in one sitting. Follow the how to map a process guide. 2-3 hours maximum.
- 3.Assign an owner. The map needs a named person responsible for keeping it current.
- 4.Review quarterly. A map nobody reviews is a map nobody trusts.
Related guides
Keep learning
Frequently asked questions
Our team says they do not have time to document. How do I convince them?▼
Ask them how much time they spend explaining processes to new hires, fixing repeated mistakes, and answering the same questions. Documentation saves 5-10x what it costs to create.
What should we document first?▼
The process with the highest bus factor risk. Which process depends most on one person who could leave? That is your first map.
How do we keep documentation from going stale?▼
Assign a named owner. Review quarterly. Put the map where people work, not in a folder nobody checks. And the map should be a diagram, not a text document - visual maps are faster to update.