Have you ever found yourself sitting in a project planning meeting where everyone around the table is discussing completion dates they know can't be met, yet no one ever says so? Or have you ever spent hours trying to work out some technical aspect of a design, even though you know another aspect of the design has a serious flaw that isn't being addressed? Unfortunately, these surreal experiences are familiar to most engineers, and they take place more often than many of us would like to admit.
How does this happen? How do engineers, who pride ourselves on our rationality and individualism, get caught up in a collective denial of reality? Most importantly, how do we live up to our professional responsibility to speak out?
Groupthink is a concept that was introduced by William H. Whyte in a 1952 Fortune magazine article and later developed by the psychologist Irving Janis in the 1970s and 1980s. It refers to the tendency to suspend independent critical thinking in favor of group consensus. The result is poor decision making.
The loss of the space shuttle Challenger and the lives of its crew, and the loss of the space shuttle Columbia and its crew 17 years later, are often given as examples of engineering groupthink. More recently, the stubborn insistence by the truck and engine manufacturer Navistar that its diesel emission reduction strategy would eventually work, despite evidence to the contrary, cost that company hundreds of millions of dollars and cost more than 700 people their jobs.
In all of these examples, it's probably fair to say the denial of reality was more on the part of managers than engineers. But why weren't engineers successful in winning their managers over to the side of reality?
The insidious thing about groupthink is that it builds on some of the best aspects of our character, including our ability to work together toward common goals and our unwillingness to give up in the face of a challenge. Despite the stereotype of engineers as solitary misanthropes, teamwork is central to the engineering profession. Engineers often have deep loyalty to their teammates. This is a good thing, but loyalty should never mean self-censorship of criticism. Engineers also often have a tendency to believe they can solve any problem with hard work and ingenuity. This can sometimes lead to ever-increasing expenditures of effort toward a difficult task without questioning the value of the task itself.
The first rule in Dale Carnegie's well-known book How to Win Friends and Influence People is "Don't criticize, condemn, or complain." It's certainly true that negativity rarely leads to popularity, but it can sometimes play an important role in making good decisions.
During my senior design project in engineering school, one of my classmates distinguished herself by criticizing nearly every group decision and constantly complaining about the hopeless state of our project. Needless to say, the rest of the group found this behavior annoying. As the semester progressed, however, I realized that it was important to take her criticisms seriously. If they were wrong, explaining why they were wrong increased our own understanding. If they were right, they helped keep us from going in the wrong direction.
Of course, I'm not suggesting it's good to be a chronic complainer, but such people shouldn't always be written off. Engineers should not let the fear of being perceived as negative, stepping out of line, standing alone, or even being wrong override their professional judgment. As Richard Feynman pointed out in his appendix to the Challenger report, "For a successful technology, reality must take precedence over public relations, for nature cannot be fooled."
Keep that in mind the next time a project leader asks you for a positive piece of information to help him sell a project to his managers.
Great post, Dave. Groupthink is a danger that happens across all professions and to everyone at some point in time in their personal life. The on-going challenge is to strike that balance between useful criticism and problem identification and trying to find issues just because it's expected. Groupthink is also often a result of an ingrained organizational culture which unfortunately, transcends any one engineer's ability to break down and fix.
Beth, it is important to have useful criticism. At General Electric we were schooled constantly about this. If you were going to criticize something you had better have an alternative. Quite frankly, the alternative may be argued with, but in the process we typically came up with a synthesis that moved things forward. Don't be afraid to criticize, but don't just complain, either.
If engineers and designers can set aside attachment and ego, groupthink is less likely.
It's hard to be the one who calls out any issue that needs to be addressed in a project. Unfortunately, pointing out flaws in the process is often seen as criticism. Timing is very important too. Too early or too late in the process can derail good momentum.
@naperlou: At times, it may be necessary to criticize a plan even when you don't have an alternative worked out. If there are problems with the plan, they need to be brought up, so that they can be addressed. You're absolutely right, though, that it needs to be in a constructive spirit, rather than a spirit of finding fault. (For one thing, if others perceive that you're simply trying to find fault, they will be less likely to listen to your concerns).
Thanks, Dave, for writing this article. I haven't seen Whyte's name in ages. He wrote The Organization Man, a key social science text discussing in detail what groupthink was doing to 1950s companies and their employees. I think one of the toughest aspects to groupthink, for engineers and everyone else, is figuring out the line between it and teamwork.
Lou that's sound practice, and I agree. You were GE – so you know Zafirowski – and what an example he set. (MikeZ, if you're reading this, the connation is NOT positive). Back to the point; we had an un-written rule when I was at Motorola – If you're going to criticize a concept, you must offer an improvement alternative; not just another Jerk-input. (MikeZ, you would have benefited following this idea. Maybe even kept you out of bankruptcy a few times)
Complain all you want, missing unreasonable deadlines on projects will lead to your exit from the company. This is happening to a colleague of mine. He is stressing himself out over meeting the dates. He has even said it is impossible. The response, "we have to get it done." (We as in him only.) He confided in me that he is worried, his job is a stake.
Is groupthink more like groupblame? Swaying a manager to reality is just a way to buy more time, pass the blame onto time so to speak. Perhaps complaining is a good way to cover the bases. Squeaky wheel getting the grease, to add another cliche.
What can someone like my friend do when they complain about unreachable milestones and still are responsible?
@JamesCAnder: Managers who set unachievable deadlines and then blame engineers for failing to achieve them are setting themselves up for failure.
Suppose the company fires your friend and hire someone else. His replacement is unlikely to have any more success in meeting the deadlines. Ultimately, the company will fail to achieve its goals. They can blame whoever they want, but at the end of the day, they will be the losers.
I'm not suggesting that your friend should complain; I'm suggesting that he should tell the truth. This is his professional responsibility. Whether or not his managers want to listen to him is outside of his control.
The law of gravity applies, whether you choose to acknowledge it or not. Denying reality does not change the facts. But we, as individuals, can choose whether to participate in the denial of reality.
Your friend should be looking for another job, if he isn't already. Based on your description of its management style, the company he works for is clearly not headed for success.
Sounds very familiar a manager setting unrealistic deadlines just so the project schedule would fit into some kind of mold. I always hated when a manager would ask my completion date then put whatever date he felt would fit well in the project's schedule. I've seen this happen not only to me but other engineers more times than I can count. Then for some strange reason the manager would be surprised when the project was behind schedule. In fact, I worked a place this was so bad that "behind schedule and over budget" was a common phase. I thought "on schedule and within budget" was a unicorn project.
Beth, I know what you mean about the ingrained thinking.
I'm generally the one who don't have a problem going against the group's opinion if I think it is wrong. However, there are times when like Beth stated it is ingrained and my feedback is not worth mentioning, but not often. Lol.
One time a program manager asked me "how is the project going"? I politely stated it wasn't going well, the new people he put on the project had taken it way off track and no progress was being made. Long story short, He let me know that I was the only person on the project that felt that way. I told him I was the only person who said anything.
I learned over the years to NEVER repeat someone else's opinion about something like this, as they always deny saying it making you look like the liar. So when he asked who I said he/she must speak for themselves. Not 30 days later, the group was called into his office saying the "project isn't going well no progress was being made". I said "OH NO!! I can't believe it". It's funny the project engineer came to me in private and said "I should have said something about how bad the project was going when he asked me instead of saying everything was going good". I was thinking yes you should have but rest assures I will not speak for you or anyone else. It a shame there are so many people that are afraid to speak the truth. The truth may hurt but I rather it hurt and make things better than say nothing and make them worst.
In a world that's going green, industrial operations have a problem: Their processes involve materials that are potentially toxic, flammable, corrosive, or reactive. If improperly managed, this can precipitate dangerous health and environmental consequences.
An analysis of what’s needed to implement Design for Disassembly and Design for Recycling results in eight strategies engineers can use to design an intentional end-of-life stage into their products.
Government regulations, coupled with growing consumer sensitivity about data and identity theft, require that data storage organizations demonstrate proper protection and due diligence in protecting sensitive information stored inside datacenter enclosures.
When a crane doesn't have a monitoring system, crane owners schedule service every six months and simply scrap the parts they replace, even if a part has had little use and doesn't need replacing. This can cost thousands.
From Dell / Intel® New Paradigms in Design Work Scott Hamilton, vertical market strategist for Dell Precision workstations, 5/2/2013 3
Early in my career, I worked as a draftsman and remember the days of drawing on vellum with numbered pencils and Mylar with plastic lead. This was a fun experience in the sense that I ...
I've been using workstations for more than 10 years and love finding ways to get more performance from my system. With demanding professional applications that require more power each ...
A lasting memory from my first job as an engineer in an auto assembly plant is standing on hard concrete at six in the morning, vending-machine coffee clutched in hand, listening to ...
A quick look into the merger of two powerhouse 3D printing OEMs and the new leader in rapid prototyping solutions, Stratasys. The industrial revolution is now led by 3D printing and engineers are given the opportunity to fully maximize their design capabilities, reduce their time-to-market and functionally test prototypes cheaper, faster and easier. Bruce Bradshaw, Director of Marketing in North America, will explore the large product offering and variety of materials that will help CAD designers articulate their product design with actual, physical prototypes. This broadcast will dive deep into technical information including application specific stories from real world customers and their experiences with 3D printing. 3D Printing is
To save this item to your list of favorite Design News content so you can find it later in your Profile page, click the "Save It" button next to the item.
If you found this interesting or useful, please use the links to the services below to share it with other readers. You will need a free account with each service to share an item via that service.
Tweet This
0 
