Monday, May 19, 2014

When Good Ideas Go Bad

In my experience, groupthink is a behavior that can sink an improvement project if not caught and stopped early. Groupthink is where there is group pressure to ‘go along’ with the decisions of the group or the beliefs of the group. This can start with ill-defined problem statements, scope, and/or goals, and the team will stay on the wrong path if assumptions are not tested or questioned. Keeping charter information simple and validating the problem statement can go a long way control groupthink. Validation is accomplished through using process timelines or data that is reflective of the problem statement.

Another method to reduce groupthink is to use a balanced functionally diverse team. Members bring their own perspective of the problems and causes to the team and if functional diversity is not present, then the natural group will have the numbers to force their perspective on the other team members. Using balanced teams with one or two members from each function can prevent groupthink.


ummm, no.



My favorite cause of groupthink is when one "expert on everything" arrives and begins to tell everyone how to think. Many will go along to get along because they are afraid of making someone mad or they do not want to be seen as a non-team player or because they are introverts that are uncomfortable speaking up. As a project lead my first method is to take them off to the side and tell them to knock it off. If it continues I have called them out in front of the team, which usually sends them into the stratosphere. If I still do not see the behavior I am looking for I will send them back to their work group and let the boss know that I'm not interested in baby-sitting their problem child. I have not had to do this very often because we use ground-rules for team member behavior that are discussed during the kick-off of the project while everyone's Supervisor, the Project Champion and General Manager are in the room.

This type of behavior can show up at any time during the project whether it is executed through weekly team meetings or kaizen style locked in a room for a week. When the behavior arrives a the end of the week when everyone is tired and ready to go home, the aforementioned expert will begin to implement her solution. Another method to overcome is to provide everyone with a number of votes or rating system to use across different possible solutions. I have had good results with this style and will continue to use it in the future.


Ultimately setting the expectations for team behavior must be established early (and often). If you are on a team and you begin to recognize groupthink, it may be time to become the voice of dissension.

No comments:

Post a Comment