The one person who knows how it works
· 2 min read · Tim Cooley

My grandmother had one kitchen drawer that only she could open right. You had to lift and pull at the same time, and if you didn't know that you'd walk away with the handle in your hand. Everyone in the family knew which drawer it was and just avoided it when she wasn't home.
We have a version of that at work, and I think most companies do. One person who knows how the reconciliation actually clears, or how the old system talks to the new one, or which of the three approval paths is the real one. Everyone knows who it is. When they go on vacation, work quietly rearranges itself around them, and nobody says why out loud.
I've done this one myself. Years ago we had someone who was the only person who understood how a legacy billing process actually worked — not the documented version, the real one, with two manual steps nobody had ever written down. When she wanted a real vacation, two full weeks, no laptop, I made sure nothing landed on her desk before she left. I felt good about that. I told myself I was protecting her time off.
What I wasn't doing was fixing the actual problem, which was that the company had exactly one person who could do that job, and I knew it, and I let two more years go by before it caught up with us. I called it respecting her vacation. It was also me avoiding a harder conversation — sitting with her long enough to document the real process, or cross-train someone else, which costs time out of both their weeks and admits the shortcut had been a shortcut for two years.
I'd been doing a worse version of this for a long time before I heard it called bus factor — how many people would need to get hit by a bus before the thing stops working. Ours was one, in more places than I wanted to count when I actually looked. Protecting her time off was kind. It also meant the fix stayed exactly as far away the following year.
What I still haven't figured out is how to raise it without it landing on the person like an accusation — right after they've spent years being the only one holding something up, being told the real message is you're replaceable now. I don't think I've found a way to do that that doesn't cost something on the way in.
If you've actually fixed this without it stinging on the way there, what did you do?
perspectiveoperationsbus-factorsingle-point-of-failure