Problem Card · Stable · Repeat It
Tribal Knowledge Drives Operations
You may recognize this when
- Documentation may exist, but experienced employees still know how work is really done.
- New people need informal explanation, repeated rescue and observation to succeed.
- This creates hidden key-person dependency.
- Turn recurring know-how into usable workflows, examples, quality standards and exception paths, then test whether another capable person can use them without help.
What you may be seeing
Key steps happen because one experienced person remembers them. When she is out, work slows, mistakes rise and nobody else knows the shortcut.
What it looks like
Documentation may exist, but experienced employees still know how work is really done. New people need informal explanation, repeated rescue and observation to succeed. This creates hidden key-person dependency. Turn recurring know-how into usable workflows, examples, quality standards and exception paths, then test whether another capable person can use them without help.
How the Roadmap reads it
Documentation may exist, but ordinary work still depends on experienced people remembering how things are really done. New employees learn through explanation, rescue and observation instead of a usable operating method. This creates hidden key-person dependency even when the company looks organized on the surface. Stable work turns recurring know-how into workflows, examples, standards and exception paths that capable people can use.
A question to test it
What recent example from your own company would confirm or rule this out?
Source: Stable Roadmap v2.1 problems and Stage Playbook v2.0
Ask Atria
Next step
See the Stable problemsThis Card connects to
The Game
Accelerators
Where this fits
Accelerators that address it
Related on the Roadmap
Talk it through with us
If this Card describes your week, a free conversation is the fastest way to see what it means for your company and what to do next.
Book a free conversation