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 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.
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 welcomeWould you like to see your comments posted here? rbrenFMxewvCatGqYCWRTner@ChaczqbfyCbemvhrnjeRoCanyon.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.
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.
More articles on Personal, Team, and Organizational Effectiveness:
- Getting Around Hawthorne
- The Hawthorne Effect appears when we measure employee attitudes or behavior — when people know
they're being measured, they modify their behavior. How can we measure attitudes with a minimum of distortion
from the Hawthorne Effect?
- We Are All People
- When a team works to solve a problem, it is the people of that team who do the work. Remembering that
we're all people — and all different people — is an important key to success.
- 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?
- Clueless on the Concept
- When a team member seems not to understand something basic and important, setting him or her straight
risks embarrassment and humiliation. It's even worse when the person attempting the "straightening"
is wrong, too. How can we deal with people we believe are clueless on the concept?
- Workplace Anti-Patterns
- We find patterns of counter-effective behavior — anti-patterns — in every part of life,
including the workplace. Why? What are their features?
Forthcoming issues of Point Lookout
- Coming October 25: Workplace Memes
- Some patterns of workplace society reduce organizational effectiveness in ways that often escape our notice. Here are five examples. Available here and by RSS on October 25.
- And on November 1: Risk Creep: I
- Risk creep is a term that describes the insidious and unrecognized increase in risk that occurs despite our every effort to mitigate risk or avoid it altogether. What are the dominant sources of risk creep? Available here and by RSS on November 1.
I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrenlHhrJYOCNgBwTmCmner@ChaceMnScFMcwRhYLyBqoCanyon.com or (617) 491-6289, 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, USD 11.95)
- Get 2003-4 in Why Dogs Wag (PDF, USD 11.95)
- Get 2005-6 in Loopy Things We Do (PDF, USD 11.95)
- Get 2007-8 in Things We Believe That Maybe Aren't So True (PDF, USD 11.95)
- Get 2009-10 in The Questions Not Asked (PDF, USD 11.95)
- Get all of the first twelve years (2001-2012) in The Collected Issues of Point Lookout (PDF, USD 28.99)
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 words in your inbox in one hour. License any article from this Web site. More info
- Ten Project Management Fallacies: The Power of Avoiding Hazards
- Most of what we know about managing projects is useful and effective, but some of what we know "just ain't so." Identifying the fallacies of project management reduces risk and enhances your ability to complete projects successfully. Even more important, avoiding these traps can demonstrate the value and power of the project management profession in general, and your personal capabilities in particular. In this program we describe ten of these beliefs. There are almost certainly many more, but these ten are a good start. We'll explore the situations where these fallacies are most likely to expose projects to risk, and suggest techniques for avoiding them. Read more about this program. Here's a date for this program:
- The Power Affect: How We Express Our Personal Power
- Many people who possess real organizational power have a characteristic demeanor. It's the way they project their presence. I call this the power affect. Some people — call them power pretenders — adopt the power affect well before they attain significant organizational power. Unfortunately for their colleagues, and for their organizations, power pretenders can attain organizational power out of proportion to their merit or abilities. Understanding the power affect is therefore important for anyone who aims to attain power, or anyone who works with power pretenders. Read more about this program.