Every leadership team knows the feeling. A senior person resigns, takes a holiday, or goes quiet for a week, and something significant either stalls or lands on the desk of whoever is available. The moment passes. But what it exposes does not.
The businesses most affected by key-person dependency rarely experience it as a crisis. They experience it as friction: decisions that slow down because one person is at capacity, opportunities that stall because one relationship is unavailable, growth that requires scaling something the business has never been able to scale. The key person keeps showing up, so the cost of depending on them never quite becomes urgent enough to address. Meanwhile, the ceiling on what the business can do is set not by its market, its capital, or its strategy, but by the bandwidth of one or two individuals who have become structurally irreplaceable.
That ceiling is expensive. It limits how fast the business can take on new work, how confidently it can commit to growth targets, and how attractive it looks to anyone evaluating it from the outside. Key-person dependency is one of the most widely acknowledged risks in business and one of the least addressed, because the business keeps functioning well enough to defer the conversation. The cost of deferring it, however, compounds quietly in the background every year that nothing structural changes.
Mercer and Marsh's 2024 People Risk Report, which surveyed over a thousand risk and HR professionals, found that 34 percent of organisations cited dependency on key individuals and inadequate succession planning as a primary concern. The concern is real and widely felt. What has changed is that it is now structurally solvable in a way it has not been before.
The cost the P&L never shows
The visible cost of key-person dependency is the disruption that follows when the key person is unavailable. The invisible cost is larger and more persistent: the ceiling it places on the business every day that person is present.
When decisions route through one individual, the pace of the business is governed by their capacity. When client relationships are held by one person, the business's ability to win new work, expand existing accounts, or survive that person's departure is constrained by a single point of failure. When operational knowledge lives in one person's head, the business cannot be documented, delegated, or scaled without them.
Research published in MIT Sloan Management Review in December 2024 found that organisational bottlenecks are routinely mismanaged because businesses address them piecemeal rather than systemically, fixing the most visible constraint without addressing the underlying resource and workflow architecture that generates bottlenecks in the first place. The result is that relieving pressure in one area simply shifts it elsewhere. The business feels like it is making progress. The structural dependency remains.
That dependency also has a market price. In formal business valuations, key person discounts of between 5 and 25 percent are routinely applied to the assessed value of a business where performance, relationships, or decision-making are concentrated in one individual, with higher discounts applied where the dependency is more acute or succession planning is absent. The reduction is not a reflection of poor performance. It is an acquirer or investor pricing the risk that the performance does not continue without that person present.
Where key-person dependency actually lives
The risk concentrates in different places depending on the nature and scale of the business. Recognising it requires looking beyond the obvious.
In a founder-led professional services firm with fifty people, the dependency is almost always relational. The founder holds the senior client relationships personally. New business flows through their network. Account growth depends on their involvement in the conversation. The firm can deliver excellent work, but its commercial ceiling is the founder's personal bandwidth.
In a mid-market manufacturing business with three hundred staff, the dependency tends to be operational. One production manager holds the institutional knowledge of the plant: the supplier relationships that took years to build, the workarounds that keep ageing equipment running, the scheduling logic that lives in a spreadsheet and in their head simultaneously. The business runs because they show up, but the risk profile of that business changes materially when they do not.
In a high-growth technology business, it is frequently architectural. One engineer understands the codebase in its entirety. Others work within it, but decisions about how it scales, where it is fragile, and what it can support depend on one person's comprehension of the whole. That dependency does not appear on any risk register until something breaks at the worst possible moment.
The form the dependency takes matters less than the pattern it creates: a business whose capacity, quality, or commercial performance is bounded by the continued presence of one individual in a role that was never designed to be held by systems.
The view from inside
What rarely surfaces in conversations about key-person dependency is that the key person themselves is often the most acutely aware of the problem.
Senior leaders and founders who have become operational bottlenecks did not set out to be. They became indispensable because the business needed them to be, and because nothing was ever built to reduce that need. Many carry a version of the same frustration: they can see the decisions that should not require them, the approvals that should flow without their sign-off, the work that should move faster than it does. They want to step back but the structure does not allow it.
The ask that comes up repeatedly in conversations with C-suite leaders is more immediate than succession planning. It is a system that lets the business move faster without them being in every critical path: something that holds the logic of how decisions get made, routes the right information to the right people, and handles the operational cadence that currently requires their personal involvement. The goal is not to remove them from the business. It is to free them for the work that actually requires their judgment: the strategic decisions, the relationships, the problems that genuinely need the most experienced person in the room.
Succession planning matters, and most serious leadership teams have some version of it. Finding a successor with the same capabilities, relationships, and institutional knowledge as the person they are replacing is genuinely difficult. The businesses that reduce that difficulty most effectively are the ones that have already systematised what the key person holds, so the incoming person steps into a role supported by infrastructure rather than one held together by the individual judgment of whoever occupied it last.
What changes when the infrastructure changes
An Intelligent Operating System addresses key-person dependency at the level where it actually lives: in the processes, decisions, and knowledge flows that currently require a specific person to function.
For the founder-led professional services firm, this means the client onboarding, account management cadence, and reporting processes that flow through the founder are systematised so that senior practitioners can manage them independently. For the manufacturing business, the scheduling logic, supplier communication, and production reporting the operations manager holds personally are embedded in a system that surfaces the same decisions and flags the same exceptions, regardless of who is looking at it.
In each case, the key person's judgment, relationships, and expertise remain valuable. The operational bottleneck they have become does not. A business that has systematised what its key people hold can scale what they contribute, deploy their judgment where it adds the most value, and present to any acquirer, investor, or partner as a business whose performance does not depend on the continued presence of specific individuals.
A business that has systematised what its key people hold does not just reduce its risk profile. It changes what growth means. Every new hire, every new client, every new market entered compounds through infrastructure that was built to carry the weight rather than inherited from necessity. For businesses that have been growing around their key people rather than through a system built to support that growth, the shift is less about risk reduction than about what becomes possible once the constraint is removed.
Karst is an operations and technology firm that designs and implements Intelligent Operating Systems to deliver commercial outcomes. Built by operators. Powered by AI. Measured in outcomes.
