Bottlenecks: I

Some people are bottlenecks. We wait for them to decide, or to approve activities or efforts that truly are beneath their station. They and they alone can report on certain activities. They and they alone can represent those activities in meetings. Their calendars are so full that we have trouble scheduling meetings. In frustration, we call these people names: "micromanagers" or "nanomanagers" or something worse.

But labeling them doesn't solve the problem or offer much of a path to understanding it. As their supervisors, if we want to solve the problem, or as subordinates, if we want to work around it or avoid it, we'll do much better if we understand it.

Let's begin with examples of reasons why some people cannot release these tasks to the care of their subordinates or staff or team members.

Pseudo-parental attachments

Some bottleneckers attained their positions by completing particular projects successfully. They maintain emotional attachments to those projects — attachments not as strong as what parents feel for children, but in other ways analogous. Their concern for the welfare of these "child-projects" makes them reluctant to release them to others. Release, if it comes at all, can be incomplete. Thus, the bottlenecker remains responsible for work that can be appropriately delegated to others.

Anxiety

Anxiety about the success of efforts that are properly the responsibility of subordinates need not derive from pseudo-parental attachments. It can arise, for example, if the bottlenecker has a mistakenly low opinion of the capabilities of the person responsible for the effort. Or the bottlenecker might fear that the effort could be at risk for other reasons, such as poor design or poor planning. Whatever the source of anxiety, instead of addressing it, the bottlenecker uses the concern to avoid entrusting the effort to the subordinate.

Political ambitions

Some activities Labeling people as micromanagers
doesn't solve the problem or
offer much of a path
to understanding itinherently confer political stature on those who represent them to other parts of the organization. An example is reporting on the status of the development of a new product that's expected to form a future raison d'être for the company. Other examples are negotiating for funding or justifying requests for funding increases. Bottleneckers often strive to be the public face of such efforts, even if they aren't actually involved in the performance of the work itself.

Addiction to feeling needed

Although most of us feel good when others express appreciation for our work, some people measure their own self-worth almost solely in terms of how others see them. For these people, maintaining ownership of activities that others value is more than desirable. It is essential to a definition of self-worth. In a real sense, they can become addicted to feeling needed, and incapable of delegating detailed responsibility for efforts that others regard as important.

We'll continue next time with an exploration of tactics for dealing with the bottlenecking pattern.   Next issue in this series   Top    Next Issue

More about micromanagement

There Are No Micromanagers  [January 7, 2004]

If you're a manager who micromanages, you're probably trying as best you can to help your organization meet its responsibilities. Still, you might feel that people are unhappy — that whatever you're doing isn't working. There is another way.

Are You Micromanaging Yourself?  [November 24, 2004]

Feeling distrusted and undervalued, we often attribute the problem to the behavior of others — to the micromanager who might be mistreating us. We tend not to examine our own contributions to the difficulty. Are you micromanaging yourself?

Managing Pressure: Communications and Expectations  [December 13, 2006]

Pressed repeatedly for "status" reports, you might guess that they don't want status — they want progress. Things can get so nutty that responding to the status requests gets in the way of doing the job. How does this happen and what can you do about it? Here's Part I of a little catalog of tactics and strategies for dealing with pressure.

Managing Pressure: The Unexpected  [December 20, 2006]

When projects falter, we expect demands for status and explanations. What's puzzling is how often this happens to projects that aren't in trouble. Here's Part II of a catalog of strategies for managing pressure.

Managing Pressure: Milestones and Deliveries  [December 27, 2006]

Pressed repeatedly for "status" reports, you might guess that they don't want status — they want progress. Things can get so nutty that responding to the status requests gets in the way of doing the job. How does this happen and what can you do about it? Here's Part III of a set of tactics and strategies for dealing with pressure.

How to Tell If You Work for a Nanomanager  [March 7, 2007]

By now, we've all heard of micromanagers, and some have experienced micromanagement firsthand. Some of us have even micromanaged others. But there's a breed of micromanagers whose behavior is so outlandish that they need a category of their own.

Reverse Micromanagement  [July 18, 2007]

Micromanagement is too familiar to too many of us. Less familiar is inappropriate interference in the reverse direction — in the work of our supervisors or even higher in the chain. Disciplinary action isn't always helpful, especially when some of the causes of reverse micromanagement are organizational.

Lateral Micromanagement  [September 10, 2008]

Lateral micromanagement is the unwelcome intrusion by one co-worker into the responsibilities of another. Far more than run-of-the-mill bossiness, it's often a concerted attempt to gain organizational power and rank, and it is toxic to teams.

Bottlenecks: I  [February 4, 2015]

Some people take on so much work that they become "bottlenecks." The people around them repeatedly find themselves stuck, awaiting responses or decisions. Why does this happen and what are the costs?

Bottlenecks: II  [February 11, 2015]

When some people take on so much work that they become "bottlenecks," they expose the organization to risks. Managing those risks is a first step to ending the bottlenecking pattern.

What Micromanaging Is and Isn't  [April 14, 2021]

Micromanaging is a dysfunctional pattern of management behavior, involving interference in the work others are supposedly doing. Confusion about what it is and what it isn't makes effective response difficult.

On Schedule Conflicts  [May 10, 2023]

Schedule conflicts happen from time to time, even when the organization is healthy and all is well. But when schedule conflicts are common, they might indicate that the organization is trying to do too much with too few people.

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!

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:

The True Costs of Cubicles

Although cubicles do provide facility cost savings compared with walled offices, they do so at the price of product development delays and increased product development costs. Decisions of facilities planners can have dramatic project schedule impact.

Personal Trade Secrets

Do you have some little secret tricks you use that make you and your team more effective? Do you wish you could know what secret tricks others have? Here's a way to share your secrets without risk.

Organizing a Barn Raising

Once you find a task that you can tackle as a "barn raising," your work is just beginning. Planning and organizing the work is in many ways the hard part.

The Perils of Piecemeal Analysis: Content

A team member proposes a solution to the latest show-stopping near-disaster. After extended discussion, the team decides whether or not to pursue the idea. It's a costly approach, because too often it leads us to reject unnecessarily some perfectly sound proposals, and to accept others we shouldn't have.

Paid-Time-Off Risks

Associated with the trend to a single pool of paid time off from separate categories for vacation, sick time, and personal days are what might be called paid-time-off risks. If your team must meet customer expectations or a schedule of deliverables, managing paid-time-off risks can be important.

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

Forthcoming issues of Point Lookout

Coming April 30: On Planning in Plan-Hostile Environments: II

When we finally execute plans, we encounter obstacles. So we find workarounds or adjust the plans. But there are times when nothing we try gets us back on track. When this happens for nearly every plan, we might be working in a plan-hostile environment. Available here and by RSS on April 30.

And on May 7: Subject Matter Bullying

Most workplace bullying tactics have analogs in the schoolyard — isolation, physical attacks, name-calling, and rumor-mongering are common examples. Subject matter bullying might be an exception, because it requires expertise in a sophisticated knowledge domain. And that's where trouble begins. Available here and by RSS on May 7.

Coaching services

I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrenfHlRlTgqCIXkUHBTner@ChacrEuHRQPYVKkOucGfoCanyon.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