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? rbrennFxegNSbbhZdaDVBner@ChacmOulLqHbRRrVlkXKoCanyon.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:

White water raftingWe Are All People
When a team works to solve a problem, it is the people of that team who do the work. Remembering that we're all people — and all different people — is an important key to success.
Six kids on a PlayPumpThe Questions Not Asked
Often, the path to forward progress is open and waiting, but we don't recognize it, or we convince ourselves it isn't there. Learning to see what we believe isn't there is difficult. Here are some reasons why.
A portrait of Matthew Lyon, printer, farmer, soldier, politicianHow to Foresee the Foreseeable: Recognize Haste
When trouble arises after we commit to a course of action, we sometimes feel that the trouble was foreseeable. One technique for foreseeing the foreseeable depends on recognizing haste in the decision-making process.
Dunes in Death Valley, CaliforniaHill Climbing and Its Limitations
Finding a better solution by making small adjustments to your current solution is usually a good idea. The key word is "usually."
Eugene F. Kranz, flight director, at his console on May 30, 1965, in the Control Room in the Mission Control Center at HoustonDesign Errors and Group Biases
Design errors can cause unwanted outcomes, but they can also lead to welcome surprises. The causes of many design errors are fundamental attributes of the way groups function. Here is Part II of our exploration.

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

Forthcoming issues of Point Lookout

A human marionetteComing 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.
Desperation at workAnd on December 6: Reframing Revision Resentment: I
From time to time, we're required to revise something previously produced — some copy, remarks, an announcement, code, the Mona Lisa, whatever… When we do, some of us experience frustration, and view the assignment as an onerous chore. Here are some alternative perspectives that might ease the burden. Available here and by RSS on December 6.

Coaching services

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

Ten Project Management Fallacies: The Power of Avoiding Hazards
Most Ten Project Management Fallaciesof 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 The Power Affect: How We Express Personal Powerpeople 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.

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.
Technical Debt for Policymakers BlogMy new 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.
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.