Sign In

Communications of the ACM

Viewpoints

Contagious Craziness, Spreading Sanity


View as: Print Mobile App ACM Digital Library Full Text (PDF) In the Digital Edition Share: Send by email Share on reddit Share on StumbleUpon Share on Hacker News Share on Tweeter Share on Facebook
suction sign

Credit: Mikhail Esteves

In the late 1970s the president of a company I worked with asked the company's economists and financial forecasters to provide their future market predictions for the next decade. This was a capital-intensive business with long lead times for equipment purchases, so a realistic appraisal of the likely future business environment was a pretty important thing. When the predictions arrived, they did not match what the president wanted to seenot at all.

It is not uncommon that people in positions of power are strong-willed, opinionated individuals who are used to getting their own way. The president was no exception and his response to the figures presented was quite dramatic. After some blustering, shouting, and numerous derogatory remarks directed at the professional expertise of the financial forecasting group, he scratched out some numbers on a piece of paper and handed them over to the chief economist. "These are the numbers I want to see," he said, "make these happen."

There is no doubt that the will and the drive to do things is a very important attribute. Certainly, having a strong conviction that something cannot be done is usually a self-fulfilling prophecy. If people are convinced that something is not achievable, then they usually won't achieve itif we argue for our limitations, we get to keep them. But sometimes things cannot be accomplished simply through force of will. Just because we really, really want something doesn't mean we will be able to get iteven if we are the president of a major corporation.

Back to Top

Infectious Conduct

Capricious behavior, particularly on the part of powerful or influential people, can be infectious. When one person in a system starts acting oddly, nearby people have two choices: to label the behavior as odd or to act like it is normal. If, for whatever reason, people act as if someone's weird actions are OK, they themselves start behaving weirdly. It is almost as if the odd behavior is catching. To compound the problem, we humans have built-in rationalizing capability that kicks in like a reflex when we act in an odd or unethical manner. This rationalization employs a thing called "cognitive dissonance" and allows us to continue to act in a weird way while simultaneously retaining the conviction that we are not acting in a weird way at all.a

Back to Top

The Project Managers: Can-Do

A friend of mine, a project manager at a large electronics company, described this behavior in the planning meetings he attends. The project managers reporting to the strong-willed and forceful vice president in charge of their division almost compete with each other to promise things to the boss and pretend they and their teams can do things they really don't think they can do at all. The boss is the instigator. He puts enormous pressure on his people and browbeats them if they come up with numbers he doesn't like. When one manager "caves" and agrees to something he (secretly and privately) doesn't think can be done, the others feel they have to do so as well. The compliant managers then get praised by the vice president, which reinforces the behavior.

Privately, the managers bemoan their fate and wring their collective managerial hands over what their boss has forced them to commit to. But, until recently, they didn't change their behavior.

Back to Top

The Construction Manager: First Law of Behavior

Years ago, I was coaching a (non-software) manager working in the construction industry. An affable and customer-centric person, his life was being made very difficult by his primary customer. The construction company built telephone switch centers and no matter what the manager promised and agreed to do for his customer, the customer always wanted more. In fact, it seemed like the more he gave the customer the more was wanted. The "customer is always right" approach did not seem to be working. After much discussion we decided that:

  • The customer was a very strong-willed and decisive person.
  • Asking for "more" is a perfectly appropriate thing for a customer to do, especially from the customer's perspective.
  • The customer was asking for more because more was being provided.
  • If the construction manager agreed to do more, it meant he must be able to do it.
  • As a strong-willed decisive person, the customer was expecting the manager to be equally strong-willed and decisive in deciding what could not be done.
  • The customer would continue piling on until the project manager said "no."

This could be called "Newton's First Law of Behavior": every behavior will continue until acted upon by another behavior. We could even extend this to Newton's Third Law and infer that the other behavior must be equal and opposite. This meant the project manager had to learn how to apply equal force in saying "no" to the extra work to balance the force the customer was applying in demanding the extra work.

Back to Top

Breaking the Cycle

To stop this behavior, people and organizations must somehow get out of the cycle. For the construction manager it was to learn to be firm and to realize the customer is not best served by trying to do everything. The customer is best served by most effectively doing the most important things.

For the software project managers dealing with the vice president, my friend bravely decided to break the cycle himself. After working a lot on his project's estimation practice, he vigorously defended his estimates to the vice president and simply refused to back down when pressured to reduce the projections. At one point, he even challenged the vice president to fire him if necessary. The vice president wisely chose not to do this and privately commented that it "took guts" to stand up and hold your ground like that.

Then an interesting thing started happening. Since there were dependencies operating between the division's projects, other project managers started intentionally "hooking" their project estimates and plans to my friend's project plan. Their reasoning was that since the boss doesn't mess with that project if my project has dependencies on it, he won't mess with my project either. As each project stabilized by being strongly coupled to more realistic project deadlines, everyone started calming down. Inexorably, sanity spread across the organization as people started committing only to things they really believed they could do.

Back to Top

Infectious Insanity

The opposite can be true too, as evidenced in the case of the financial forecasting scenario mentioned earlier. Confronted with the president's demand to "...make these numbers happen..." the Ph.D. economists returned to their financial forecasting groups and had to figure out how to ignore factors or promote factors to make it happen. One can imagine the chief economist's assistant saying "...but why would we ignore this factor, boss? We'd be crazy to do that! That's not how it works!" To which the chief economist might reply "Well, that's how it works if you want to keep your job...".

Then cognitive dissonance kicks in and people start rationalizing: "...well maybe the factor really isn't that important..." and, starting from the top, everyone starts separating from reality.

In the business of software, this cycle results in significant and perennial overcommitments. Lacking well-defined estimation practices, these commitments are simply the wishes of the strongest-willed people with the highest authorityunless the organizations and people that work for them can provide the appropriate counter-response.

It seems that sensible behavior or weird behavior will grow within organizations rather like a disease propagates. It is an upward or a downward spiral. But we can choose the direction.

Back to Top

Author

Phillip G. Armour (armour@corvusintl.com) is a senior consultant at Corvus International Inc., Deer Park, IL.

Back to Top

Footnotes

a. Tavris, C. and Aronson, E. Mistakes Were Made (But Not by Me). Harvest Books, 2003.

DOI: http://doi.acm.org/10.1145/1562764.1562774


Copyright held by author.

The Digital Library is published by the Association for Computing Machinery. Copyright © 2009 ACM, Inc.