Organisational dependency is reliance on a particular person or small group for decisions, access to knowledge, authorisations or work to proceed. It becomes a continuity risk when the organisation cannot reliably maintain an essential activity without those individuals.
Dependency is not automatically a weakness. Specialist judgement, required approvals and deep experience can be valuable. The question is whether the reliance is understood, proportionate and supported by arrangements that work when circumstances change.
What is key-person dependency?
Key-person dependency is a form of organisational dependency in which a particular individual carries knowledge, relationships, authority or operating judgement that others cannot readily replace. The person may be highly capable; the vulnerability lies in how the work is organised, not in that person’s performance.
Five questions that reveal the underlying risk
1. What actually stops? Identify a specific decision, service, approval or handover that depends on a named role or person. Avoid treating general concern about a busy colleague as evidence of a continuity failure.
2. Why does it stop? Distinguish exclusive system access, undocumented knowledge, unclear delegation, a required specialist check and habitual escalation. Different causes require different responses.
3. What happens when that person is unavailable? Examine relevant examples of leave, absence, turnover or competing demands. A deputy named in a plan is not the same as a deputy with usable authority and information.
4. Which dependencies are justified? Some controls must remain concentrated for legal, technical or safety reasons. The goal is not to distribute every decision, but to distinguish necessary oversight from avoidable single points of failure.
5. What evidence would change the conclusion? Compare accounts from different roles with process records, delegations, actual decisions and contrary examples. A credible assessment documents both supporting and competing explanations.
Reducing dependency without losing expertise
A practical response might clarify exception thresholds, make operational guidance accessible, provide authorised backups, strengthen handovers or change how advice is requested. Simply asking a key person to delegate more may be ineffective if the team still lacks usable authority, information or support.
Define a baseline before making changes. Depending on the process, useful observations may include waiting time, the proportion of cases escalated to one role, interruptions, rework and how essential work continues during absence. Review the same evidence after an intervention, including any unintended consequences.
Is key-person dependency the same as a decision bottleneck?
Not always. A person can hold critical knowledge without approving every decision. Conversely, a decision bottleneck can arise from unclear rules, too many approval steps or missing information even when no single specialist is indispensable. The two issues often overlap, but should be examined separately. Explore decision bottlenecks.
How ODLAMS approaches the question
ODLAMS uses a scoped, evidence-led approach to understand how organisational arrangements shape dependency, decision authority and continuity. Its Assess, Improve, Assure cycle links observations to a bounded change and a subsequent review. The framework is in development; this page does not claim a validated maturity rating or certification outcome.
Read the ODLAMS Framework · Follow a fictional assessment example · Discuss an organisational or research enquiry