Every executive team I talk to has an org chart, and most of them trust it more than they should. Not as a directory, but as a risk map. When the question comes up of where the organization is exposed if someone leaves, the chart is what people reach for. They look at the boxes near the top, the ones with the most reports underneath them, and they reason about risk in proportion to altitude. The higher the box, the bigger the perceived exposure.
This is a reasonable instinct and a misleading one. The org chart was designed to show reporting relationships and span of control. It was never designed to show where the work that actually keeps the business running is concentrated. Those two things overlap, but not as much as the chart’s clean hierarchy implies. The gap between them is where unmanaged key-person risk lives.
Most leaders have seen the pattern at least once. Someone leaves, often not a particularly senior person, and over the following months a series of small things stop working in ways nobody quite predicted. A quarter-end close that used to take four days takes nine. A vendor renewal lapses because the person who understood the terms is gone. A customer relationship cools because the history behind it walked out the door. None of these show up as a catastrophe. They show up as a slow, expensive tax that the org chart gave no warning about, because the person who left was three boxes down and didn’t look like a risk.
The title gets backfilled in weeks. The work takes months.
Start with the asymmetry at the center of the problem. When a key person leaves, the title is usually not hard to replace. There are candidates, internal and external, who can hold the role. The job gets posted, a successor is named, the box on the chart gets a new name in a matter of weeks.
What takes months, if it can be reconstructed at all, is the knowledge that person carried about this operation. Not the general competence of the role, which the successor probably has, but the particulars: the exceptions that get made and why, the relationships that rest on personal history, the documented process that hides an undocumented workaround the team has leaned on for years. That knowledge lives in the work, not the title, and the work is invisible on the chart.
This is why title-level succession planning so often misses the real exposure. A plan that says “if the VP of Finance leaves, here is the successor” has answered a question about the box. It has not answered the question that matters: when this person leaves, what work stops happening at the level it was happening, and how long until someone else can do it as well?
One person is rarely one risk
Consider a role that sounds unremarkable on an org chart: a Senior Analyst in a finance function. One box, one reporting line, one name. From the chart’s point of view, the exposure is singular and modest.
Look at the actual work and the picture fractures. This particular Senior Analyst owns the revenue forecasting model the leadership team plans against. She also runs the regulatory reporting that keeps the company compliant on a hard quarterly deadline. And she handles the vendor negotiations for a set of contracts that represent real money. Three distinct bodies of work, each one critical, each calling for different knowledge and a different backup, and eventually a different successor.
If she leaves, “name a successor for the Senior Analyst” is the wrong response, because there may be no single person who can absorb all three. The right response is three separate questions. Who covers revenue forecasting tomorrow if she’s out? Who can run regulatory reporting against the next deadline? Who holds the vendor relationships well enough to keep them from slipping? The exposure was never the role itself but the three pieces of work it happened to contain, and the org chart showed none of them.
This is the common case, not a special one. Most important roles are bundles of distinct critical work, often assembled by accident of who was available when the work appeared. The bundling is invisible on the chart, and frequently invisible to leadership, until the bundle comes apart.
The right unit of risk is the work, not the box
If the org chart is the wrong map, what is the right one?
The unit that carries risk is the area of business responsibility: the discrete piece of work that creates exposure if its owner walks out the door. We call it a Key Value Process: revenue forecasting, regulatory reporting, the customer-success playbook a long-tenured manager built from scratch, the legacy integration only one engineer understands. Every one of these is something the business depends on, with an owner, a level of documentation, a pool of people who could step in, and a degree of difficulty in replacing the knowledge it holds. Each can be assessed on its own terms.
This is a more demanding way to look at the organization, and that is the point. It forces a set of questions the org chart lets you avoid. What are the processes this business depends on? Who owns each one? How well is each documented versus held in someone’s head? If the owner left tomorrow, who could cover it immediately, and who is being developed to take it over for good? These questions have answers. They just are not answers you can read off a chart of reporting lines, because reporting lines are not where the dependency lives.
There is a useful piece of evidence behind the intuition that so much depends on individuals. Research widely cited in the knowledge-management field finds that roughly 42% of the knowledge employees use to do their jobs is held by those individuals alone: not written down, not in a system, not recoverable without them. That is the material the org chart cannot see. When a person leaves, a meaningful share of what they knew has no representation anywhere except the work they were doing, and the work is what title-based planning does not track.
What changes when you plan around the work
Reframing risk from the box to the work changes the practical job of succession planning. Coverage stops being a yes-or-no question. Instead of asking whether there is a successor for a role, you ask, for each critical process a person owns, who provides immediate backup and who is the longer-term successor. Those are different jobs. A backup is emergency cover, the person who keeps regulatory reporting moving if the owner is unexpectedly out next week. A successor is someone being developed to own the work for good, on a readiness timeline you can track. Organizations that blur the two often believe they are covered when they have neither.
Development gets a target as well. Generic talent programs, the kind that produce individual development plans nobody can tie to a business need, give way to development aimed at the processes the business actually depends on. The path from where someone is today to readiness on a named Key Value Process is concrete, and so is the return on that investment. You are no longer training people in the abstract. You are closing an identified exposure.
And the picture stops going stale the moment it is built. The annual-review model fails less because of its cadence than because the organization changes every week, as people join, leave, move, and get promoted, while a yearly snapshot cannot tell you how out of date it already is. When risk is tracked at the level of the work, each of those changes becomes a signal that updates the picture, rather than the slow erosion of a document that looked authoritative right up until the moment it was needed.
Making it a number the board can use
The reframe also makes something possible that title-based planning never could: a real measurement.
When the unit of risk is a process rather than a box, each process can be scored, on how critical it is, how concentrated its ownership is, how well it is documented, and how covered it is by backups and successors. Those scores roll up. For the first time the answer to “how exposed are we to key-person risk?” becomes a number you can present, compare across departments, and trend over time, instead of a qualitative shrug. The board conversation moves from “do we have a succession plan?”, a yes-or-no that everyone knows is mostly theater, to “here is where our exposure concentrates, here is how it has changed since last quarter, and here is what we are doing about the worst of it.”
This is where the cost of getting it wrong is easiest to see. The data on the gap is not flattering. In a 2023 survey of board directors, Gartner found that only about half had a written succession plan for their current CEO, and that is the one role boards watch most closely. Broader research from SHRM finds a majority of HR professionals report no formal succession plan at all. And when a key person does leave, the cost of replacing them runs, by SHRM’s own estimates, to somewhere between half and twice their annual salary, before you count the institutional knowledge that leaves with them. The exposure is large, it is widespread, and most organizations are measuring it with a tool, the org chart, that was built for something else entirely.
Getting the frame right
None of this requires believing the org chart is useless. It is an excellent map of authority and reporting. It is the wrong map for risk, and the trouble starts when it gets used for a job it was never designed to do.
The shift that matters is a narrow one. Stop reasoning about continuity risk in terms of who reports to whom, and start reasoning about it in terms of the work the organization depends on and who owns it. The roles will still matter. But the roles are containers, and the risk is in the contents. Once you can see the contents, name the critical processes, find their owners, measure how exposed each one is, most of what felt like an unknowable, soft problem turns out to be concrete, assessable, and addressable.
That visibility is what most organizations are missing, and it is what Incleon Vantage was built to provide: an always-current map of the work the organization depends on, scored for risk and backed by the plans that keep it covered. The frame comes first, though. If you finish this and find yourself looking at your own org chart with a little more suspicion, asking not who sits in which box but what work would stop if that box emptied, then the more useful conversation has already started.
If you would like to see what mapping your organization’s critical processes would surface, the exposure your current succession approach cannot show you, that is the conversation our team has every week. Book a Vantage briefing