Methods Of Decision Making for Teams

While a decision within organizations often relies on facts and data, teams must agree upon a method of decision making based on that data. Ensuring that the decisions are made with a process and purpose that the team can utilize to make the best possible decision with the given facts and data.

There are many decision-making styles, and two methods must be chosen to serve as guideposts for decisions made. The primary method must be agreed to by the team, and a backup method must also be selected. The methods can and will vary from the people and stakeholders making the decision as well as the knowledge of the facts and data that the team possesses when making the decision.

Below is a decision-making spectrum as well as the advantages and disadvantages of each method.

deciding on how the team decides create-learning team building and leadership

Authoritarian Decision Making

Authoritarian decision making is a decision that is placed in the hands of one person who chooses quickly and without regard for input from others. Typically this method is utilized when either there is a crisis and calls for an immediate decision or when the decision is mundane.

Advantages
  • Quick decision made when the leader may possess more information than those being affected by the decision.
  • When the team leader has the trust and “best interest” of those, who are affected by the decision.
  • The speed of the decision being made, the decision can be made quickly
  • The decision is not watered down with compromises
Disadvantages
  • Decision lacks the involvement of those who are affected
  • Those affected have a decreased chance for “buy in” to decision made
  • Likelihood of incorrect decision based on poor judgment and wrong facts
Consultative Decision Making

Consultative decision making is the type where decision-making power is in the hands of one person, and the person actively solicits the ideas, suggestions, and opinions of others.

Advantages
  • People who are affected by the decision are sought out for their input, allowing for greater buy-in to the ultimate decision made.
  • By seeking input from varied sources a better and more knowledgeable decision can be made
Disadvantages
  • It takes longer
  • Buy-in of the final decision with the consultative method only occurs if your input is finally decided on by the decision maker.
  • If the decision maker already has a predetermined choice in mind and is only “going through the motions” showing a false consultative style, this method backfires rapidly.
Consensus Decision Making

Many misconceptions haunt consensus; it is not a tool in total agreement among the team, nor is it a type of voting. The consensus decision-making method dictates that all parties involved have input on the decision to be made, and whatever agreement is reached (i.e., compromise) will not be sabotaged by the team.

Advantages
  • Full participation by the entire team; involves total involvement of the team
  • Full participation increases buy-in to the decision made
  • With input from the whole team, the ultimate decision is not made until there is agreement, therefore, showing buy-in from all team members.
Disadvantages
  • Necessitating buy-in from the entire team takes longer
  • Final decision made is often “watered down.”
Majority Voting

Consensus will often prove not to be a viable option. Therefore a backup is usually needed majority vote is a suitable backup. Majority voting is rarely ever used as the primary decision-making method.

Advantages
  • The decision can be made with a less watered down solution
  • The speed of the decision can be increased, following a lengthy consensus process
Disadvantages
  • Voting creates winners and losers
  • Those who lose may be more inclined to sabotage the decision, creating the possibility that whatever decision reached will not be adequately implemented.
100% Agreement

It is a rarity when a diverse team is asked to decide that 100% agreement is ever truly reached. Thus it is strongly recommended that this method should never be used, not even as a back-up.

Click for a case study about using a shared and known process for making team-based decisions.