One of the most important benefits of delegating responsibility I experienced comes from the founder of a company who groomed many lieutenants, giving them authority and responsibility while removing obstacles.
Taking time to groom many lieutenants is probably one of the biggest responsibilities the founder has to take, I believe.
Agreed. As a manager, at any level, when you delegate you still own the problem. If the person or team you delegated to does not deliver a solution, it is your duty to step in and take corrective action.
So, I get what your saying, no one can do it all. No man is an island and all that stuff.
One thing that can not ever be deligated is responsibility.
The CEO can deligate tasks, projects, and work, but not responsibility. As a member of the board, if the CEO comes into the board meeting and says, "I told the team to finish the software, and they did not get it done, so not my fault." what would you do? Toss him out on his rear I would guess.
Delegating to the right person, giving them the tools to complete the job, and the support they need is the way to successfully delegate. The EE CEO does not give up responsibility for their company and the work that needs to be done.
When the team succeeds, as the boss, all the accolades go to them. When they fail, it is your failure. That is why it is hard to be the boss.
My Mom the Radio Star Max MaxfieldPost a comment I've said it before and I'll say it again -- it's a funny old world when you come to think about it. Last Friday lunchtime, for example, I received an email from Tim Levell, the editor for ...
A Book For All Reasons Bernard Cole1 Comment Robert Oshana's recent book "Software Engineering for Embedded Systems (Newnes/Elsevier)," written and edited with Mark Kraeling, is a 'book for all reasons.' At almost 1,200 pages, it ...