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 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.
A question to test it
What recent example from your own company would confirm or rule this out?
Source: Stable problem registry
Ask Athena
Next step
See the Stable problems