Paper 01
The Key Person Dependency Risk
Many teams appear to have stable operations. Work gets done, clients are served, and requests are handled in a timely manner. But underneath that, execution depends on a few key people in order for work to move forward. When those key people are unavailable, work slows, stalls, or must be rerouted.
This is key person dependency. For most teams, this is not caused by lack of effort or incapability. It is a system design problem.
What is Key Person Dependency?
Key person dependency occurs when work cannot move forward without the intervention of specific people. Instead of flowing through structured systems, work depends on who understands the context, who knows how work is typically done, and who decides what happens next. When those people are present, work moves smoothly. When they are not, execution slows or stops.
Why Tech Teams Are Susceptible
Teams within tech companies tend to develop key person dependency for predictable reasons:
+ Implicit Workflows: Work moves through people rather than clearly defined steps.
+ Missing Context: Teams rely on memory or direct explanation instead of easily accessible, documented information.
+ Poor Documentation: Documentation exists, but it is not usable during execution.
+ Unclear Ownership: Responsibility for specific steps is not always clear.
+ Fragile Handoffs: Work does not transfer cleanly between people or teams.
What It Looks Like in Practice
Key person dependency rarely manifests as immediate failure. It usually appears as friction. Work pauses until a specific person is available, decisions wait for input before work can continue, and tasks require explanation before they can proceed. Progress depends on who is present, not what your team's system supports. Eventually, this limits how much work a team can reliably handle before encountering major disruptions.
A Simple Diagnostic Question
A useful way to evaluate your team is to ask yourself: “Where does work slow, stall, or reroute because it depends on a key person?”
If you can answer that question clearly, you are likely experiencing key person dependency.
What Fixing It Requires
Reducing key person dependency means redesigning how work moves through the team. This includes:
+ Defining workflows so execution does not rely on individual interpretation
+ Embedding required context into systems, not people
+ Assigning clear ownership at each step of work
+ Structuring handoffs so work transfers cleanly
+ Ensuring work can continue without requesting context from key people
The goal is to design workflows that move forward without requiring intervention from key people.