
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 itof 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 issue 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
Would you like to see your comments posted here? rbrenjTnUayrCbSnnEcYfner@ChacdcYpBKAaMJgMalFXoCanyon.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.
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 Conflict Management:
Managing Pressure: The Unexpected
- 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
- 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.
A Critique of Criticism: I
- Whether we call it "criticism" or "feedback," the receiver can sometimes experience
pain, even when the giver didn't intend harm. How does this happen? What can givers of feedback do to
increase the chance that the receiver hears the giver's message without experiencing pain?
Managing Hindsight Bias Risk
- Performance appraisal practices and project retrospectives both rely on evaluating performance after
outcomes are known. Unfortunately, a well-known bias — hindsight bias — can limit the effectiveness
of many organizational processes, including both performance appraisal and project retrospectives.
Suppressing Dissent: II
- Disagreeing with the majority in a meeting, or in some cases, merely disagreeing with the Leader, can
lead to isolation and other personal difficulties. Here is Part II of a set of tactics used by Leaders
who choose not to tolerate differences of opinion, emphasizing the meeting context.
See also Conflict Management and Conflict Management for more related articles.
Forthcoming issues of Point Lookout
Coming February 26: Devious Political Tactics: Bad Decisions
- When workplace politics influences the exchanges that lead to important organizational decisions, we sometimes make decisions for reasons other than the best interests of the organization. Recognizing these tactics can limit the risk of bad decisions. Available here and by RSS on February 26.
And on March 5: On Begging the Question
- Some of our most expensive wrong decisions have come about because we've tricked ourselves as we debated our options. The tricks sometimes arise from rhetorical fallacies that tangle our thinking. One of the trickiest is called Begging the Question. Available here and by RSS on March 5.
Coaching services
I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrenjTnUayrCbSnnEcYfner@ChacdcYpBKAaMJgMalFXoCanyon.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
Follow Rick





Recommend this issue to a friend
Send an email message to a friend
rbrenjTnUayrCbSnnEcYfner@ChacdcYpBKAaMJgMalFXoCanyon.comSend a message to Rick
A Tip A Day feed
Point Lookout weekly feed
