Business-Held Knowledge System
Make the organisation retain knowledge when individual employees leave
- Difficulty
- Advanced
- Time to result
- ~months to results
- Steps
- 5
- Confidence
- 95%
A company does not become resilient merely by training individuals; it must retain what those individuals learn. Hoffmann describes repeated barista training as pouring water into a bucket with a hole because employees left and the customer business forgot the knowledge. The remedy is to collect, systemise, and maintain that knowledge inside the organisation through documented processes, training materials, decision rules, and accessible records. Employees still provide judgment and creativity, but they no longer carry the entire operation privately in their heads. New staff can access accumulated learning, experienced staff can leave without guilt, and the organisation can improve its methods over time rather than continually restarting from zero.
Origin
Extracted from Deep Dive with Ali Abdaal, where Hoffmann described helping coffee shops retain training despite high staff turnover.
Core principles
- 01Training people is insufficient if the business forgets when they leave
- 02Systems should preserve expertise without devaluing employees
- 03No employee should feel trapped because the company depends on them
- 04Institutional memory makes work easier and the business more resilient
How to run it
- 1
Locate fragile knowledge
Identify tasks, relationships, and decisions that only one person understands. Prioritise anything whose absence would stop operations.
Pro tip Ask each employee what would break if they disappeared for a month.
Watch out Job titles rarely reveal all hidden dependencies.
- 2
Capture work in context
Document how recurring work is performed, why key choices are made, and what exceptions occur.
Pro tip Capture the process while it is being performed rather than reconstructing it later.
Watch out A bare checklist may omit the judgment needed for unusual cases.
- 3
Build accessible systems
Turn captured knowledge into searchable procedures, training resources, templates, and decision rules owned by the business.
Pro tip Keep materials close to the tools and moments where people need them.
Watch out Documentation that employees cannot find is not institutional memory.
- 4
Test transferability
Ask another person to perform the work using the system and record where they become confused or blocked.
Pro tip Use new hires as high-quality testers of assumed knowledge.
Watch out The original expert should not silently rescue the test.
- 5
Maintain organisational learning
Update the system whenever work changes, failures reveal gaps, or employees develop a better method.
Pro tip Give each critical process a named maintainer.
Watch out Stale procedures can become more dangerous than missing ones.
In the wild
A coffee roaster repeatedly trained café employees, but much of the knowledge vanished as temporary staff moved on. Hoffmann proposed working with café owners to collect and systemise the material so it remained available regardless of who executed it.
→ The café could preserve standards, onboard replacements more easily, and reduce dependence on particular employees.
A course company relies on its founder as the only person who knows how to resolve delivery problems. The team records supplier contacts, escalation rules, booking steps, and contingency options, then tests the process with an operations assistant.
→ Deliveries no longer require the founder to stay awake monitoring every shipment.
Common mistakes
Training without retention
The company repeatedly teaches individuals but never stores the resulting knowledge for future employees.
Documenting actions without reasons
Procedures list clicks and commands but omit the principles needed to handle exceptions.
Using dependency as retention
A key employee is made to feel unable to leave because too much of the organisation rests on them.
Is it for you?
Best for
Growing organisations with repeated training, employee turnover, or dependency on a few experts.
Not ideal for
Short-lived projects whose processes will not be repeated or maintained.
From the transcript
“you build a business that is able to retain knowledge independent of the people that work within it.”
“we need to work with you in a way of collecting and Systemising the knowledge that we are delivering so that it's yours, regardless of…”
“the business itself has to retain information knowledge, it has to have a purpose bound into it. To be sustainable long term.”
From the episode
How To Turn Your Passion Into A Business Without Sacrifice - James Hoffmann
James Hoffmann