Expertise Dependency Map
If this person left tomorrow, what would actually break?
Why this matters
Organizations often know who their experts are. They are less likely to know which capabilities depend on those experts, how transferable those capabilities are, or where dependency risk is concentrated.
As AI compresses roles and accelerates turnover, understanding where expertise resides becomes increasingly important. A process can look stable right up until a key person leaves, changes roles, or becomes a bottleneck — and by then it's too late to do anything but react.
This tool works in two passes: a quick inventory to find concentration, then a closer look at whatever the inventory flags.
Pass 1 — Find concentration
List the capabilities, processes, or areas of responsibility that matter to your team. For each one, fill in:
| Capability / Process | Primary Holder | Backup Holder | Documented? | Transfer Difficulty |
|---|---|---|---|---|
Flag a row if
There's no backup holder and (it's undocumented or transfer difficulty is high).
This alone usually reveals the pattern: who's carrying too much, where documentation is thin, where transfer would be painful.
Review questions
- Which capabilities have no backup holder?
- Which capabilities aren't documented?
- Which capabilities are difficult to transfer?
- Which individuals appear most often as primary holder?
- What would fail if one person were unavailable for two weeks?
Worked example
| Capability / Process | Primary Holder | Backup Holder | Documented? | Transfer Difficulty |
|---|---|---|---|---|
| Release Readiness | Sarah | None | Partial | High |
| Customer Escalations | Mike | Lisa | No | Very High |
| Vendor Coordination | Sarah | None | No | Moderate |
Pass 2 — Understand what's flagged
For rows that triggered the triage rule, identify what kind of dependency it actually is. The type determines what fixes it:
| Dependency Type | Typical Response |
|---|---|
| Explicit knowledge (documentable, just not written down) | Document and transfer |
| Tacit knowledge (built from experience) | Shadowing, mentorship, apprenticeship |
| Judgment calls (interpretation, not rules) | Decision criteria, case review, escalation guidance |
| Escalation dependency (people route to this person) | Formal ownership and routing |
| Integration work (connects separate systems/teams) | Process redesign or responsibility redistribution |
The goal isn't to identify your most important people. It's to identify your most important expertise — and the difference matters. When organizations confuse the two, critical capabilities stay invisible until the person carrying them becomes unavailable. This map makes the dependency visible while there's still time to do something about it.