Skip to content
IT White GloveFractional CIO & IT decision advisory
Build a decision brief
Menu

Decision guide · Key-person risk

One person's knowledge is not a continuity plan.

When one employee, one contractor, or one long-standing relationship holds most of the operating knowledge, the organization is carrying a risk nobody has priced.

Frame the coverage question

The dependency accumulates one reasonable decision at a time.

Nobody decides to build an organization around one irreplaceable person. It happens gradually: the person who set up a system stays the only one who understands it, the person who negotiated a vendor relationship becomes the only contact who can reach them, and the shortcut nobody documented is remembered by exactly one employee.

This is not a loyalty or personnel problem to manage by hoping nothing changes. It is a decision about how much undocumented dependency the organization is currently willing to carry-and whether that amount is a choice or an accident.

Working test

If this person was unreachable for two weeks starting today, could someone else keep the essential systems running?

Exposure lenses

Six questions to price the dependency.

  • Knowledge concentrationWhat exists only in one person's head, with no written record anywhere?
  • Access concentrationWhich admin, vendor, or infrastructure accounts can only that person reach?
  • Documentation currencyDoes written documentation exist, and does it reflect the system as it runs today?
  • Coverage during absenceWhat actually happens this week if that person is unreachable?
  • Transition costWhat would it take, in time and money, to replace this function starting today?
  • Trigger for actionWhat signal-tenure, market movement, a stated intention-should raise the urgency now?

Working process

Price the gap before it opens, not during it.

  1. Map knowledge and access

    Identify what only one person currently knows or can reach, system by system.

  2. Test a real absence

    A planned or simulated absence will surface gaps a checklist alone will not.

  3. Prioritize by consequence

    Document and cross-train the highest-consequence gaps first, not the easiest ones.

  4. Decide the coverage model

    Choose internal backup, fractional cover, or a vendor arrangement before it is needed.

Connect this to the underlying structure decision

A single departure also tests whether offboarding actually closes every access point

Hypothetical pattern

A two-week notice and undocumented credentials

A sole IT administrator resigns with two weeks' notice. Several vendor accounts, an undocumented backup process, and the reasoning behind a handful of firewall rules exist only in that person's memory. The organization is not just losing an employee-it is discovering, under time pressure, exactly how much of its operating knowledge was never written down.

See how recovery capability itself gets tested

Next step

Bring the system only one person can explain.

A focused brief can turn an unpriced dependency into a documented gap, a priority order, and a coverage decision.

Build the coverage brief

IT White Glove · Fractional CIO & IT decision advisory

Get IT decisions made, and made to stick.

contact@itwhiteglove.com

IT White Glove is an independent IT provider. Microsoft and Microsoft 365 are trademarks of the Microsoft group of companies.

Related brands share common ownership and are operated by the same team.