The symptom
“One person holds the whole process in their head”
Reduce Key-Person Dependency
What it’s costing you
The business pauses when one person is on leave.
- Work queues when a specific person is on leave, because only they can do it
- Their knowledge exists as experience rather than as company data
- Every plan to grow runs through the limits of one person’s day
Why it usually happens
Knowledge stayed where it was cheapest to keep: in a head.
- The business grew around a capable person faster than it built systems, so the process still lives where it started: in their head
- Knowledge that was never written down cannot be delegated, so every exception routes back to the same desk
- The tools followed the person rather than the process: the spreadsheet only they maintain, the pricing only they can produce
The target operating state
The knowledge moves into a system anyone can run.
- 01The published outcome of this fix: estimating became repeatable, material usage traceable and labour measurable, and the company can quote when the supervisor is away
- 02The knowledge mapped: what they actually decide, from what inputs, by what rules
- 03Those rules captured in a system others can operate
- 04The expert moved from doing every case to handling the exceptions
A worked example
The company can quote without him now.
Before
One supervisor could look at a site and know what was required. When he was unavailable, producing an estimate of the same quality became significantly harder.
After
The system remembers how the company prices the work: materials, labour, wastage and contingency across every trade it handles. He still walks the site, and the quoting no longer waits for him.
Services that may be involved
Questions
Does this replace the person?
No, and the published costing engagement is explicit about it: the supervisor still walks the site, because someone has to. The system carries the obvious calls so their judgement is spent where it matters.
What if the key person is protective of their knowledge?
Start with what costs them most: the interruptions. Turning their knowledge into structured data removes the queue at their desk without removing their role in judging the hard cases.
How is knowledge actually captured?
As structure, not documents: material masters, consumption matrices, service definitions and labour mappings, the pieces the published costing framework was built from.
Where else does this problem hide?
In inboxes. In the published tourism engagement, which booking was actually confirmed lived in one person’s head and inbox; an eleven-stage pipeline made it a fact in the system instead.
Start before the next resignation letter.
If that sentence sounded familiar, the Health Check maps it properly before anything is bought.