Why visible systems don't tell the whole story
Organisations invest in cybersecurity, backups, business continuity plans and crisis procedures because those things reduce risk in normal conditions. Major disruptions expose a gap: two organisations with similar technical protections can have very different recovery trajectories. Technical recovery is necessary but not sufficient for operational continuity.
This illustrates the distinction between restoring systems and keeping operations going while systems are down. Formal procedures and responsibilities mattered, but they had to be adapted. Resilience therefore requires the capacity to move between structure and adaptation as circumstances change.
Relational dependencies vs technical dependencies
Relational dependencies occur internally and externally. Internally, response may require cooperation between IT and operations, security and communications, or local teams and senior management. Externally, it may depend on suppliers, regulators or partners who must make fast decisions or adapt service levels under stress.
Types of people-related dependencies
Not every dependency tied to a person is the same. The article distinguishes three overlapping but distinct reasons an individual may be critical:
- They hold specialist technical or procedural knowledge.
- They sustain access through personal relationships.
- They possess the authority needed for urgent decisions.
Each type requires different redundancy. Technical knowledge needs documented procedures and cross-training. Relationship-based access needs multiple points of contact and institutionalised channels. Authority requires clear delegation and backup decision-makers.
The relational single point of failure
Organisations often remove technical single points of failure but leave relational ones intact. A relationship may be strong yet fragile for the organisation if only one person can activate it. The objective is not to eliminate personal relationships, which can be valuable, but to make critical relationships accessible through more than one person and to translate personal networks into institutional access.
Relationships can be liabilities or strengths. When distributed across teams and supported by shared practices, relationships create redundancy and adaptive capacity. Effective crisis performance depends on pre-existing patterns of cooperation, the ability to improvise workarounds, and mechanisms for rapid information-sharing and decision-making. Organisations should therefore identify which relationships will matter in a disruption and then build the specific redundancies each dependency needs.
- Map relational as well as technical dependencies.
- Distinguish the form of redundancy each dependency requires (knowledge, contact, authority).
- Avoid dependence on a single individual for access to critical partners.
- Practice coordination across units to build mutual adjustment habits before disruption occurs.