Some Roles Carry More Risk Than Their Title Suggests

Ask a leadership team to name their critical roles, and the list almost always comes from the org chart: vice president and above, maybe a director or two below that line. It looks complete, because everyone on it holds real authority.

I understand why teams start there. Titles usually do track authority, and starting from the org chart is the fastest way to get a first list on paper.

Authority is only one measurement, though. It tells you who has the standing to decide. What actually breaks when one specific person leaves is a separate question: dependency. A role can carry plenty of authority and very little dependency, or the reverse. The org chart only measures authority.

I once built a critical-role list across a 13-plant manufacturing organization. One of the roles that made that list, over real pushback from the executive team, was a metallurgist several layers below a vice president. The objection was reasonable at first glance. Modest title, no meaningful span of direct reports, nowhere near the top of the chart.

In practice, that metallurgist was the only person on site who could read a batch and know whether it had been mixed correctly before it became scrap, a shipment delay, or a safety incident. Output would have slowed the day that person left. The judgment involved lived in one head, and it had never been written down anywhere else. A strong outside hire would have needed real time on the floor before the plant trusted their calls the way it trusted the person already doing the job.

Leaders often challenge a role like this by asking whether it is hard to fill. That reflects labor-market conditions, and those conditions say nothing about what the organization loses while the seat sits empty, or gets filled by someone who has not yet had time to get up to speed.

The same logic applies outside manufacturing. A law firm's associate who is the only person who understands a client's decade-old contract history is exposed the same way. So is a claims adjuster who is the only one who knows why a specific account has always been handled a certain way. A standard list would skip every one of these roles.

Look at this list once, put it back on a shelf, and it stops working. The value comes from checking it on a set rhythm. When I ran this process, we came back every quarter and asked the executive team one question: has anything changed? Some quarters the answer was yes: a role that mattered three months ago no longer did, or one nobody had flagged suddenly did. That habit is what kept the list accurate. Skip it, and the list you built in January is describing a business that no longer exists by summer.

I call these torque moments: an outage, a plant startup, a systems cutover, any point where the organization is already under pressure and a leadership gap makes it worse. An organization hardly ever discovers a role like this was so consequential during an uneventful quarter. It discovers it the day the person leaves, and nobody else can do the work.

None of this shows up on an org chart, and that's exactly the point.

Putting it into practice does not require a new process, only a different question. For every role currently excluded from your critical-role list because the title looks too small, ask what specifically would slow, stall, or fail if that person left tomorrow. If the honest answer involves a customer relationship, a piece of technical judgment, or a body of knowledge that exists in one place, the role belongs on the list regardless of where it sits on the chart.