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 workspressure 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 . 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.
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!
Your comments are welcomeWould you like to see your comments posted here? rbrenrCKohKfcMumRmtkZner@ChacaVaHjTceuRBDtUIwoCanyon.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.
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.
More articles on Problem Solving and Creativity:
- Problem Defining and Problem Solving
- Sometimes problem-solving sessions are difficult because we get started solving a problem before we
know what problem we're solving. Understanding the connection between stakeholders, problem solving,
and problem defining can reduce conflict and produce better solutions.
- Project Improvisation as Group Process
- When project plans contact reality, things tend to get, um, a bit confused. We can sometimes see the
trouble coming in time to replan thoughtfully — if we're nearly clairvoyant. Usually, we have
to improvise. How a group improvises tells us much about the group.
- New Ideas: Generation
- When groups work together to solve problems, they employ three processes repeatedly: they generate ideas,
they judge those ideas, and they experiment with those ideas. We first examine idea generation.
- Reactance and Decision-Making
- Some decisions are easy. Some are difficult. Some decisions that we think will be easy turn out to be
very, very difficult. What makes decisions difficult?
- Rationalizing Creativity at Work: I
- Much of the work of modern organizations requires creative thinking. But financial and schedule pressures
can cause us to adopt processes that unexpectedly and paradoxically suppress creativity, thereby increasing
costs and stretching schedules. What are the properties of effective approaches?
Forthcoming issues of Point Lookout
- Coming March 21: Narcissistic Behavior at Work: III
- People who behave narcissistically tend to regard themselves as special. They systematically place their own interests and welfare ahead of anyone or anything else. In this part of the series we consider how this claimed specialness affects the organization and its people. Available here and by RSS on March 21.
- And on March 28: Narcissistic Behavior at Work: IV
- Narcissistic behavior at work is more damaging than rudeness or egotism. It leads to faulty decisions that compromise organizational missions. In this part of the series we examine the effects of constant demands for attention and admiration. Available here and by RSS on March 28.
I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrenhdDgjSnANZhWqeRPner@ChacIQuwigOlpQQruhlGoCanyon.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:
- Get 2001-2 in Geese Don't Land on Twigs (PDF, USD 11.95)
- Get 2003-4 in Why Dogs Wag (PDF, USD 11.95)
- Get 2005-6 in Loopy Things We Do (PDF, USD 11.95)
- Get 2007-8 in Things We Believe That Maybe Aren't So True (PDF, USD 11.95)
- Get 2009-10 in The Questions Not Asked (PDF, USD 11.95)
- Get all of the first twelve years (2001-2012) in The Collected Issues of Point Lookout (PDF, USD 28.99)
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 Power Affect: How We Express Our Personal Power
- Many people 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.