Key-Person Risk Map.

Find the functions that depend on one person and rank them by how badly their loss would hurt, so you protect the worst single points of failure first.

First in Make the Operation Survive Any One Person Leaving. Go function by function and ask the departure question.

The departure test

For each function, ask: if this person were gone for a month starting tomorrow, what would stop?

What to look for, for each function

Knowledge only one person has: how a system works, a funder’s history, the quirks of a process

Access only one person holds: passwords, accounts, keys, signing authority

Relationships only one person carries: the funder who deals only with them, the partner who trusts only them

Rank by damage

Order the risks by how badly the organization would be hurt if that person vanished. Protect the high-damage ones first

This map is your protection list. The functions marked high are where one departure could stop the work, and where the next two steps go first. Feeds the Knowledge and Access Capture and the Cross-Training Plan.

Your answers stay in your browser on this page and are never sent anywhere. Use Save or print to keep your copy.

Back to Make the Operation Survive Any One Person Leaving, or start over from the welcome page.