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.

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:

Figuring Out What to Do First

Whether we belong to a small project team or to an executive team, we have limited resources and seemingly unlimited problems to deal with. How do we decide which problems are important? How do we decide where to focus our attention first?

Some Limits of Root Cause Analysis

Root Cause Analysis uses powerful tools for finding the sources of process problems. The approach has been so successful that it has become a way of thinking about organizational patterns. Yet, resolving organizational problems this way sometimes works — and sometimes fails. Why?

The Retrospective Funding Problem

If your organization regularly conducts project retrospectives, you're among the very fortunate. Many organizations don't. But even among those that do, retrospectives are often underfunded, conducted by amateurs, or too short. Often, key people "couldn't make it." We can do better than this. What's stopping us?

The Risks of Too Many Projects: I

Some organizations try to run too many development projects at once. Whether developing new offerings, or working to improve the organization itself, taking on too many projects can defocus the organization and depress performance.

Anticipating Absence: Passings

In times more normal than ours, co-workers who pass on tend to do so one at a time. Disease or accidents rarely strike many co-workers in the same week, month, or year. There are exceptions — 9/11 was one such. This pandemic is another.

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

Forthcoming issues of Point Lookout

Coming June 7: Toxic Disrupters: Tactics

Some people tend to disrupt meetings. Their motives vary, but they use techniques drawn from a limited collection. Examples: they violate norms, demand attention, mess with the agenda, and sow distrust. Response begins with recognizing their tactics. Available here and by RSS on June 7.

And on June 14: Pseudo-Collaborations

Most workplace collaborations produce results of value. But some collaborations — pseudo-collaborations — are inherently incapable of producing value, due to performance management systems, or lack of authority, or lack of access to information. Available here and by RSS on June 14.

Coaching services

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