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.
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? TopNext Issue
Strange Loops are discussed at length in Douglas Hofstadter's Gödel, Escher, Bach: An Eternal Golden Braid. New York: Basic Books, 1999. .
In the past two years, your life has probably changed. Do you commute over the same route you did two years ago? Same transportation? Same job? Same company? Same industry? Change is all around, and you're probably pretty skilled at it. You can become even more skilled if you change how you change.
When leaders try to motivate organizational change, they often resort to clever sloganeering. One of the most commonly used slogans is a definition of insanity. Unfortunately, that definition doesn't pass the sanity test.
Sometimes changing organizations goes smoothly. More often, it doesn't. Whatever methodology we use — and there are many methodologies available — difficulties can arise. When change is hard, what's happening? What makes change hard?
When organizational change is difficult, we sometimes blame poor leadership or "resistance." But even when we believe we have good leadership and the most cooperative populations, we can still encounter trouble. Why is change so hard so often?
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
The Race to the South Pole: Ten Lessons for Project Managers
On 14 December 1911, four men led by Roald Amundsen reached the South Pole. Thirty-five days later, Robert F. Scott and four others followed. Amundsen had won the race to the pole. Amundsen's party returned to base on 26 January 1912. Scott's party perished. As historical drama, why this happened is interesting enough, but to project managers, the story is fascinating. Lessons abound. Read more about this program. Here's an upcoming date for this program:
The Race to the South Pole: The Power of Agile Development
On 14 December 1911, four men led by Roald Amundsen reached the South Pole. Thirty-five days later, Robert F. Scott and four others followed. Amundsen had won the race to the pole. Amundsen's party returned to base on 26 January 1912. Scott's party perished. As historical drama, why this happened is interesting enough. Lessons abound. Among the more important lessons are those that demonstrate the power of the agile approach to project management and product development. Read more about this program. Here's an upcoming date for this program:
The Politics of Meetings for People Who Hate Politics
There's a lot more to running an effective meeting than having the right room, the right equipment, and the right people. With meetings, the whole really is more than the sum of its parts. How the parts interact with each other and with external elements is as important as the parts themselves. And those interactions are the essence of politics for meetings. This program explores techniques for leading meetings that are based on understanding political interactions, and using that knowledge effectively to meet organizational goals. Read more about this program. Here's an upcoming date for this program:
TBD, Mansfield, MA: August 21, Regional Event, PMI MassBay, PMI Central Mass, Ocean State PMI, PMI Keene, PMI Southern New England.
Looking for insights, tips, and concrete suggestions for the conundrums and kerfuffles of workplace life? The Collected Issues of Point Lookout is a collection of articles from my weekly newsletter, all in a single ebook of 1263 pages, searchable and cross referenced. Newly released, order by 30 Jun 2013, New York Time, at the introductory price of only , a savings of USD 9.00! Check it out!
A Tip a Day arrives by email, or by Yahoo! Widget, each business day. It's 20 to 30 words at most, and gives you a new perspective on the hassles and rewards of work life. Most tips also contain links to related articles. Free!