Your operation depends on particular people, and you know it. There is a person, maybe you, who is the only one who knows how to run payroll, or where the passwords are, or how the funder relationship really works, and if they were out for a month, or left, part of the organization would simply stop.
This work finds those single points of failure, captures what is locked in one head, and cross-trains so that no one person leaving can take a critical function with them. It is not distrust of your people; it is protection for them and the mission, so no one is trapped as the irreplaceable person who can never take a real vacation. And it does not make everyone interchangeable, which is neither possible nor desirable; it removes the single points of failure that would actually stop the work. Use this if a departure or a long absence would stop part of your operation. If your core work is not even documented yet, map and standardize it first, because you cannot cross-train on work that does not exist on paper. And a boundary: if your real fear is the leader specifically being gone with no plan for who signs and who decides, that is emergency succession, and it has its own work.
You cannot protect against single points of failure you have not named. Go function by function and ask: if this person were gone for a month starting tomorrow, what would stop? Name each function that depends on one person, and what exactly they hold that no one else does, whether it is knowledge, access, or a relationship. Then rank the risks by how badly the organization would be hurt if that person vanished, so you protect the worst ones first.
Open the Key-Person Risk Map →Much of what makes a person irreplaceable is not skill but knowledge and access that live nowhere else: the passwords, the funder history, the quirks of the system, the relationships. For each high-risk function, have the person document what only they know: the steps, the logins, the contacts, the history, the things that would take a successor months to learn. Then make sure the organization holds, or can immediately reach, every critical account, password, and record, so no login leaves with a person.
That is a serious risk and often a warning sign, of insecurity, of a problem they are hiding, or of a culture where knowledge is hoarded for job security. Address it directly. Where it concerns control of money or records, protect the organization's access regardless. Where it is about trust and a culture of hoarding, that routes to culture and team health. This is a route, not a stop.
Captured knowledge still needs a person who can act on it. For each high-risk function, name at least one other person who will learn to do it, chosen realistically for capacity and fit. Then have the backup actually do the function, with the key person coaching, until they can do it alone. Reading a document is not cross-training; doing the work is. Build a periodic rotation so the backup skill does not fade.
Open the Cross-Training Plan →If the single point of failure is you, the leader, and the reason the knowledge has never been shared is that there has never been time or trust to share it, that is worth sitting with honestly, because an organization built entirely around one person is carrying a real risk, and so is that person. Where this is about the leader specifically and the organization's survival of their departure, the emergency succession work is the right room, with your board. This work spreads the everyday load; the deeper question of the organization built around one person has its own home.
No critical function depends on a single person. The knowledge and access that used to live in one head are captured and controlled by the organization. And a trained backup could step in for each critical function, which means your key people can take time off without the operation holding its breath.
Most leaders move from here to Build a Way to Find and Fix What Breaks, so the resilient operation also keeps improving. If the deeper issue is the leader's own succession, consider the emergency succession work, with your board. If knowledge hoarding is the block, that is culture and team health.