Monday I wrote about the welder every engineer in the building walks over to consult. The one the shop cannot promote, because moving him means the hard jobs start coming back wrong. If that essay named someone on your team, or named you, this is the part where we do something about it.
Most leaders treat this as one problem. There are two.
The first is capability risk. The team cannot function without this person, and that exposure is real whether or not they ever leave.
The second is retention risk. This person has every reason to take the next offer, because the place that relies on them most is the place doing the least with their career.
You cannot fix one by fixing the other. Promote them out of the bind and the hard jobs still come back wrong. Build redundancy and stay silent, and they read it as you quietly arranging their replacement. Both have to move at once.
Run the two-week test first
Before any of the moves below, do this. Picture the person gone for two weeks. Not quit. Just out, no phone.
Write down every task, decision, and judgment call that stalls or routes to someone scrambling. Be honest about the small ones, the “oh, only she knows the trick for that” ones. That list is your dependency map.
(I have been the leader who ran a version of this test with my IT team and then quietly hoped nobody would quit. Hope, it turns out, is a prayer with a spreadsheet attached.)
What the list actually tells you
The list you just wrote looks like proof of how good they are. Read it again. Every line is a place the work lives in one head and nowhere else. That is an audit of how exposed you are, and you have until their next offer to close it.
