Point Lookout: a free weekly publication of Chaco Canyon Consulting
Volume 5, Issue 43;   October 26, 2005: Dealing with Deadlock

Dealing with Deadlock

by

At times it seems that nothing works. Whenever we try to get moving, we encounter obstacles. If we try to go around them, we find more obstacles. How do we get stuck? And how can we get unstuck?

In cities with rectangular layouts, traffic can lock up when drivers enter intersections on green, but cannot clear them within that green. We call this phenomenon gridlock. [Popik 2004]

Gridlock is an example of a deadlock. In a deadlock, we find a closed path at each node of which we can say, "Movement is blocked because movement at a neighboring node is blocked."

DeadlockGridlock seems paradoxical because each driver is trying to move as quickly as possible, and yet the system is stuck. Resolution usually requires that some drivers abandon their goals temporarily, to make way for others to clear the system. It's each driver's local perspective that prevents the system from resolving the deadlock. And the path to resolution is visible only from the global perspective.

Organizational deadlocks work the same way. Here's an example. Let's suppose that Purchasing can't keep up with its workload, because it has been denied extra staff in anticipation of new productivity software. To handle its load temporarily, management decides to limit assistance to requisitioners. This change delays the work of the IT project team that's responsible for the new software that Purchasing itself needs to deal with its workload. Sadly, something like this is probably happening somewhere right now.

Hierarchy tends to
make organizations
vulnerable to deadlock
Organizational deadlocks can be surprisingly persistent. Most organizations function on the basis of hierarchical delegation, in which operational decisions are made locally. And since local decisions cannot resolve global deadlocks, the deadlocks tend to persist.

Here are some ideas for managing the risk of organizational deadlock.

Resolve feuds
Feuds, passive resistance, and their cousins limit cooperation. Feuds at high levels are especially dangerous, because they interfere with access to the global perspective.
Relax emphasis on unit performance
Too much emphasis on unit performance can erode the ability of individual units to modify their own efforts for the benefit of the whole. Cooperation must be recognized as part of unit performance.
Complete all acquisitions
When one company acquires another, it acquires its culture, too. Leaving both cultures in place can be problematic when the two must cooperate. Eradicating the acquired culture doesn't work either, because of the hostility that results. When collaboration is the end goal, the acquisition is complete only when the two cultures become one.

Sometimes, even when everyone tries to support global goals, honest differences appear. To resolve them, people need ways to escalate the dispute, but when escalation incurs a penalty, escalation itself becomes part of the deadlock. Rewarding and encouraging appropriate escalation is a key to resolving honest deadlocks. Let's hope there's no deadlock about that. Go to top Top  Next issue: The Costs of Threats  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!

Footnotes

Comprehensive list of all citations from all editions of Point Lookout
[Popik 2004]
The term gridlock first appeared in print in 1980, but it was probably in use in the New York City planning department as early as 1971. See Barry Popik's blog post Back

Your comments are welcome

Would you like to see your comments posted here? Send 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:

My right foot. Arrow indicates the location of the break.My Right Foot
There's nothing like an injury or illness to teach you some life lessons. Here are some things I learned recently when I temporarily lost some of my independence.
Vortex cores about an F18 fighter jetGuidelines for Sharing "Resources"
Often, team members belong to several different teams. The leaders of teams whose members have divided responsibilities must sometimes contend with each other for the efforts and energies of the people they share. Here are some suggestions for sharing people effectively.
Mohandas GhandiNo Tangles
When we must say "no" to people who have superior organizational power, the message sometimes fails to get across. The trouble can be in the form of the message, the style of delivery, or elsewhere. How does this happen?
A tire reef off the coast of Fort Lauderdale, FloridaManaging 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.
A performance reviewPerformance Mismanagement Systems: I
Some well-intentioned performance management programs do more harm than good, possibly because of mistaken fundamental beliefs. Specifically: the fallacy of composition, the reification error, the myth of identifiable contributions, and the myth of omniscient supervision.

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

Forthcoming issues of Point Lookout

A dramatization of a mobbing incidentComing May 7: Subject Matter Bullying
Most workplace bullying tactics have analogs in the schoolyard — isolation, physical attacks, name-calling, and extortion are common examples. Subject matter bullying might be an exception, because it requires expertise in a sophisticated knowledge domain. And that's where trouble begins. Available here and by RSS on May 7.
Grissom, White, and Chaffee in front of the launch pad containing their AS-204 space vehicleAnd on May 14: Working with the Overconfident
A cognitive bias known as the Overconfidence Effect causes us to overestimate the reliability of our judgments. Decisions we make based on those judgments are therefore suspect. But there are steps we can take to make our confidence levels more realistic, and thus make our decisions more reliable. Available here and by RSS on May 14.

Coaching services

I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrenner@ChacoCanyon.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 Bluesky, 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.
101 Tips for Managing ConflictFed up with tense, explosive meetings? Are you the target of a bully? Learn how to make peace with conflict.
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.