When a critical capability depends too heavily on one person
Consider an unexpected absence: a capability is fragile when its absence interrupts a critical outcome and no alternative has demonstrated that it can restore that outcome in time.
Within hours of every monthly close, a specialist reconstructs discrepancies between financial systems, interprets exceptions, and decides which adjustments may be recorded. Two people are listed as backups. Neither has completed the close without her intervention.
The case is a composite. The fragility it represents often remains hidden because the outcome is delivered as long as the specialist is available.
On the matrix, there is coverage. In the operation, there is only one reliable path.
Dependency becomes visible through decisions
Calling someone “indispensable” is too broad. It may recognize expertise while obscuring what is actually at risk.
It is better to identify the outcome that could be interrupted, the decision where judgment is concentrated, and how long the organization can afford to wait. Delaying an internal recommendation is not the same as failing to meet a regulatory obligation.
In the financial close, the dependency does not encompass everything the specialist does. It is concentrated in interpreting certain discrepancies and authorizing their treatment before a deadline. That degree of precision makes a proportionate response possible.
Four backup states that should not be confused
A nominal replacement is someone associated with the role on a list. It signals intent, not response capability.
A theoretical backup knows the procedure and has reviewed the documentation. They can explain the steps but have not acted when exceptions arose.
A participating backup has supported the decision, performed part of the work, and received feedback. There is evidence of practice, although responsibility is still shared.
A demonstrated backup has sustained the outcome under representative conditions and within the required time. They do not need to reproduce the expert’s style; they need to resolve the risk.
Jumping directly from the first state to the fourth during a real absence is a gamble, not a plan.
Measure exposure and recovery
A highly specialized capability is not always critical. If demand can wait several weeks, there may be time to bring in external support. A less sophisticated decision can be critical if it must be made every hour and only one person has the authority.
Concurrency matters too. The specialist may be present and still become a single point of failure when three closes, incidents, or requests compete for her attention.
This interpretation connects with Team capability is not the average of its members: available knowledge does not amount to effective coverage under real demand conditions.
Knowledge transfer is not enough
The organization documents the procedure and arranges handover sessions. The backup learns the standard rules, but difficult discrepancies require recognizing patterns, asking about missing data, and anticipating the effect of an adjustment on another account.
That knowledge becomes visible through work on real cases, not by copying instructions. Transfer requires gradual exposure: observe, explain decisions, resolve them alongside the specialist, and then lead with a later review.
It may also require changing authority. If the backup has mastered the task but every exception still requires the specialist’s signature, the dependency remains institutionalized.
The case forces a redesign of the practice
For two closes, the backup first leads a limited set of reconciliations. The specialist intervenes only when an escalation rule requires it. On the third, the backup takes responsibility for the full close and documents the decisions that still raise doubts.
The test reveals that part of the work can be standardized, another part requires shared judgment, and one authorization had been concentrated by custom rather than regulation.
The result is not a duplicate of the expert. It is a second operating path and less work that should never have depended on her in the first place.
GAO has argued that succession planning and management can help develop an organization’s future capability, rather than merely recreate replacements for current positions. The context is the US federal government, but the distinction between a name and a capability is directly relevant. GAO, Human Capital: Succession Planning and Management Is Critical Driver of Organizational Transformation (opens in a new tab).
A later GAO review also notes that leading organizations move beyond a focus solely on replacing individuals and orient succession toward strengthening present and future capability. GAO, Selected Agencies Have Opportunities to Enhance Existing Succession Planning and Management Efforts (opens in a new tab).
The expert also needs protection
Dependence on someone is often presented as recognition. In practice, it can prevent vacation, mobility, and development. Every attempt at change seems too risky because the organization never created alternatives.
Reducing dependency does not diminish the person’s value. It allows their contribution to shift toward new problems and stops the system from using their availability as its primary control.
The review must avoid blaming the person for having accumulated knowledge. Many dependencies arise from design decisions, incentives, and sustained urgency.
A list of successors does not reduce risk until someone else demonstrates that they can sustain the critical decision. The final question is not who could take the job, but how long the organization would need to restore the outcome if its only reliable path disappeared tomorrow.
To extend this reading, see From a skills gap to a capability gap: individual development is not always what is missing and From headcount to capability: what should change in workforce planning, which develop complementary dimensions of the problem.
Keep exploring
Bias and fairness: the same scale does not guarantee the same opportunity to demonstrate
An uncomfortable finding in assessment is that a common scale does not produce fairness when people lack comparable opportunities to generate and present evidence.
Generalists, specialists, and hybrid roles: what the architecture should decide
Does the organization need breadth, depth, or integration? Generalist, specialist, and hybrid are possible answers, not identities the architecture should fix permanently.
How to adapt an assessment without changing what it is meant to measure
Two people may demonstrate a capability in different ways while still meeting the same core demand. Fair adaptation requires separating the construct from barriers created by the format.
How to tell whether a skills-first initiative creates value after the pilot
To decide what comes after the pilot, examine which decisions changed, which outcomes followed, and what it costs to sustain the mechanism. Participation and coverage do not yet demonstrate value.
Not every critical skill is strategic: importance, scarcity, and advantage are not the same
Although importance, scarcity, and advantage are often compressed into the label “critical skill,” each dimension requires different evidence and investment. Separating them changes what must be protected, sourced, or built as a system.
What must remain common and what can vary across areas
Even when two areas work differently, they can still share an architecture. Adaptation stops being local when it changes meaning, comparability, or the rights attached to use.