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 in this series  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!

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:

Shooting Ourselves in the Feet

When you give a demo to a small audience, there's a danger of overwhelming them in a behavior I call "swarming." Here are some tips for terrific demos to small audiences.

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.

Coping and Hard Lessons

Ever have the feeling of "Uh-oh, I've made this mistake before"? Some of these oft-repeated mistakes happen not because of obstinacy, or stupidity, or foolishness, but because the learning required to avoid them is just plain difficult. Here are some examples of hard lessons.

Business Fads and Their Value

Fads in business come and go, like fads anywhere. In business, though, their effects can be so expensive that they threaten the enterprise. Still, the ideas and methods that become fads can have intrinsic value. Where does that value come from? Where does it go?

Problem-Solving Preferences

When people solve problems together, differences in preferred approaches can surface. Some prefer to emphasize the goal or objective, while others focus on the obstacles. This difference is at once an asset and annoyance.

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

Forthcoming issues of Point Lookout

Coming April 17: How to Answer When You Don't Know How to Answer

People engaged in knowledge work must often respond to questions that test the limits of their knowledge, or the limits of everyone's knowledge. Responding effectively to such questions advances us all. Available here and by RSS on April 17.

And on April 24: Antipatterns for Time-Constrained Communication: 1

Knowing how to recognize just a few patterns that can lead to miscommunication can be helpful in reducing the incidence of problems. Here is Part 1 of a collection of communication antipatterns that arise in technical communication under time pressure. Available here and by RSS on April 24.

Coaching services

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