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.[*]
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."
Gridlock 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
vulnerable to deadlockOrganizational 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. 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 welcomeWould you like to see your comments posted here? rbrenijnfKTSVVgTtvCHhner@ChacWfMnLbdLeeVMbKYtoCanyon.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:
- How We Avoid Making Decisions
- When an important item remains on our To-Do list for a long time, it's possible that we've found ways
to avoid facing it. Some of the ways we do this are so clever that we may be unaware of them. Here's
a collection of techniques we use to avoid engaging difficult problems.
- 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.
- Ten Reasons Why You Don't Always Get What You Measure: III
- The phrase "You get what you measure," has acquired the status of "truism." Yet
many measurement-based initiatives have produced disappointing results. Here's Part III of an examination
of the idea — a look at management's role in these surprises.
- Dealing with Negative Progress
- Many project emergencies are actually the result of setbacks — negative progress. Sometimes these
mishaps are unavoidable, but often they're the result of patterns of organizational culture. How can
we reduce the incidence of setbacks?
- Seven Ways to Get Nowhere
- Ever have the feeling that you're getting nowhere? You have the sense of movement, but you're making
no real progress towards the goal. How does this happen? What can you do about it?
Forthcoming issues of Point Lookout
- Coming November 22: Motivation and the Reification Error
- We commit the reification error when we assume, incorrectly, that we can treat abstract constructs as if they were real objects. It's a common error when we try to motivate people. Available here and by RSS on November 22.
- And on November 29: Manipulators Beware
- When manipulators try to manipulate others, they're attempting to unscrupulously influence their targets to decide or act in some way the manipulators prefer. But some targets manage to outwit their manipulators. Available here and by RSS on November 29.
I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrenOtdQCLPVqANWTKTrner@ChacXRytFuCBkZEkaUgtoCanyon.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.