Guidelines for Delegation
by Rick Brenner
Mastering the art of delegation can increase your productivity, and help to develop the skills of the people you lead or manage. And it makes them better delegators, too. Here are some guidelines for delegation.
Admiral Edward Ratcliffe Garth Russell Evans, 1st Baron Mountevans of Chelsea. Earlier in his career, he was second in command of the British Antarctic Expedition 1910 (also known as the Terra Nova
expedition). He was in command of the Terra Nova
from Cardiff to Capetown, where the expedition leader, Capt. Robert F. Scott, caught up with the Terra Nova
by fast mail boat. The plan had been for then Lt. Evans to be in command until the ship reached Melbourne, where Capt. Scott would be waiting and then assume command. But having caught up with the Terra Nova
early, in Capetown, Capt. Scott assumed command there, thus infringing — or rescinding without cause — previously delegated authority. Lt. Evans hid his feelings, but he nevertheless took this change of plan as a slur, and thus the tension between the two leaders began to take hold and bloom into a serious problem of leadership. For more, see Roland Huntford's history, The Last Place on Earth.
Photo obtained from Wikipedia
Delegating is the investing of responsibility and authority from you to your subordinates. It creates reserves for you and gives your subordinates a chance to grow. Too often, though, troubles arise because we don't have a clear understanding of how to delegate effectively. Here are some guidelines you might find helpful.
- You can't delegate your own accountability
- Even though you might have delegated something, you remain accountable for it. Your subordinate is accountable to you, but you are still accountable for whatever you delegated.
- Be prepared to rescind
- Sometimes, things don't work out. You might have delegated inappropriately, or your subordinate might fail for some reason. Since you always retain the responsibility to revisit your decision, be prepared to do so, but never rescind without cause.
- Your subordinate has final say
- Even if you believe that your delegation decisions were correct, your subordinates control their own levels of passion and commitment. They might agree to accept what you delegate, but unless they're truly committed, delegation can create trouble.
- Keep your promises
- When what you delegate is unappealing, there's a temptation to promise something in exchange. If you do promise something, keep that promise. If you can't keep the promise, don't make the promise.
- The greater the risk, the more important is delegation
- In risky situations, emergencies can occur, because when things go wrong, they sometimes go wrong in herds. To create reserves to manage these emergencies, delegate.
- Delegate fully
- When you delegate something, delegate it fully. You remain accountable for it, but it's no longer yours. Get out of the way.
- Delegate authority, not just work
- Delegating the work of a task, and not the authority to determine the manner of accomplishing it, can be demoralizing for the subordinate. This is particularly true of tasks requiring creativity, insight, or commitment.
- Never infringe delegated authority
- Infringing delegated You can't delegate
your own accountabilityauthority is demoralizing and creates problems for future delegation. If you feel the need to infringe, but you don't see a need to rescind the delegation, you're probably over the line.
- Have an inform-as-soon-as-you-know norm
- Make an agreement that each of you will inform the other as soon as you learn anything that changes the risk profile of whatever you delegated. Your subordinate agrees to alert you when trouble looms, and you agree to tell your subordinate about any enhanced risks. It's a trusting partnership.
- Establish checkpoint expectations
- Since you remain accountable for whatever you delegated, you have a right to reasonable monitoring of progress. Work out with your subordinate a mutually acceptable set of checkpoints, and stick to them, asking for status reporting neither more frequently nor less frequently than you agreed.
Most important is clear, two-way communication between you and your subordinate. Mutual understanding of your mutual agreement is essential to a successful delegation experience. OK, now. You can take it from here. Top Next Issue
Is every other day a tense, anxious, angry misery as you watch people around you, who couldn't even think their way through a game of Jacks, win at workplace politics and steal the credit and glory for just about everyone's best work including yours? Read 303 Secrets of Workplace Politics, filled with tips and techniques for succeeding in workplace politics. Order Now!
Your comments are welcome
Would you like to see your comments posted here? Send me your comments by email
, or by Web form
About Point Lookout
Thank you for reading this article. I hope you enjoyed it and found it useful,
and that you'll consider recommending it to a friend
Point Lookout is a free weekly email newsletter. Browse the archive
of past issues. Subscribe for free.
Support Point Lookout by joining the Friends of Point Lookout,
as an individual or as an organization.
Do you face a complex interpersonal situation? Send it in,
anonymously if you like, and I'll give you my two cents.
More articles on Workplace Politics
- When All Your Options Are Bad
- When you have several options, and all seem politically risky, what can you do? Here are two guidelines to finding your way to a good outcome.
- How to Undermine Your Subordinates
- People write to me occasionally that their bosses undermine them, but I know there are bosses who want to do more undermining than they are already doing. So here are some tips for bosses aspiring to sink even lower.
- What Insubordinate Non-Subordinates Want: Part I
- When you're responsible for an organizational function, and someone not reporting to you won't recognize your authority, or doesn't comply with policies you rightfully established, you have a hard time carrying out your responsibilities. Why does this happen?
- The Politics of the Critical Path: Part II
- The Critical Path of a project is the sequence of dependent tasks that determine the earliest completion date of the effort. We don't usually consider tasks that are already complete, but they, too, can experience the unique politics of the critical path.
- Telephonic Deceptions: Part I
- People have been deceiving each other at work since the invention of work. Nowadays, with telephones ever-present, telephonic deceptions are becoming more creative. Here's Part I of a handy guide for telephonic self-defense.
See also Workplace Politics and Personal, Team, and Organizational Effectiveness for more related articles.
I offer email and telephone coaching at both corporate and individual rates.
Contact me for details at rbrenner@ChacoCanyon.com
or (617) 491-6289, or toll-free in the continental US at (866) 378-5470.
Get the ebook!
Past issues of Point Lookout
are available in six ebooks:
Reprinting this article
Are you a writer, editor or publisher on deadline?
Are you looking for an article that will get people talking and get compliments flying your way? You can have 500 words in your inbox in one hour. License any article from this Web site. More info
- The Race to the South Pole: Ten Lessons for Project Managers
- On 14 December 1911, four men led by Roald Amundsen reached the South Pole. Thirty-five days later, Robert F. Scott and four others followed. Amundsen had won the race to the pole. Amundsen's party returned to base on 26 January 1912. Scott's party perished. As historical drama, why this happened is interesting enough, but to project managers, the story is fascinating. Lessons abound. Read more about this program. Here's an upcoming date for this program:
- The Race to the South Pole: The Power of Agile Development
- On 14 December 1911, four men led by Roald Amundsen reached the South Pole. Thirty-five days later, Robert F. Scott and four others followed. Amundsen had won the race to the pole. Amundsen's party returned to base on 26 January 1912. Scott's party perished. As historical drama, why this happened is interesting enough. Lessons abound. Among the more important lessons are those that demonstrate the power of the agile approach to project management and product development. Read more about this program. Here's an upcoming date for this program: