Well not exactly. You have to look at it from an organisational perspective, and not from an employee perspective.
If you have systems (and that is any function, also cutting onions in the kitchen) that relies so heavily on one employee that you can not continue to operate them without that person then you have a serious issue.
Because you don’t retain employees, and your goal isn’t to keep them forever either. Even if they are happy and stay for 40 years they will eventually retire and then the system tend to break down anyway, and that’s with planned departure. What if your vital employee gets run over by a truck on the way to work?
So from an organisational perspective, it’s not an entire IT system vs one employee. It’s removing a flawed and dangerous system from your organisation.
Some people will argue that employees who design such systems aren’t worth keeping to begin with. I would agree, if the world was perfect, but it’s not.
If you have systems (and that is any function, also cutting onions in the kitchen) that relies so heavily on one employee that you can not continue to operate them without that person then you have a serious issue.
Because you don’t retain employees, and your goal isn’t to keep them forever either. Even if they are happy and stay for 40 years they will eventually retire and then the system tend to break down anyway, and that’s with planned departure. What if your vital employee gets run over by a truck on the way to work?
So from an organisational perspective, it’s not an entire IT system vs one employee. It’s removing a flawed and dangerous system from your organisation.
Some people will argue that employees who design such systems aren’t worth keeping to begin with. I would agree, if the world was perfect, but it’s not.