Impasses in Group Decision-Making:
by Rick Brenner
When groups can't reach agreement on all aspects of an issue, the tactics of some members can actually exacerbate disagreement. Here's Part II of an exploration of impasses, emphasizing two of the more toxic tactics.
The Bill of Rights — the first ten amendments to the U.S. Constitution. The Bill actually was a Bill, introduced in the First Congress, and sent on after much wrangling, to the states for ratification. How it came about is a wonderful illustration of the approach to impasse that is founded on acceptance and serious consideration of the views of dissenters. Ratification of the Constitution was a controversial decision, with two views contending for dominance. The dominant group were the Federalists, who favored a strong central government and who felt that no enumeration of rights was advisable. The dissenting minority were the Anti-Federalists, who were wary of strong central government and who wanted specific protection of individual rights. Ratification of the Constitution met serious opposition in some states, including in Massachusetts. But it succeeded there based on an approach that came to be known as the Massachusetts Compromise, which enabled Anti-Federalists to vote to ratify the Constitution in exchange for a commitment by Federalists to consider the amendments that would become the Bill of Rights. This compromise was replicated in other states where ratification was problematic, and on September 13, 1788, the Constitution was finally declared ratified, albeit at that time by only 11 of the thirteen states that eventually ratified it.
The first Congress met in New York City on March 4, 1789, dominated by the Federalists, 20 to 2 in the Senate, and 48 to 11 in the House. It was this First Congress that adopted and sent to the states for ratification the Bill of Rights, which dealt specifically with the Anti-Federalists' objections. Read more about the history of the Bill of Rights. Photo courtesy US Library of Congress.
We began an exploration of impasses last time by focusing on the perspective of opinion minorities. In our scenario, we postulated that the group did have consensus on some issues, which we called the C-Issues. But there was disagreement on other issues — the D-Issues. In this Part II, we explore two tactics that tend to strengthen the impasse, preventing agreement.
- Hostage tactics
- Some group members believe that by taking hostages, they can compel the rest of the group to adopt a position more to their liking. The hostage of choice is often one or more of the C-Issues. In the view of the hostage takers, refusing to agree to the C-Issues exerts pressure on the rest of the group to comply with the hostage-takers' wishes. This tactic can become corrosive if members of the rest of the group press the hostage-takers to justify their opposition to the hostage C-Issues. The hostage-takers then devise arguments to justify their opposition to the C-Issues, which, often, they themselves don't believe. What little agreement there was with respect to C-Issues might then vanish. Even worse, others in the group might become intransigent, if they feel that acceding to the hostage-takers' demands will only invite further demands and further hostages, either by the hostage-takers or by others who witness the success of the hostage-takers.
- Acceding to hostage-takers' demands might seem appealing, but it does usually lead to more widespread hostage taking. Because questioning the hostage-takers about C-Issues risks converting C-Issues to D-Issues, approaches to forging agreement must always focus on D-Issues. Make the concerns of the objectors visible, and deal with them substantively.
- Abuse of the concept of precedent
- Some group members might fear that after they agree to the C-Issues, they won't be able to influence subsequent decisions sufficiently with respect to the D-Issues. They see partial agreement as the first step on a slippery slope, fearing that others will use their partial agreement as inappropriate leverage for later decisions. In effect, they fear they might be confronted with, "I don't see what your problem is with D-Issue #3, because you agreed to C-Issue #2." That tactic can indeed be an abuse of the concept of precedent, if it relies solely on the fact of agreeing to C-Issue #2, rather than on the substance of C-Issue #2, the substance of D-Issue #3, and their connection.
- If abuse of precedent Acceding to hostage-takers' demands
might seem appealing, but it does
usually lead to more
widespread hostage-takinghas occurred in the past, then certainly the concern is real, and the group must deal with it. To address the concern, the group can agree that such content-free appeals to precedents are unacceptable.
Hostage-taking by dissenters, or precedent abuse by those pressuring dissenters, are indirect attempts to gain adherents. To avoid strengthening impasses, deal directly with objections to agreement. First in this series Next in this series Top Next Issue
Are you fed up with tense, explosive meetings? Are you or a colleague the target of a bully? Destructive conflict can ruin organizations. But if we believe that all conflict is destructive, and that we can somehow eliminate conflict, or that conflict is an enemy of productivity, then we're in conflict with Conflict itself. Read 101 Tips for Managing Conflict to learn how to make peace with conflict and make it an organizational asset. Order Now!
Your comments are welcome
Would you like to see your comments posted here? rbrenmiEabJHIIutvcIwXner@ChacdJHqsMahoVzwjUJooCanyon.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
Point Lookout is a free weekly email newsletter. Browse the archive
of past issues. Subscribe for free.
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 Conflict Management:
- Hurtful Clichés: Part II
- Much of our day-to-day conversation consists of harmless clichés: "How goes it?" or "Nice to meet you." Some other clichés aren't harmless, but they're so common that we use them without thinking. Here's Part II of a series exploring some of these clichés.
- Is It Blame or Is It Accountability?
- When we seek those accountable for a particular failure, we risk blaming them instead, because many of us confuse accountability with blame. What's the difference between them? How can we keep blame at bay?
- Letting Go of the Status Quo: the Debate
- Before we can change, we must want to change, or at least accept that we must change. And somewhere in there, we must let go of some part of what is now in place — the status quo. In organizations, the decision to let go involves debate.
- Meeting Bullies: Advice for Chairs
- Bullying in meetings is difficult to address, because intervention in the moment is inherently public. When bullying happens in meetings, what can you do?
- The Myth of Difficult People
- Many books and Web sites offer advice for dealing with difficult people. There are indeed some difficult people, but are they as numerous as these books and Web sites would have us believe? I think not.
See also Conflict Management and Workplace Politics for more related articles.
Forthcoming Issues of Point Lookout
- Coming July 8: Ethical Debate at Work: Part I
- When we decide issues at work on any basis other than the merits, we elevate the chances of making bad decisions. Here are some guidelines for ethical debate. Available here and by RSS on July 8.
- And on July 15: Ethical Debate at Work: Part II
- Outcomes of debates at work sometimes favor one party, not only at the expense of the other or others, but also at the expense of the organization. Here's Part II of a set of guidelines for steering debates toward wise outcomes. Available here and by RSS on July 15.
I offer email and telephone coaching at both corporate and individual rates.
Contact Rick for details at rbrenZkNErWpNWgjyUcJDner@ChacNwYMCdBrrevoFZqEoCanyon.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:
Reprinting this article
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
- Ten Project Management Fallacies: The Power of Avoiding Hazards
- Most of what we know about managing projects is useful and effective, but some of what we know "just ain't so." Identifying the fallacies of project management reduces risk and enhances your ability to complete projects successfully. Even more important, avoiding these traps can demonstrate the value and power of the project management profession in general, and your personal capabilities in particular. In this program we describe ten of these beliefs. There are almost certainly many more, but these ten are a good start. We'll explore the situations where these fallacies are most likely to expose projects to risk, and suggest techniques for avoiding them. Read more about this program. Here's an upcoming date for this program:
- Managing in Fluid Environments
- Most people now work in environments that can best be characterized as fluid, because they're subject to continual change. We never know what's coming next. In such environments, managing — teams, projects, groups, departments, or the enterprise — often entails moving from surprise to surprise while somehow staying almost on track. It's a nerve-wracking existence. This program provides numerous tools that help managers who work in fluid environments. Read more about this program. Here are some upcoming dates for this program:
- The Race to the South Pole: The Organizational Politics of Risk Management
- On 14 December 1911, four men led by Roald Amundsen reached the South Pole. Thirty-five days later, Robert F. Scott and four others followed. Amundsen had won the race to the pole. Amundsen's party returned to base on 26 January 1912. Scott's party perished. As historical drama, why this happened is interesting enough. But to organizational leaders, business analysts, project sponsors, and project managers, the story is fascinating. We'll use the history of this event to explore lessons in risk management, its application to organizational efforts, and how workplace politics enters the mix. A fascinating and refreshing look at risk management from the vantage point of history and workplace politics. Read more about this program. Here's an upcoming date for this program: