# How to reduce key person dependency **Canonical URL:** https://skillsmatrixtemplate.com/guides/reduce-key-person-dependency.html **Author:** Dr Alex J. Martin-Smith **Last reviewed:** 27 May 2026 **License:** Free to cite with attribution and link back to the canonical URL. --- ## Definition Key-person dependency is when one person is the only one who can do something the team relies on. Lose them, and the work stalls. The "bus factor" is the number of people who would have to vanish before a task stops. A bus factor of one is the danger zone. Map coverage, not just capability. For each critical skill, count how many people reach the target level. ## Key takeaways - Use this guide to implement key person dependency with the same 0-5 framework as the site methodology. - Write descriptors before you rate, then calibrate managers on what each level looks like in your context. - Review the matrix on a fixed cadence and date every cell when capability changes. - Separate capability ratings from performance conversations. - Link training and hiring plans to named gaps, not generic catalogues. ## Guide body ## What is the first thing to do for key person dependency? World Economic Forum research finds that 39% of workers' core skills will change by 2030, and 63% of employers cite skills gaps as the top barrier (World Economic Forum, 2025). Key-person dependency is when one person is the only one who can do something the team relies on. Lose them, and the work stalls. The "bus factor" is the number of people who would have to vanish before a task stops. A bus factor of one is the danger zone. Map coverage, not just capability. For each critical skill, count how many people reach the target level. ## What is the short answer for key person dependency? To reduce key-person dependency, find the skills that only one person can do, then deliberately build a second and third capable person for each one. Score your team on a single scale, count how many people reach the target level for every critical skill, and treat any skill with a count of one as an urgent risk. Close it with cross-training, documentation, pairing and rotation, then re-check. The goal is simple: no critical task should rest on a single pair of hands. ## Why does building a skills matrix matter now? One pair of hands is a quiet liability Key-person risk rarely announces itself. It sits dormant while the key person is present, then turns into missed deadlines, broken commitments and frantic firefighting the week they are unavailable. The APQC, 2025 of the workforce, on average, is expected to retire or leave within five years, taking hard won knowledge APQC, 2025 rarely or never even attempt to capture the know-how of people who are leaving. SHRM of a person's annual salary is the typical cost to replace them, and that is before counting the knowledge lost. Put those together and the picture is clear. A large slice of your team's knowledge is on the move, most organisations do little to capture it, and replacing the person who held it is expensive. Key-person dependency is where all three risks meet. The good news is that it is also one of the most fixable risks you have, once you can see exactly where it lives. ## What does a real team matrix look like? What key-person risk looks like on a matrix Here is the same six-person team from our skills-gap guide, but read for resilience. Below the grid, each skill gets a coverage count: how many people reach the target of Level 3. The ones and zeros are exactly where your team is one absence away from trouble. ## WHAT THE COVERAGE ROW REVEALS? Nobody covers Data analysis. A count of zero: not one person reaches Level 3. This is a team-wide gap and a resilience hole at the same time, and a clear case for group training. Compliance rests on one person. Only Priya is capable of KYC. If she is away during an audit, the team is exposed. This is the textbook single point of failure and the top priority to fix. Demand forecasting hangs by a thread. Only Tom reaches the target. A quiet skill, but lose him at month-end and the numbers do not get done. Complaint handling is genuinely resilient. Six people capable. Worth knowing, because it tells you where you do not need to spend effort, freeing you to focus on the red columns. ## Choosing How To Spread Knowledge? Five proven ways to build coverage, and when to use each No single tactic fixes key-person risk on its own. The strongest teams combine a few, matched to how critical and how teachable each skill is. Here is how the main approaches compare. ## From Hidden Risk To Visible Plan? The method is free. A ready-made matrix just makes the risks jump out. Everything here works in a blank spreadsheet, and that is a fine place to start. A purpose-built template simply does the counting for you. The grid, the fixed 0 to 5 scale and the maths are already there, the heat map builds itself, and the analytics show how many people are capable of each skill, so single points of failure light up the moment you enter your scores. The Advanced Excel Skills Matrix counts capable people per skill for you, so the columns with only one strong contributor, your single points of failure, are obvious at a glance. The online 5×5 builder maps a small team in your browser, with no sign-up. A fast way to see your The full Excel template: heat map, coverage analytics, automated roadmaps, up to 30 people and 30 yours forever. ## Which tools on this site support key person dependency? - [Excel Skills Matrix Template (£199)](/template.html) ## How should you score skills on the 0-5 scale? Use the same 0-5 descriptors as the PDF and this site's methodology. Define each level in observable behaviours, not labels alone. (See HTML for 0-5 scale table.) See the [methodology pillar](/methodology.html) and [descriptor generator](/descriptor-generator.html) for policy wording. ## What should you add when implementing this online? This web guide adds live links, cited sources, and site tools around the same method as the PDF. Download [reduce-key-person-dependency.pdf](/assets/downloads/guides/reduce-key-person-dependency.pdf) for workshops; use the sections below to implement online. The [methodology pillar](/methodology.html) explains the Upleashed 0-5 framework used across 106. 5M+ assessments. Pair it with the [descriptor generator](/descriptor-generator.html) so raters share one definition of each level. Treat each section as an action checklist: agree evidence rules, run calibration, publish the grid, then review on cadence. The PDF is the narrative; this page is the implementation path with calculators and templates linked in context. Key-person dependency is when one person is the only one who can do something the team relies on. Lose them, and the work stalls. The "bus factor" is the number of people who would have to vanish before a task stops. A bus factor of one is the danger zone. Map coverage, not just capability. For each critical skill, count how many people reach the target level. Ones and zeros are your risks. Close gaps deliberately with cross-training, pairing, documentation and rotation, prioritising the most critical single points of failure first. A skills matrix makes it visible. Read down each column and the single points of failure show themselves instantly. What key-person dependency actually means Key-person dependency is when the ability to do something important sits with one person, and one person only. While they are there, everything runs. The moment they are not, the gap is exposed, and usually at the worst possible time. The "bus factor", explained without the jargon Engineers gave this risk a memorable name: the bus factor. It is the number of people who would have to be hit by the proverbial bus before a project grinds to a halt. The phrase goes back to 1994, when a developer asked, only half-joking, what would happen to the Python programming language if its creator were hit by a bus. A bus factor of one means a single person holds the keys; if they go, the work stops. The higher the number, the safer you are. You do not need a bus for this to bite. Resignations, illness, a long holiday, parental leave, retirement or simply being poached by a competitor all have the same effect. Whenever the knowledge to do a critical task lives in one head, you are exposed, and you usually cannot see it until it is too late. Key-person dependency is a coverage problem, not a talent problem This is the reframe that matters. Your expert is not the problem; they are an asset. The problem is that nobody else can step in. So the fix is never to lean less on your best people. It is to make sure their knowledge is shared, written down and practised by others, so the team can keep going whoever happens to be away. You are building redundancy, in the good, resilient-engineering sense of the word. One pair of hands is a quiet liability Key-person risk rarely announces itself. It sits dormant while the key person is present, then turns into missed deadlines, broken commitments and frantic firefighting the week they are unavailable. The APQC, 2025 of the workforce, on average, is expected to retire or leave within five years, taking hard won knowledge APQC, 2025 rarely or never even attempt to capture the know-how of people who are leaving. SHRM of a person's annual salary is the typical cost to replace them, and that is before counting the knowledge lost. Put those together and the picture is clear. A large slice of your team's knowledge is on the move, most organisations do little to capture it, and replacing the person who held it is expensive. Key-person dependency is where all three risks meet. The good news is that it is also one of the most fixable risks you have, once you can see exactly where it lives. Seven steps to reduce key-person dependency The approach mirrors how you would find any skills gap, but with a twist: instead of asking "is this person good enough?", you ask "how many people are good enough?". Coverage, not just capability, is the thing you List the skills the team genuinely depends on Start with the work that absolutely must keep happening: the tasks where a day's delay causes real damage. Keep it to the vital few, usually 8 to 20 skills. These are the columns you will most want covered by more than one person, so be honest about which ones truly matter rather than listing everything. WATCH OUT Do not treat every skill as critical. If everything is a priority, Score everyone on the same scale Rate each person against each skill using one consistent scale, so a "3" means the same thing for everyone. The Upleashed 0 to 5 framework below works well, with Level 3 ("Capable") as the point at which someone can genuinely work alone. You are not just after who is brilliant; you are after who could safely cover the work if needed. ## Frequently asked questions ### How do I apply key person dependency using this guide? Key-person dependency is when one person is the only one who can do something the team relies on. Lose them, and the work stalls. The "bus factor" is the number of people who would have to vanish before a task stops. ### What is the first step for key person dependency? Agree skills and 0-5 descriptors, then run a calibrated pilot before you scale. ### How often should we refresh ratings for key person dependency? Quarterly is the minimum useful cadence; monthly when regulations, tools, or project mix change quickly. ### Can we use the Excel template for key person dependency? Yes. The £199 template implements this 0-5 method with heat maps and training outputs. PulseAI automates the same scale when you outgrow spreadsheets. ### How does the 0-5 scale keep key person dependency fair? Observable descriptors and evidence rules stop ratings collapsing into opinion or favouritism. ## FAQ ### How do I apply key person dependency using this guide? Key-person dependency is when one person is the only one who can do something the team relies on. Lose them, and the work stalls. The "bus factor" is the number of people who would have to vanish before a task stops. ### What is the first step for key person dependency? Agree skills and 0-5 descriptors, then run a calibrated pilot before you scale. ### How often should we refresh ratings for key person dependency? Quarterly is the minimum useful cadence; monthly when regulations, tools, or project mix change quickly. ### Can we use the Excel template for key person dependency? Yes. The £199 template implements this 0-5 method with heat maps and training outputs. PulseAI automates the same scale when you outgrow spreadsheets. ### How does the 0-5 scale keep key person dependency fair? Observable descriptors and evidence rules stop ratings collapsing into opinion or favouritism. ## References 1. World Economic Forum. (2025). The future of jobs report 2025. https://www.weforum.org/publications/the-future-of-jobs-report-2025/ ## Related - [How to plan cross-training](https://skillsmatrixtemplate.com/guides/plan-cross-training.html) - [How to use a skills matrix for succession planning](https://skillsmatrixtemplate.com/guides/succession-planning.html) - [How to do workforce capacity planning](https://skillsmatrixtemplate.com/guides/workforce-capacity-planning.html) - [How to staff a project team](https://skillsmatrixtemplate.com/guides/staff-a-project-team.html)