Understanding Delegation

The widely accepted definition of delegation is "the assignment of a responsibility or authority to another person, usually from a manager to a subordinate." In this view of delegation, the manager transfers some of the manager's responsibilities — or some of the manager's authority — to a subordinate. If you believe you're delegating, in the sense that you're transferring responsibility or authority from yourself to a subordinate, you probably view yourself as responsible for getting something done — in effect, as a doer. And one of your tasks is to allocate some of your tasks to other doers.

That is not the most effective role for a manager. It is, however, how micromanagers view their roles.

In one sense, using the term delegation to describe what managers do is a tragic error that encourages micromanagement. Using the term implies that what we call delegation is the transfer of responsibility from manager to subordinate. In that sense, the delegation concept is itself problematic, because that isn't what happens when effective managers do their actual jobs.

Here are three insights about managers' jobs.

Don't do; meta-do

Effective managers Effective managers know that
the manager's job is not
to do, but to meta-doknow that the manager's job is not to do, but to meta-do. Managers allocate tasks to people who execute those tasks, and then the managers do what it takes to enable their subordinates to accomplish those tasks. Effective managers lead people and arrange for resources and infrastructure to support those people. They fly political "air cover" when necessary and they influence the organizational culture. They don't manage the tasks of the people who do the tasks. Managing the tasks is what the people who do the tasks do.

The hands-on manager role is dangerous

Some managers' jobs do require that they actually execute some tasks. They're in jobs sometimes described as "hands-on manager." This kind of job is a setup for failure. It's very difficult to keep straight in one's mind what work is to be executed personally, and what work is to be allocated to subordinates. The hands-on manager job creates inherent conflicts of perspective. Someone in this kind of job is likely to get into trouble about delegation, because the job is so poorly defined. See "The Risky Role of Hands-On Project Manager," Point Lookout for April 23, 2008, for more.

Manager's responsibilities differ from subordinates' responsibilities

Managers are indeed ultimately responsible for the work their subordinates do, but it's a kind of responsibility that differs from the responsibility the subordinates carry. The manager's responsibility is most evident when things don't happen as planned. When things do happen as planned, the manager's responsibility is to ensure that the people who executed those tasks get the credit they're due. When things don't happen as planned, the manager's responsibility is to investigate what went wrong, and then to see that corrective actions are taken so that things work better next time.

So if you feel that it's your job as a manager to delegate a task, there's a good chance that you were holding onto that task yourself. And if you were holding onto it, you might have been doing what micromanagers do.  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. More info

Your comments are welcome

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.

This article in its entirety was written by a human being. No machine intelligence was involved in any way.

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.

Related articles

More articles on Personal, Team, and Organizational Effectiveness:

Taming the Time Card

Filling out time cards may seem maddeningly trivial, but the data they collect can be critically important to project managers. Why is it so important? And what does an effective, yet minimally intrusive time reporting system look like?

Problem Defining and Problem Solving

Sometimes problem-solving sessions are difficult because we get started solving a problem before we know what problem we're solving. Understanding the connection between stakeholders, problem solving, and problem defining can reduce conflict and produce better solutions.

Remote Facilitation in Synchronous Contexts: III

Facilitators of synchronous distributed meetings (meetings that occur in real time, via telephone or video) can make life much easier for everyone by taking steps before the meeting starts. Here's Part III of a little catalog of suggestions for remote facilitators.

Pseudo-Collaborations

Most workplace collaborations produce results of value. But some collaborations — pseudo-collaborations — are inherently incapable of producing value, due, in part, to performance management systems, lack of authority, or lack of access to information.

Six Traps in Email or Text: I

Most of us invest significant effort in communicating by email or any of the various forms of text messaging. Much of the effort is spent correcting confusions caused, in part, by a few traps. Knowing what those traps are can save much trouble.

See also Personal, Team, and Organizational Effectiveness for more related articles.

Forthcoming issues of Point Lookout

Coming September 24: Time Is Not a Resource

In the project management community, it's often said that time is the most precious resource. Although time is indeed precious, to regard it as a resource — like finance, equipment, or people — can be a dangerous mistake. Time is not a resource. Available here and by RSS on September 24.

And on October 1: On the Risks of Obscuring Ignorance

A common dilemma in knowledge-based organizations: ask for an explanation, or "fake it" until you can somehow figure it out. The choice between admitting your own ignorance or obscuring it can be a difficult one. It has consequences for both the choice-maker and the organization. Available here and by RSS on October 1.

Coaching services

I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrenaXXxGCwVgbgLZDuRner@ChacDjdMAATPdDNJnrSwoCanyon.com or (650) 787-6475, or toll-free in the continental US at (866) 378-5470.

Get the ebook!

Past issues of Point Lookout are available in six ebooks:

• Get 2001-2 in Geese Don't Land on Twigs (PDF, )
• Get 2003-4 in Why Dogs Wag (PDF, )
• Get 2005-6 in Loopy Things We Do (PDF, )
• Get 2007-8 in Things We Believe That Maybe Aren't So True (PDF, )
• Get 2009-10 in The Questions Not Asked (PDF, )
• Get all of the first twelve years (2001-2012) in The Collected Issues of Point Lookout (PDF, )

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-1000 words in your inbox in one hour. License any article from this Web site. More info