Decisions, Decisions: I

As I write this, it's Election Day 2004 in the US. I don't yet know what the result will be, but it occurred to me that we're engaged in one kind of group decision-making process. And that got me wondering about how many different variations there are for smaller groups. Here's Part I of a little catalog of commonly used group decision-making procedures. For Part II, see "Decisions, Decisions: II," Point Lookout for December 1, 2004.

Unanimity

Everyone has to agree whole-heartedly.

Unanimity means "the state of being of one mind" and that's about the size of group this works best for: one. For larger groups, if there's even a little controversy, this process is very difficult.

Consensus

Everyone votes either "I agree completely, I will support it;" or "I can live with it, and I will support it;" or "No, I can't live with it and I will not support it." Sometimes this is done by a show of thumbs, respectively, Up, Sideways, or Down. If there's a single down thumb, the proposal is defeated; otherwise it's accepted.

Consensus ensures that any accepted proposal has everyone's support. Some disadvantages: a small number can block any decision; there's a risk of groupthink; and achieving consensus can be slow. It's probably unworkable in a highly polarized environment.

Consensus Minus N

Like Consensus, except that the proposal is accepted with any number of No votes up to N.

This is an attempt to deal with the problem of blocking by a tiny minority, and it can speed the decision. It's more workable than Consensus in a polarized environment if one faction is very small. The big risk: a dissenting minority can feel alienated or "check out."

Multi-voting

When the proposal before the group involves either rank ordering a set of options, or selecting one option from many, simple voting or consensus don't work very well, because they're oriented toward either accepting or rejecting a single proposition. In Multi-Voting, each participant has a set number of votes, which he or she can distribute among the options in any way at all.

One weakness: there's no way to vote No. You might be able to address this by giving people a set of No votes to distribute freely among the options.

Authority

The Authority (or Chair or Executive or manager or leader) decides, possibly after open discussion.

This method is best for time-critical decisions, or for decisions for which open discussion is inappropriate, impossible, unethical or illegal.

There is a risk of overlooking some issues, and alternative proposals; a risk of ethical conflicts; a risk of bias; and a risk of alienating some stakeholders, who might feel excluded from the process. And if the Authority controls compensation decisions, either directly or indirectly, participants in the discussion might not surface all issues.

Now the only problem is deciding how to decide — and this is just Part I. See "Decisions, Decisions: II," Point Lookout for December 1, 2004, for more.  Next in this series  Top    Next Issue

Do you spendyour days scurrying from meeting to meeting? Do you ever wonder if all these meetings are really necessary? (They aren't) Or whether there isn't some better way to get this work done? (There is) Read 101 Tips for Effective Meetings to learn how to make meetings much more productive and less stressful — and a lot more rare. Order Now!

For a great resource on consensus, see "A Short Guide to Consensus Building, from the Public Disputes Program of Harvard Law School, the MIT Department of Urban Studies and Planning, the Tufts University Fletcher School of Law and Diplomacy, and the not-for-profit Consensus Building Institute.

Reader Comments

Brad Appleton

Great article! This is an issue that I deal with a lot in my work. I wonder if you have seen any of the work of Ellen Gottesdiener. She has a book called "Requirements by Collaboration: Workshops for Defining Needs" and a good article/excerpt called "Decide how to Decide".

Your comments are welcome

Would you like to see your comments posted here? rbrenCYqJuFTzcRATFgpfner@ChacVheXTpiLdmUTbLWhoCanyon.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.

Related articles

More articles on Personal, Team, and Organizational Effectiveness:

Double Your Downsizing Damage

Some people believe that senior management is actually trying to hurt their company by downsizing. If they are they're doing a pretty bad job of it. Here's a handy checklist for evaluating the performance of your company's downsizers.

Email Antics: II

Nearly everyone complains that email is a time waster. Yet much of the problem results from our own actions. Here's Part II of a little catalog of things we do that help waste our time.

An Emergency Toolkit

You've just had some bad news at work, and you're angry or really upset. Maybe you feel like the target of a vicious insult or the victim of a serious injustice. You have work to do, and you want to respond, but you must first regain your composure. What can you do to calm down and start feeling better?

Embolalia and Stuff Like That: I

When we address others, we sometimes use filler — so-called automatic speech or embolalia — without thinking. Examples are "uh," "um," and "er," but there are more complex forms, too. Embolalia are usually harmless, if mildly annoying to some. But sometimes they can be damaging.

Avoid Having to Reframe Failure

Yet again, we missed our goal — we were late, we were over budget, or we lost to the competition. But how can we get something good out of it?

See also Personal, Team, and Organizational Effectiveness and Effective Meetings for more related articles.

Forthcoming issues of Point Lookout

Coming September 26: Congruent Decision-Making: I

Decision-makers who rely on incomplete or biased information are more likely to make faulty decisions. Congruent decision-making can limit the incidence of bad decisions. Available here and by RSS on September 26.

And on October 3: Congruent Decision-Making: II

Decision-makers who rely on incomplete or biased information are more likely to make decisions that don't fit the reality of their organizations. Here's Part II of a framework for making decisions that fit. Available here and by RSS on October 3.

Coaching services

I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrenpoadyRzgiKieCyDqner@ChactYltUEWHAcnDUoRPoCanyon.com or (650) 787-6475, or toll-free in the continental US at (866) 378-5470.

Get the ebook!

Past issues of Point Lookout are available in six ebooks:

• Get 2001-2 in Geese Don't Land on Twigs (PDF, USD 11.95)
• Get 2003-4 in Why Dogs Wag (PDF, USD 11.95)
• Get 2005-6 in Loopy Things We Do (PDF, USD 11.95)
• Get 2007-8 in Things We Believe That Maybe Aren't So True (PDF, USD 11.95)
• Get 2009-10 in The Questions Not Asked (PDF, USD 11.95)
• Get all of the first twelve years (2001-2012) in The Collected Issues of Point Lookout (PDF, USD 28.99)

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

Public seminars

10 Non-Technical Phenomena That Lead to Technical Debt

When organizations set about gaining control of their accumulated and newly incurring technical debt, a common error of thinking is that the problem can be addressed by modifying their technical processes alone. That can be effective in cases in which the causes of technical debt are found only in the engineering and IT organizations. But those cases are rare. This program surveys ten examples of organizational phenomena that lead to technical debt and which are not restricted to the engineering or IT organizations. Indeed, many of these phenomena cannot be found in the engineering or IT organizations, or if found there, they have relatively small effects on technical debt. For each of the ten phenomena, we describe how it leads to technical debt formation or persistence, and what can be done to mitigate its effects. Most important, we explain how effective control of technical debt requires contributions from a broad array of organizational roles. Read more about this program. Here's a date for this program:

• Wherever you are: it's a teleseminar: September 20, Teleseminar, Computer Aid, Inc. (CAI). Register now.
   

The Power Affect: How We Express Our Personal Power

Many people who possess real organizational power have a characteristic demeanor. It's the way they project their presence. I call this the power affect. Some people — call them power pretenders — adopt the power affect well before they attain significant organizational power. Unfortunately for their colleagues, and for their organizations, power pretenders can attain organizational power out of proportion to their merit or abilities. Understanding the power affect is therefore important for anyone who aims to attain power, or anyone who works with power pretenders. Read more about this program.

• A recording of a program presented 6:00 PM June 29 (Eastern Time), Monthly Webinar, Technobility Webinar Series. You can earn 1.0 Category 'A' PDU by viewing this program. View this program now.