Document everything
Documentation is essential, but static instructions become stale and rarely appear at the moment an exception needs a decision.
D/07When they leave,
When they leave,
what leaves with them?
The official process explains how work should happen. One experienced person knows how it really happens — which exceptions matter, what the systems get wrong and how to recover when something fails.
The person became part of the system.
Every established operation develops judgement that no procedure captures completely. Experienced people recognise a customer exception, reconcile conflicting records and know when the official process will create the wrong result.
Over time, the business routes more ambiguity towards them. Their knowledge keeps service dependable, so the underlying gaps remain hidden. A resignation, retirement, promotion or long absence suddenly places a deadline on understanding what they do.
The answer is not to document every thought or automate a person's role. It is to identify which decisions, rules and recovery paths the business cannot afford to lose.
The same event can create exposure or advantage.
The fear
The company discovers what they knew after they are gone.
Service failures expose undocumented exceptions, remaining staff lose confidence and the replacement inherits responsibility without the evidence needed to exercise it.
The ambition
Hard-won knowledge becomes a shared capability.
The operation can surface the right exception, preserve the reasoning behind decisions and help more people exercise judgement without depending on one individual.
How the constraint shows up.
01
Colleagues say, 'Ask them — they know how it really works.'
02
Important reconciliations or decisions happen outside the system.
03
Training explains the standard path but not the exceptions that consume most attention.
04
Only one person can recover a failed integration, report or operational process.
05
The business cannot describe what would stop if that person were unavailable tomorrow.
06
A replacement is expected to learn the role by shadowing rather than using reliable records and controls.
A handover document cannot carry judgement on its own.
01
02
Hire a replacement early
Overlap transfers experience, but it reproduces the same dependency unless the operation itself becomes easier to understand.
03
Automate the role
Automation can remove repeated work, but opaque rules may hide the knowledge more deeply and fail on the exceptions that matter.
Find the knowledge the operation cannot safely improvise.
Start with decisions and failure recovery, not a catalogue of everything the person does.
Q/01
Which outcomes change materially when this person is unavailable?
Q/02
What information do they assemble before exercising judgement?
Q/03
Which rules can be made explicit, and which decisions still need a person?
Q/04
How should the system surface an exception, record the decision and make the result teachable?
The right answer may be to change the process, configure a product, integrate what you already have, modernise one part or build an owned capability. ORBN helps make that decision before it helps deliver it.
Own the knowledge the company paid to learn.
The valuable asset is not the employee's task list. It is the accumulated understanding of customers, rules, exceptions and recovery that makes the operation dependable.
OWN / 01
Explicit business rules and the circumstances in which they do not apply.
OWN / 02
Visible exception queues, decision evidence and recovery paths.
OWN / 03
Operational records that allow a new person to understand what happened and why.
Continue the decision.
Service
Custom software development
Put rules, exceptions and operational decisions where the work actually happens.
ServiceAI development
Make approved operational knowledge searchable and useful without removing human judgement.
ServiceTechnology strategy
Identify the dangerous dependencies and choose the smallest credible response.
What else changed?
What changed?Protect what the operation
Protect what the operation
cannot afford to relearn.
Tell us which person the business depends on and what changes when they are unavailable. We will help identify the knowledge worth turning into a shared capability.