Key person dependency
Concept
An operational risk where critical process knowledge or capability is concentrated in one or a few individuals, creating a single point of failure when they are absent or leave.
あわせて取り上げられたテーマ
Key person dependencyに関するエピソードでは、App sprawl、Zoned governance、Fusion development、Microsoft Excel、Power Platform、Power Platform Center of Excellence (CoE)も取り上げられています。
Description
Key person dependency is an operational risk in which critical process knowledge or capability is concentrated in one or a few individuals. When those people are absent or leave, the process, project or service can stall because nobody else knows how to run it. The concept describes a single point of failure that sits in people rather than in technology, and it is a common concern in operational resilience and continuity planning.
A closely related measure is the bus factor, also called the truck, lottery or circus factor. According to the Wikipedia article on the topic, it is the smallest number of team members who would have to leave suddenly before a project stalls because nobody else has the required knowledge. The article links the bus factor to key person risk but focuses on technical experts rather than on easily replaced managers or financial leaders. A person counts only if they are both key to the work and irreplaceable. A bus factor of 1 is a single point of failure, while higher values indicate more redundancy. The article gives the example of a 30-person bakery: if only five people can bake, the factor is five.
The cause is often undocumented or unshared work. In software, a component that only one person understands is a key dependency. The departure does not have to be dramatic: a new job or parental leave has the same effect as any other exit. The same source cites a 2015 to 2016 study of 133 popular GitHub projects that found 65 percent had a bus factor of two or less, which shows how common the pattern is even in widely used projects.
Typical mitigations named in the source are reducing complexity, documenting and updating processes, cross-training and sharing information. In practice, the decisions around this risk include which processes are critical, who currently holds the knowledge, and whether that knowledge lives in a form others can read, reuse and verify.
The M365.FM episode "Fix Excel Shadow Systems and Broken Business Processes" connects key person dependency to spreadsheet-based work. The episode says that relying on Excel and spreadsheets creates shadow data, key person dependency and static information. It describes these tools as a source of data integrity issues and information silos, and it argues that spreadsheets hide errors, slow the business and block real-time decisions. In that framing, a spreadsheet understood by only one person becomes exactly the kind of single point of failure described above.
The episode's recommended direction is to apply governance, visibility and automation to protect operations. It advises assessing the process architecture and choosing modern solutions that move beyond Excel and spreadsheets, with the stated goals of operational resilience, reduced risk and a team that is set up for growth. Taken together, the sources treat key person dependency as a risk to be identified and reduced through documentation, shared knowledge and more transparent, automated processes rather than as an unavoidable fact of how teams work.
Overview compiled with AI from M365.FM episodes and the facts on this page. You can improve it with the edit button below.
| Type | Concept |
|---|
Community wiki
Short info above, community knowledge below: add practical tips, examples or corrections. New contributions are reviewed first; trusted members publish directly.
Experts and companies for this topic
Nobody has listed this topic yet. Add it to your profile.
Maintained by Mirko Peters (Microsoft MVP) · Last updated: