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.
Lance 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 systemsSimilar 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? 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!
Strange 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? rbrenDJpmhgyaDTwBQXkhner@ChacmGoYuzfZpOvDQdRkoCanyon.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 Organizational Change:
Conventional Foolishness
- Every specialization has a set of beliefs, often called "conventional wisdom." When these
beliefs are so obvious that they're unquestioned and even unnoticed, there's an opportunity to leap
ahead of the pack — by questioning the conventional wisdom.
The True Costs of Cost-Cutting
- The metaphor "trimming the fat" rests on the belief that some parts of the organization are
expendable, and we can remove them with little impact on the remainder. Ah, if only things actually
worked that way...
Deciding to Change: Trusting
- When organizations change by choice, people who are included in the decision process understand the
issues. Whether they agree with the decision or not, they participate in the decision in some way. But
not everyone is included in the process. What about those who are excluded?
The Expectation-Disruption Connection
- In technology-dependent organizations, we usually invest in infrastructure as a means of providing new
capability. But mitigating the risk of disruption is a more powerful justification for infrastructure
investment, if we understand the Expectation-Disruption Connection.
Improvement Bias
- When we set about improving how our organizations do things, we expose ourselves to the risk of finding
opportunities for improvement that offer very little improvement, while we overlook others that could
make a real difference. Cognitive biases play a role.
See also Organizational Change and Organizational Change for more related articles.
Forthcoming issues of Point Lookout
Coming 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.
And on May 21: Mismanaging Project Managers
- Most organizations hold project managers accountable for project performance. But they don't grant those project managers control of needed resources. Nor do they hold project sponsors or other senior managers accountable for the consequences of their actions when they interfere with project work. Here's a catalog of behaviors worth looking at. Available here and by RSS on May 21.
Coaching services
I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrenDJpmhgyaDTwBQXkhner@ChacmGoYuzfZpOvDQdRkoCanyon.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
rbrenDJpmhgyaDTwBQXkhner@ChacmGoYuzfZpOvDQdRkoCanyon.comSend a message to Rick
A Tip A Day feed
Point Lookout weekly feed

- 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