“Bus factor” is an old engineering term with a grim setup. It asks how many people would have to be hit by a bus before a project grinds to a halt. When the answer is one, you have a problem, because everything depends on a single person who is, like all of us, occasionally unavailable and eventually gone. The phrase is morbid, but the question underneath it is one every leadership team should be able to answer, and most cannot.

Try it on your own finance function. If your CFO resigned this afternoon, what happens on Monday? Someone steps in, of course. But how much of what your CFO does is written down, and how much lives in judgment and relationships built over years? How much of the board reporting could another person actually produce? Who holds the banking relationships? What about the quiet workarounds that keep the monthly close on schedule? “We would figure it out” is the answer most teams reach for, and it is worth being honest about what that answer really is. Figuring it out is precisely the slow, costly, error-prone scramble you would most want to avoid.

Teams fall back on “we would figure it out” because they have never looked at the problem closely enough to say anything more specific. Key-person risk feels handled because the org chart looks complete. Every role has a name, every name has a manager, and nothing appears to be missing. The exposure only becomes visible when you go a level deeper and ask what actually determines how badly a departure would hurt.

A handful of things drive that, and none of them appear on an org chart.

The first is coverage. For any critical piece of work, how many people could genuinely do it in practice? When the honest answer is one, you have found a single point of failure.

Then there is documentation. If the owner vanished overnight, could someone reconstruct the work from what is written down, or does it exist only in their head and their sent folder?

Time to competence matters too. Even a capable replacement takes a while to actually run the work at the level it needs. The difference between a two-week ramp and a six-month one is the difference between an inconvenience and a serious gap.

Business impact is the fourth factor. Some work can pause for a month and nobody notices. Other work, the moment it stops, stops revenue, breaches a contract, or misses a filing. The cost of the gap is part of the risk.

Last is likelihood. A process owned by someone eighteen months from retirement, or visibly unhappy, or heavily courted by recruiters, carries more risk than the same process in the hands of someone firmly settled.

Put those together and key-person risk stops being a vague unease and becomes something you can describe plainly. This process, owned by one person, thinly covered, poorly documented, expensive if it fails, and sitting with someone who may not be here next year. That sentence is far more useful than “we would figure it out,” because you can act on it.

It is also a sentence more people are starting to ask you for. Boards increasingly treat key-person and succession risk as a governance matter rather than an HR footnote. Insurers underwriting D&O and key-person cover want to understand where an organization is concentrated. Acquirers and their advisors probe how dependent a target is on a few individuals during diligence, and they discount the price when the answer is worrying. Across all of them, the expectation is moving toward being able to show your work.

The encouraging part is that a bus factor is measurable. Once you can see risk at the level of individual processes, you can put a number on it and watch that number move as you close gaps. It becomes something you manage the way you already manage financial or operational risk, a figure on a dashboard rather than a fear at the back of your mind.

To see your own exposure quantified instead of assumed, request a walkthrough with an Incleon engagement consultant.