
A USA road sign indicating a winding road ahead, with an initial curve to the right. Road signs like these aren't accurate to the finest detail. They convey a general warning and trust the motorist to adapt that warning to the details of the road. That's a stance that many delegators would do well to adopt.
Image courtesy Wikimedia.
If you work in almost any role in a project-oriented organization, you probably know too well what micromanagement means. Briefly, micromanagement is inappropriate interference by supervisors in the work of subordinates. [Brenner 2007.1] It is a style of supervision in which the supervisor insists on receiving reports of progress on the subordinate's work that are so detailed and frequent that they deprive the subordinate of any meaningful degree of autonomy. The demands of the supervisor can become so burdensome that they constrain the subordinate's productivity. In extreme cases, involvement of the supervisor in the work of the subordinate can be so intense that it compromises the supervisor's own performance. Although this description is expressed in terms of an individual subordinate, it applies to subordinate groups or teams as well.
Microdelegation is to delegation as micromanagement is to management. To delegate to someone is to invest that person with some degree of Responsibility, Authority, and Accountability relative to some element of the organizational mission. [Brenner 2024.1] For example, the Chief Financial Officer might delegate to you the task of coordinating a "red team" review of the quarterly financial reports. Then, to some extent, you would be responsible for organizing the review — recruiting a team, setting a time, gathering materials, producing a report, and so on.
To microdelegate is therefore to delegate in such a way as to compromise the autonomy of the delegatee. The microdelegating supervisors in our example omit no detail in charging their subordinates — they list the titles of the financial reports, they specify the conference rooms, the names of the attendees, the dates and times of the meetings, and so on.
My use of the term microdelegation
Having never seen the word microdelegation, I felt free to define it in this way. But as it turns out, others have already used it in other ways. Emal uses the term to denote a more effective style of delegation. [Emal 2024] In almost the opposite sense, more closely aligned to how I use the term here, Morrison notes that, "Learning and growth can only happen if there's space for it."
Now, having learned that the term is in use in such different ways, I feel free to appropriate it in the way I need it here.
The costs of microdelegating
The Microdelegation is to delegation as
micromanagement is to managementurge to microdelegate probably springs from sources similar to the sources of the urge to micromanage. It's reasonable to suppose that the microdelegator fails to balance two attributes of microdelegation — first, the approach to the task, and second, the self-esteem of the subordinate.
- The approach to the task
- Microdelegators can tend to be resistant to the change in their own roles that is an element of any healthy delegation. As Morrison puts it, "I wonder if micro-delegation, like micromanagement, reflects a reluctance to let go of power and control and brings those unconscious trust issues into play that can get in the way of development and autonomous working." Except in highly regulated activities, the belief that the delegator knows the only feasible approach to the task is almost surely unjustified.
- The self-esteem of the subordinate
- The microdelegator unintentionally communicates to the subordinate an unspoken message of distrust in the subordinate. In Morrison's terms, the "…temptation to impart experience or knowledge in order to ensure something comes out exactly as if you'd done it yourself can make the person on the receiving end feel undervalued, untrusted, while eroding autonomy, creating tension, etc etc etc etc…"
- In this way, a pattern of microdelegation can be a contributing factor in elevated turnover and substandard performance among delegatees.
Last words
As a technique of covert bullying, some abusers take actions that appear to be microdelegation. They might do this because the penalties for microdelegation are less severe than the penalties for bullying. But be clear: it isn't microdelegation — it's bullying.
In genuine microdelegation, by unintentionally sending a message of distrust of the delegatee, the microdelegator can cause the subordinate to lack confidence whenever the subordinate's process deviates in any way from the subordinate's perception of the microdelegator's process. That loss of confidence can morph into risk aversion and a feeling of being psychologically unsafe. And from there, it's a short step to organizational rigidity and obsolescence. Top
Next Issue
Are your projects always (or almost always) late and over budget? Are your project teams plagued by turnover, burnout, and high defect rates? Turn your culture around. Read 52 Tips for Leaders of Project-Oriented Organizations, filled with tips and techniques for organizational leaders. Order Now!
Footnotes
Your comments are welcome
Would you like to see your comments posted here? rbrenaXXxGCwVgbgLZDuRner@ChacDjdMAATPdDNJnrSwoCanyon.comSend 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.
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 Conflict Management:
Knife-Edge Performers
- Some employees deliver performance episodically, while some deliver steady, but barely adequate performance.
Either way, they keep their managers drained and anxious, on the "knife edge" of terminating
them. How can you detect knife-edge performers, and what can you do about them?
A Critique of Criticism: II
- To make things better, we criticize, but we often miss the mark. We inflict pain without meaning to,
and some of that pain comes back to us. How can we get better outcomes, while reducing the risks of
inflicting pain?
Impasses in Group Decision Making: IV
- Some impasses that develop in group decision making relate to the substance of the discussion. Some
are not substantive, but still present serious obstacles. What can we do about nonsubstantive impasses?
Preventing Toxic Conflict: I
- Conflict resolution skills are certainly useful. Even more advantageous are toxic conflict prevention
skills, and skills that keep constructive conflict from turning toxic.
When Retrospectives Turn into Blamefests: III
- Although retrospectives do foster organizational learning, they come with a risk of degeneration into
blame and retaliation. One source of this risk is how we responded to issues uncovered in prior retrospectives.
See also Conflict Management for more related articles.
Forthcoming issues of Point Lookout
Coming 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.
And on October 8: Responding to Workplace Bullying
- Effective responses to bullying sometimes include "pushback tactics" that can deter perpetrators from further bullying. Because perpetrators use some of these same tactics, some people have difficulty employing them. But the need is real. Pushing back works. Available here and by RSS on October 8.
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
Follow Rick
Recommend this issue to a friend
Send an email message to a friend
rbrenaXXxGCwVgbgLZDuRner@ChacDjdMAATPdDNJnrSwoCanyon.comSend a message to Rick
A Tip A Day feed
Point Lookout weekly feed
