Point Lookout: a free weekly publication of Chaco Canyon Consulting
Volume 15, Issue 6;   February 11, 2015: Bottlenecks: II

Bottlenecks: II

by

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.
A schematic representation of a MOSFET

A schematic representation of a MOSFET (Metal-Oxide Semiconductor Field Effect Transistor), similar to the transistors in the microprocessor(s) of the computer you're using to read this article. A typical modern laptop computer contains billions of these structures. They work by using the voltage applied to the Gate terminal to control the current flowing between the Source and the Drain. In effect, variations in that voltage cause different degrees of bottlenecking of the channel between the Source and the Drain. This enables a very small current to control variations in a much larger current.

So it is with organizational bottlenecks. One person, the bottleneck, can stall the work of many hundreds of people, under the right conditions.

We began exploring bottlenecking patterns last time, focusing on the motivations of those who become bottlenecks. Certainly there are more motivations than we've mentioned so far, but let's turn now to explore measures that can reduce the incidence of the pattern, or, at least, reduce the consequences of bottlenecking when it does occur.

Measure the incidence of bottlenecking
Define metrics and gather data that measures the incidence of bottlenecking. Example metrics for individuals include: the percentage of their day spent in meetings; actual hours worked; email messages sent per week; email message response time; voice mail message age; text messages sent per week; and meetings rescheduled per week. One particularly interesting metric: the number of meetings to which they had to send a "substitute" because of a schedule conflct.
Address bottlenecking in risk plans
For projects in which bottlenecking is a significant risk, risk plans ought to address it. If monitoring bottlenecking metrics is part of risk planning, then risk plans can prescribe interventions when bottlenecking is indicated. For projects in which bottlenecking isn't regarded as a significant risk, risk plans should include evidence to that effect, and steps to be taken if events unfold differently.
Remove temptations
When people are assigned sets of responsibilities that span efforts that they once championed, and whose success was the foundation for their current stature, the temptation to hang on to their former roles can be irresistible indeed. Doing so contributes to their overload and therefore to bottlenecking. When expanding responsibilities of top performers, arranging to place their former responsibilities out of reach removes any such temptation.
Monitor activities of political rivals
Political rivals For projects in which bottlenecking
is a significant risk,
risk plans ought to address it
of bottleneckers can be expected to be targeted for obscurity by the bottleneckers. That can happen because the responsibilities that are overloading the bottlenecker are often properly the responsibilities of the political rivals. Monitor the volume and the nature of the responsibilities political rivals have. If the workload of the rival is light, or the nature of the work is of lesser importance than the rival might be expected to have, the political agenda of the bottlenecker might be the cause.
Look to the supervisor
Supervisors whose charges become bottlenecks do have some responsibility for the situation. Certainly supervisors cannot be fully aware of conditions from minute to minute, but supervisors can be held responsible for the problematic behavior people who have been bottlenecks for a month or more, or who are repeat offenders. And supervisors who have more than one subordinate who is a bottleneck are also problematic. The supervisor's supervisor must address these failures as performance issues for the supervisor.

Finally, does your organization reward martyrs — the people who work killing hours for months on end because only they know how to do whatever it is they do? Rewarding martyrs creates more martyrs. In the long run, martyrdom hurts the organization. First in this series  Go to top Top  Next issue: Grace Under Fire: I  Next Issue

52 Tips for Leaders of Project-Oriented OrganizationsAre 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

Would you like to see your comments posted here? rbrendPtoGuFOkTSMQOzxner@ChacEgGqaylUnkmwIkkwoCanyon.comSend me your comments by email, or by Web form.

About Point Lookout

This article in its entirety was written by a 
          human being. No machine intelligence was involved in any way.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 Thinker PowerPointingThink Before You PowerPoint
Microsoft PowerPoint is a useful tool. Many of us use it daily to create presentations that guide meetings or focus discussions. Like all tools, it can be abused — it can be a substitute for constructive dialog, and even for thought. What can we do about PowerPoint abuse?
Dogs Fighting in a Wooded Clearing, by Frans SnydersMudfights
When we steer the discussion away from issues to attack the credibility, motives, or character of our debate partners, we often resort to a technique known as the ad hominem attack. It's unfair, it's unethical, and it leads to bad, expensive decisions that we'll probably regret.
Lewis and Clark on the Lower ColumbiaAstonishing Successes
When we have successes that surprise us, we do feel good, but beyond that, our reactions are sometimes self-defeating. What happens when we experience unanticipated success, and how can we handle it better?
A man using a chainsawDiscussion Distractions: II
Meetings are less productive than they might be, if we could learn to recognize and prevent the most common distractions. Here is Part II of a small catalog of distractions frequently seen in meetings.
Agricultural silosDisjoint Awareness: Assessment
When collaborators misunderstand each other's work and intentions, they're at risk of inadvertently interfering with each other. Three causes of misunderstandings are complexity, specialization, and rapid change.

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

Forthcoming issues of Point Lookout

A meeting that's probably a bit too largeComing March 20: Top Ten Ways to Make Meetings More Effective
Meetings are just about everybody's least favorite part of working in organizations. We can do much better if only we take a few simple steps to improve them. The big one: publish the agenda in advance. Here are nine other steps to improve meetings. Available here and by RSS on March 20.
An informal meeting in a loungeAnd on March 27: Allocating Action Items
From time to time in meetings we discover tasks that need doing. We call them "action items." And we use our list of open action items as a guide for tracking the work of the group. How we decide who gets what action item can sometimes affect our success. Available here and by RSS on March 27.

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:

Reprinting this article

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

Send email or subscribe to one of my newsletters Follow me at LinkedIn Follow me at X, or share a post Subscribe to RSS feeds Subscribe to RSS feeds
The message of Point Lookout is unique. Help get the message out. Please donate to help keep Point Lookout available for free to everyone.
Technical Debt for Policymakers BlogMy blog, Technical Debt for Policymakers, offers resources, insights, and conversations of interest to policymakers who are concerned with managing technical debt within their organizations. Get the millstone of technical debt off the neck of your organization!
Go For It: Sometimes It's Easier If You RunBad boss, long commute, troubling ethical questions, hateful colleague? Learn what we can do when we love the work but not the job.
303 Tips for Virtual and Global TeamsLearn how to make your virtual global team sing.
101 Tips for Managing ChangeAre you managing a change effort that faces rampant cynicism, passive non-cooperation, or maybe even outright revolt?
101 Tips for Effective MeetingsLearn how to make meetings more productive — and more rare.
Exchange your "personal trade secrets" — the tips, tricks and techniques that make you an ace — with other aces, anonymously. Visit the Library of Personal Trade Secrets.
If your teams don't yet consistently achieve state-of-the-art teamwork, check out this catalog. Help is just a few clicks/taps away!
Ebooks, booklets and tip books on project management, conflict, writing email, effective meetings and more.