Monday, December 19, 2005
Is Enterprise Architecture really all about GroupThink?
You can avoid groupthink by placing responsibility and authority for a decision in the hands of a single person who turns to others for advice. Of course, it requires choosing the right person of high morale fiber. If the right person is selected, the decision and its consequences are their responsibility alone. This person will apply a reality check and will be motivated by their responsibility to take the right decision rather than follow a consensus.
Another way to reduce groupthink is to give an individual the role of disagreeing with any suggestion presented (Something I do a lot of at work). When one member of the team has an explicit Devil's Advocate role, there is less stigma in taking a negative stance. Intelligently argued opposition makes it more likely that other individuals will present their own ideas more carefully and be comfortable pointing out flaws in other's ideas.
A third way to counter groupthink is to use anonymous feedback via a suggestion box or an online chatroom. People can raise negative or dissenting views of proposals anonymously without harming the cohesiveness and social capital of the group. Collaborative workspaces are an excellent way of implementing this.
Once architecture teams acknowledge that groupthink exists, they can seek to avoid it so that quality decisions can be made. Some of the negative outcomes of groupthink include, but are not limited to:
- Not deciding against enough choices or possibilities
- Not examining early alternatives
- Not seeking expert opinion and making all decisions in an insular manner
- Rationalizing poor decisions
Been noodling the thought of evangelizing the notion of a "second-chance" meeting as part of our governance process at work that will offer one last opportunity to choose another course of action for all strategic initiatives. Would love to know your thoughts...
Links to this post: