Advertise here with Carbon Ads

This site is made possible by member support. 💞

Big thanks to Arcustech for hosting the site and offering amazing tech support.

When you buy through links on kottke.org, I may earn an affiliate commission. Thanks for supporting the site!

kottke.org. home of fine hypertext products since 1998.

Beloved by 86.47% of the web.

🍔  💀  📸  😭  🕳️  🤠  🎬  🥔

TIL: “Key man risk refers to the potential threat a company faces when a crucial employee, often a key executive or expert, is no longer available.” I think KDO has key person risk, although maybe I overestimate my VORP.

Comments  5

Sort by: thread — thread . latest . faves

D
Drew McManus

I’ve long heard this referred to as “bus count.” As in, “How many people need to get hit by a bus before your company is in trouble?”

M
Michael Miller

An HR firm that defaults to the male version of the idea of critical team member (key MAN) risks undermining interest in their content. I skipped the read for that reason. They should know better.

S
sampotts

I worked at a fairly famous place and we had one. single. person. who understood and could code our primary site's CMS. A CMS whose original developers had discontinued supporting. It was frightening. (Years ago; it's all fixed now.)

J
Jean

I feel like eliminating the KeyMan is one of the whole points of this administration.

(
(the other) Moira

Back when I worked as an exec assistant in various NYC finance firms, making sure the CEO and the CFO (for example) were not ever on the same flight was part of my job.

Hello! In order to leave a comment, you need to be a current kottke.org member. If you'd like to sign up for a membership to support the site and join the conversation, you can explore your options here.

Existing members can sign in here. If you're a former member, you can renew your membership.

Note: If you are a member and tried to log in, it didn't work, and now you're stuck in a neverending login loop of death, try disabling any ad blockers or extensions. Or try logging out and then back in. Still having trouble? Email me!