Business Process Expert·7 min read
The tipping point
Not every process needs to be documented. A 3-person startup where everyone sits in the same room can coordinate verbally. A 50-person company with remote teams across time zones cannot. The question is not whether to document, but when.
Here are the five triggers that signal the tipping point has passed.
The 5 triggers
1. Someone quit and knowledge walked out
The most painful trigger. A key person leaves and nobody can do their job. The team scrambles to reconstruct the process from memory, emails, and guesswork. If this has happened, you are already late.
2. You are hiring faster than you can onboard
Every new hire asks the same questions. Senior people spend 20% of their time explaining instead of doing. Documentation scales onboarding from "ask Sarah" to "read this, then ask Sarah."
3. An audit or compliance requirement appeared
ISO 9001, SOX, HIPAA, GDPR all require documented processes. The auditor does not accept "we know how it works." They need evidence. If certification or compliance is on the roadmap, documentation is mandatory.
4. You are about to automate
The automation team is asking "how does this process work?" If the answer involves a 45-minute verbal explanation with "and then sometimes we also...", the process needs to be mapped before code is written.
5. The same mistake happened three times
When different people make the same error in the same process, the process is unclear. The fix is not "be more careful" - it is documenting the decision criteria and exception paths so the process itself prevents the error.
"The honest answer is: the moment you hire your second person. But the realistic answer is: the moment something breaks because the knowledge was in one head. Do not wait for that moment. It is expensive."
Signs you are too early
- -The process changes every week. If the process is still being figured out, documenting it wastes time. Wait until it stabilizes.
- -Only one person does it and they are not leaving. If the bus factor is low and the risk is low, a quick conversation beats a formal document.
- -The team is 3 people in the same room. Verbal coordination works at this scale. Documentation overhead is not worth it yet.
Signs you are too late
- -New hires take months to become productive. If ramp-up is slow, undocumented processes are the bottleneck.
- -Customers experience inconsistent service. Different people handle the same request differently because there is no standard process.
- -Key person risk keeps you up at night. If you are worried about what happens when someone leaves, you already know the answer.
The minimum viable first step
You do not need to document every process at once. Start with one:
- 1.Pick the process with the highest risk (key person dependency, compliance requirement, or frequent errors).
- 2.Map it in one sitting. 2-3 hours. Do not aim for perfect.
- 3.Show it to the team. Does it match reality? Fix what is wrong.
- 4.Assign an owner and a review trigger. Done.
Related guides
Keep learning
Frequently asked questions
Is it ever too early to document processes?▼
Yes. If the process changes every week, is performed by one person who is not leaving, or the team is very small and co-located, the overhead is not worth it yet. Wait until it stabilizes.
What is the cost of not documenting?▼
Each undocumented process costs in onboarding time, repeated mistakes, compliance risk, and key person dependency. A single employee departure from an undocumented process can cost weeks of productivity.
Should I start with the most important process or the easiest one?▼
Start with the highest-risk one: the process most dependent on one person, most affected by errors, or most relevant to upcoming compliance. The impact justifies the effort and builds momentum.