Point Lookout: a free weekly publication of Chaco Canyon Consulting
Volume 16, Issue 1;   January 6, 2016: When Fixing It Doesn't Fix It: I

When Fixing It Doesn't Fix It: I

by

When complex systems misbehave, a common urge is to find any way at all to end the misbehavior. Succumbing to that urge can be a big mistake. Here's why we succumb.
Vintage slot machine at the Casino Legends Hall of Fame at the Tropicana Las Vegas Casino Hotel Resort, Nevada

Vintage slot machine at the Casino Legends Hall of Fame at the Tropicana Hotel and Casino in Las Vegas, Nevada. Slot machines reward behavior in an irregular manner (technically called a variable-ratio schedule). The reward induces the desired behavior (making a payment and pulling the lever). "Random twiddling and part replacement" also produces intermittent rewards (the system in question begins to work again), which induces further application of RTAPR in future incidents.

Photo courtesy U.S. Library of Congress Prints and Photographs Division.

From the outset, sound quality on the virtual conference was poor, even with that wonderful new system that shows everyone each site's whiteboard, and lets everyone see each other. After 10 minutes it got so bad that they suspended the conference and resumed on a plain old bridge line. The CEO was livid. But there was no alternative right then.

Overnight, people from IT and Facilities and the vendors went over the system, updated the firmware, replaced some boxes at two sites and got things working. When people signed in for the second session of the meeting the next morning, it worked a little better, but after 10 minutes, the system was again unusable. They had to sign off and resume on the bridge line. "Livid" was no longer a word strong enough to describe the CEO's state of mind.

The system didn't work, but more deeply disturbing is the problem-solving approach of IT, Facilities, and the vendors, which could be called "random twiddling and part replacement" (RTAPR). It's a standard method, and it usually ends in tragedy, because it wastes time and resources, rarely provides a lasting fix, and delays (if not precludes forever any possibility of) determining root causes.

Whether it's a complex system of electronics and software (as in our example), a process design for projects in a large enterprise, or regulations governing the banking system, RTAPR rarely works. So why do people approach complex problems this way? Here are four factors that drive us down this particular blind alley.

Periodic reinforcement
Every once in a while, RTAPR works. The chance that it might work again seduces us into trying it, against our better judgment. Psychologists call this phenomenon periodic reinforcement.
Extreme time pressure
Exerting Whether it's a complex system
of electronics and software, or
regulations governing the banking
system, "Random Twiddling and
Part Replacement" rarely works
pressure on repair teams limits their ability to perform problem diagnosis. The greater the pressure, the more powerful is the urge to use RTAPR.
Limited availability of relevant expertise
Staffing the repair team is a task that itself requires expertise, because the repair team needs expertise in all relevant fields [1]. Unless they have the expertise they need, their only real recourse is RTAPR.
Confidentiality or security
Complex systems can exhibit problems in patterns we call "intermittent," though the term intermittent might not be truly applicable. Often, the problem is predictable, but we lack the knowledge needed to predict it. That's why someone with appropriate expertise must be present at the onset of the difficulty. Sometimes the people with the needed expertise lack the stature (or maybe the security clearance) necessary to be "in the room" waiting for an incident. In some cases, unless qualified system experts can be present for the incidents, identifying the conditions that precipitate the difficulty can be impossible.

Now that we understand some reasons why repair teams resort to RTAPR, we're ready to look at an alternative method. Next time. Next in this series  Go to top Top  Next issue: When Fixing It Doesn't Fix It: II  Next Issue

[1]
See "Call in the Right Expert," Point Lookout for December 30, 2015

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!

Your comments are welcome

Would you like to see your comments posted here? rbrendIVhRaxZICCMGcwRner@ChacRwOLckMaclglSaTboCanyon.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.

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 Problem Solving and Creativity:

Helping each otherWhen We Need a Little Help
Sometimes we get in over our heads — too much work, work we don't understand, or even complex politics. We can ask for help, but we often forget that we can. Even when we remember, we sometimes hold back. Why is asking for help, or remembering that we can ask, so difficult? How can we make it easier?
The Johari WindowAssumptions and the Johari Window: II
The roots of both creative and destructive conflict can often be traced to the differing assumptions of the parties to the conflict. Here's Part II of an essay on surfacing these differences using a tool called the Johari window.
Ice on Challenger's launch pad hours before the launchDesign Errors and Groupthink
Design errors cause losses, lost opportunities, accidents, and injuries. Not all design errors are one-offs, because their causes can be fundamental. Here's a first installment of an exploration of some fundamental causes of design errors.
COL Michael Wyly, USMC (ret)Call in the Right Expert
When solving a problem is beyond us, we turn to experts, but sometimes we turn to the wrong experts. That can make the problem even worse. Why? How does this happen? What can we do about it?
A globe puzzleVirtual Brainstorming: I
When we need to brainstorm, meeting virtually carries a risk that our results might be problematic. Here's Part I of some steps to take to reduce the risk.

See also Problem Solving and Creativity and Critical Thinking at Work for more related articles.

Forthcoming issues of Point Lookout

Cargo containers at a port of entryComing May 31: Unresponsive Suppliers: III
When suppliers have a customer orientation, we can usually depend on them. But government suppliers are a special case. Available here and by RSS on May 31.
A blue peacock of IndiaAnd on June 7: The Knowledge One-Upmanship Game
The Knowledge One-Upmanship Game is a pattern of group behavior in the form of a contest to determine which player knows the most arcane fact. It can seem like innocent fun, but it can disrupt a team's ability to collaborate. Available here and by RSS on June 7.

Coaching services

I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrenxXNLhLCOGbyBzEymner@ChacfxHIofHEjRVyEsLjoCanyon.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:

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 words in your inbox in one hour. License any article from this Web site. More info

Public seminars

Creating High Performance Virtual Teams
Many Creating High Performance Virtual Teamspeople experience virtual teams as awkward, slow, and sometimes frustrating. Even when most team members hail from the same nation or culture, and even when they all speak the same language, geographic dispersion or the presence of employees from multiple enterprises is often enough to exclude all possibility of high performance. The problem is that we lead, manage, and support virtual teams in ways that are too much like the way we lead, manage, and support co-located teams. In this program, Rick Brenner shows you how to change your approach to leading, managing, and supporting virtual teams to achieve high performance using Simons' Four Spans model of high performance. Read more about this program. Here's an upcoming date for this program:

The Race to the South Pole: Ten Lessons for Project Managers
On 14The Race to the Pole: Ten Lessons for Project Managers 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 organizational leaders, business analysts, project sponsors, and project managers, the story is fascinating. Lessons abound. Read more about this program. Here's an upcoming date for this program:

Follow Rick

Send email or subscribe to one of my newsletters Follow me at LinkedIn Follow me at Twitter, or share a tweet Follow me at Google+ 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.
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.
303 Tips for Virtual and Global TeamsLearn how to make your virtual global team sing.
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.