I had an interesting discussion with an employee of mine the other day. He's a former high level executive that decided he wanted to go back to coding. Of course, he has the money to do that now, so why not!
Anyway, we discussed the difference between abdicating duties and delegating duties. Very interesting discussion that I hadn't really thought about before.
Abdication of duties involves pushing things out of your processes and letting others do them, while not having any understanding of what they are doing. Basically, a manager who is abdicating instead of delegating is someone that only deals with what they want to deal with.
On the other side, delegation is what happens when a manager understands what needs to be done and then assigns someone to perform or be responsible for that task. A delegating manager designs what they are managing and then delegates the responsibilities of that management to the people underneath him.
Abdication will always come back to haunt the abdicator. Because they didn't design the system and are only dealing with the pieces that they want to see, they will always be in a position where they need outstanding people under them working themselves to death to keep the functions going, and they will always question whether or not the people under them are doing what is correct or not. They have no overal view of the strategy of the area which they have abdicated.
Delegation, on the other hand, knows the strategy for what they are trying to accomplish and has merely delegated functions of that strategy to different people.
Here's a concrete example, related to an IT Manager:
Abdicator: Hires programmers and testers and a sysadmin. Never gives them clear roles and responsibilities, but instead just says that they should “Do their job.” Then, when the project is 5 weeks behind, he gets mad and fires the developers because they weren't doing their job, but never really understood what they were doing because he was busy writing code for the nifty FTP component that they were going to use.
Delegator: Hires programmers and testers and a sysadmin. Understands that the following processes need to happen for a successful project: Design, backups, testing, test cases, coding, etc. Deletgates the design to the architecht, delegates the backups to the sysadmin, delegates the coding to the programmers in conjunction with the sysadmin, deletgates the testing to the testers. Understands that each of these processes must happen and then tracks the progress of these processes. He knows BEFORE the project is late that it's going to be late and why, AND he develops the nifty FTP component. :)
Its a subtle difference, but one that really makes a difference, and in many cases, I think it comes down to processes inside of the department/organization--if the responsibilities are defined, and if the processes are defined, then the delegator knows what's going on. The abdicator doesn't want to get his hands dirty with the processes, and because of that, can't define the roles and responsibilities and everybody flounders.
The things you learn from employees . . .