I manage a team, and I have to disagree with this article. It is often the employee. For example, I have a client that is going live tonight. Their environme

I manage a team, and I have to disagree with this article. It is often the employee. For example, I have a client that is going live tonight. Their environment consists of 14 Linux boxes that all need apps deployed, chroot jails setup, monitoring and deployment scripts written or modified, etc. I assigned it to one of my engineers weeks ago, but he works so slowly that most work isn't completed yet. Yesterday, the day before go live, I had to take it over and completed 90% of the work in a single long day. It's not that he isn't trained... These are basic Linux engineer tasks. It's that he works so slowly, and has to ask so many questions "how did you want me to create the user accounts?" - "I don't know, with useradd, perhaps?" Then 2 weeks later, I say "the client is asking if they can login to their boxes now; are their user accounts created yet?" - "I'll get to that today, he replies." You might think that I must have hired him, so it's my fault if he works too slowly and asks too many questions, or makes too many mistakes to be of much use. Unfortunately I didn't hire him. The bottom line is that a lot of employees are just poor performers, and when someone that does good work at a high rate of speed can do it better themselves, in less time, they're going to do it.