Point Lookout: a free weekly publication of Chaco Canyon Consulting
Volume 4, Issue 4;   January 28, 2004: He's No Longer Here

He's No Longer Here

by

Sometimes we adopt inappropriate technologies, or we deploy unworkable processes, largely because of the political power of their advocates, and despite widespread doubts about the wisdom of the moves. Strangely, though, the decisions often stick long after the advocates move on. Why? And what can we do about it?

Tara knocked twice on Lance's doorjamb. "Got a minute?" she asked. Lance continued staring intently at his screen, typed a few more characters, clicked once, and looked up.

"Sure. What's up?"

"I was wondering when you'll have those slides ready," she said.

FeedbackLance rubbed his eyes. He was clearly tired. "Let's see, finish entering the data into APOLLO. That should take the rest of the afternoon, so maybe by 10. PM. Assuming that APOLLO behaves."

"Hmmm," Tara began. "What if we skip APOLLO?"

Tara and Lance might miss their deadline if they follow procedures and make the entries into APOLLO, a hard-to-use database deployed by a long since departed but powerful VP. They're considering bypassing it because nobody has ever figured out how to use its data. Still, they keep entering it.

The forces that keep
systems in place
can differ from the
forces that created
those systems
Similar things can happen with other kinds of software, and with procedures, too. They're useless, but they remain in place. What's going on?

Sometimes, when a system's advocate leaves, the advocate's constituency reconfigures. The power that put the system in place no longer exists, but the system lives on. This mechanism is called a "strange loop." Strange loops are common in complex systems such as human organizations, where they often make change very difficult. Here's why.

When we try to change, we sometimes ask, "How did we get here?" We're hoping that if we understand the path we took to the current configuration, then we can better devise adjustments. Sadly, although this sometimes works, the forces that keep a structure in place are often very different from those that installed it. They can be completely unrelated, and proceeding on the basis of the arrival story can be very misleading.

For instance, when a boneheaded process is installed, at first there can be so much resistance that the power of the advocate is the only explanation for the organization's accepting it. But once performance assessments become tied to competence with the system, the system is there to stay. That's just one of many reasons why boneheaded systems live on. Here are a few more:

  • We can't afford the system that would replace it.
  • We can't afford to dismantle it.
  • We're in such disarray because of the advocate's departure that we can't decide much of anything.
  • We can't acknowledge that we made such a crazy error.
  • Nobody wants to open that can of worms again — everyone is too burned out.

To eliminate vestigial systems, understand not what created them, but what supports them. If they really are so useless, ask: Why are we so locked in? What's keeping the system going? How can we break the strange loop? Go to top Top  Next issue: No Surprises  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!

Gödel, Escher, Bach: An Eternal Golden BraidStrange Loops are discussed at length in Douglas Hofstadter's Gödel, Escher, Bach: An Eternal Golden Braid. New York: Basic Books, 1999. Order from Amazon.com.

Your comments are welcome

Would you like to see your comments posted here? rbrenubcqSvusyBsQaEDwner@ChacfhuriyFKgDguTpuYoCanyon.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 Organizational Change:

Pick Up SticksPick-Up Sticks and the Change Game
When we change organizational culture, we often stumble over unexpected obstacles. Sometimes the tangle can be so frustrating that we want to start the company over again. Here are some tips for managing large-scale cultural change.
Ecotourists visit an iceberg off GreenlandWay Over Their Heads
For organizations in crisis, some but not all their people understand the situation. Toxic conflict can erupt between those who grasp the problem's severity and those who don't. Trying to resolve the conflict by educating one's opponents rarely works. There are alternatives.
Lifeboats on board the FS Scandinavia, May 2006Contrary Indicators of Psychological Safety: I
To take the risks that learning and practicing new ways require, we all need a sense that trial-and-error approaches are safe. Organizations seeking to improve processes would do well to begin by assessing their level of psychological safety.
Orchestra musicians performingContrary Indicators of Psychological Safety: III
When we first perform actions or play roles unfamiliar to us, we make mistakes. We learn new ways not only by reading or being told, but also by practicing. Unless we feel that making mistakes at first is acceptable, learning might never occur.
A white water rafting team completes its courseWhite Water Rafting as a Metaphor for Group Development
Tuckman's model of small group development, best known as "Forming-Storming-Norming-Performing," applies better to development of some groups than to others. We can use a metaphor to explore how the model applies to Storming in task-oriented work groups.

See also Organizational Change and Organizational Change for more related articles.

Forthcoming issues of Point Lookout

Pair of Wooden Shoes [right] (Sabots)Coming June 4: White-Collar Contractor Sabotage
Modern firms in competitive, dynamic markets draw on many types of employer/employee relationships, including contractors. By providing privileges and perks preferentially among these different types, they risk creating a caldron of resentments that can reduce organizational effectiveness. Available here and by RSS on June 4.
Horse Shoe Bend of the Colorado River in the Grand CanyonAnd on June 11: More Things I've Learned Along the Way: VI
When I gain an important insight, or when I learn a lesson, I make a note. Example: If you're interested in changing how a social construct operates, knowing how it came to be the way it is can be much less useful than knowing what keeps it the way it is. Available here and by RSS on June 11.

Coaching services

I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrenubcqSvusyBsQaEDwner@ChacfhuriyFKgDguTpuYoCanyon.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.
Reader Comments About My Newsletter
A sampling:
  • Your stuff is brilliant! Thank you!
  • You and Scott Adams both secretly work here, right?
  • I really enjoy my weekly newsletters. I appreciate the quick read.
  • A sort of Dr. Phil for Management!
  • …extremely accurate, inspiring and applicable to day-to-day … invaluable.
  • More
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 Managing ConflictFed up with tense, explosive meetings? Are you the target of a bully? Learn how to make peace with conflict.
Ebooks, booklets and tip books on project management, conflict, writing email, effective meetings and more.
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!