Cognitive Dependency: Definition, Signs and Fixes
What is cognitive dependency?
Cognitive dependency is the degree to which an operation relies on knowledge and routine mental work held by specific people instead of documents and systems: procedures people "just know", single experts for critical steps, reports assembled from memory, data retyped between systems by qualified staff. It is one of the three layers of the HDI, with coordination dependency and control dependency.
Why does cognitive dependency matter?
Knowledge that lives in one head leaves with that person, and nobody can automate it until someone writes it down. High cognitive dependency makes onboarding take months, keeps the same two or three experts answering "quick questions", and lets one resignation stall a regulated process. It also wastes expensive capacity: qualified people spend hours switching between systems, transferring data by hand and compiling status instead of doing the work only they can do.
What are the signs of high cognitive dependency?
A new hire needs months of shadowing before working alone. One person knows how a critical step works. The written procedure and the real one differ. People assemble reports by hand from scattered sources, and the same experts answer the same questions each week. The HDI screening asks about these behaviours, and they show up in the Cognitive layer score.
How do you reduce it?
Capture the knowledge and spread it. Write down the procedure as people perform it. Cross-train until a second person has performed each critical step. Remove routine load, such as manual data transfer and report assembly, through integration and automation. Captured knowledge is also what later makes AI and automation possible. The Phase 2 audit identifies which processes to start with.
Related terms
- Key-person risk: the business risk that cognitive dependency creates.
- Bus factor: how many people hold the knowledge.
- Operational leak: the monthly hours routine load consumes.