5 Decision-Making in Teams

Frame the decision

Start by stating the question the team must answer and the outcome it needs to achieve. A Decision question such as “How can we reduce missed deadlines?” leaves room for multiple solutions; “Should we add another meeting?” already proposes one.

Set roles and boundaries

Before discussion, clarify who is accountable for the final choice, who contributes relevant expertise or information, and who will carry out the decision. These roles are not necessarily held by the same people. Make clear whether each person is advising, deciding, or implementing.

Identify constraints such as budget, policy, safety, or deadlines. Set a reasonable decision deadline and, if needed, a Fallback process. Clear roles and procedures help teams match their effort to the decision’s importance and risk and reduce confusion about responsibilities.

Select a decision-making method

Choose the method before discussion begins and explain it to the team. No single method fits every decision:

• Leader decides: The leader makes and communicates the decision. This can be useful when time is short, the impact is limited, or authority and accountability are clearly assigned.

• Leader consults: The leader gathers input and then makes the final choice. This can be useful when specialized knowledge or team perspectives can improve the decision while one person remains accountable.

• Majority vote: Members discuss options and vote; the option with the most support is selected. This can be useful when a timely choice is needed among clear alternatives and broad agreement is not essential.

• Consensus: Members work toward a choice everyone can support, even if it is not everyone’s first preference. This can be useful when the decision significantly affects the team or requires sustained cooperation to implement.

• Delegate: The leader assigns the decision to an individual or subgroup within agreed boundaries. This can be useful when the task is within that group’s expertise and the limits of its authority are clear.

Consensus can build commitment but takes time. Voting can be faster but may leave a minority feeling unheard. Teams can agree on a time limit and a fallback in advance—for example, seek consensus first, then have the accountable leader decide if the group cannot reach it.

Involve people and surface dissent

Invite people who can contribute relevant expertise, represent affected perspectives, approve resources, or carry out the decision. Involvement does not give everyone equal authority, so distinguish who advises, decides, and implements.

To reduce the chance that status or the first opinion dominates, ask members to write down their views before discussion, invite each person to speak, and share the leader’s preference only after hearing others. Ask someone to test the leading proposal by identifying its assumptions, risks, and contrary evidence. These practices can help surface concerns and reduce the risk of Groupthink.

Use disagreement constructively

Treat disagreement as information about different evidence, priorities, or assessments of risk rather than as a personal conflict. Summarize opposing views fairly and ask what evidence would change someone’s assessment. For important decisions, make sure people can raise concerns without being pressured to agree merely to end the discussion.

Compare options with clear criteria

Identify more than one plausible option, including doing nothing when appropriate. Compare the options against Decision criteria that follow from the team’s goal. Common criteria include expected benefit and effectiveness; cost, time, and staffing needs; risks and possible unintended effects; feasibility within constraints; and effects on the people who will use or implement the decision.

For example, a team deciding how to address missed deadlines might compare three options:

• Add a weekly check-in: Expected benefit is earlier warning about delays; the cost is moderate staff time; the main risk is additional meeting time; it is feasible by the deadline.

• Use a shared progress tracker: Expected benefit is easier identification of blockers; the cost is low setup effort; the main risk is that updates may be missed; it is feasible by the deadline.

• Keep the current process: There is no new cost or effort; the risk is that delays may continue; it is feasible by the deadline.

A comparison helps make trade-offs visible but does not replace judgment. Give greater weight to the criteria that matter most, check whether assumptions are supported by evidence, and distinguish facts from predictions. When uncertainty is substantial, identify what is unknown and consider whether a small trial or further information would reduce the risk.

Communicate the choice and next steps

After the chosen method produces a decision, communicate it promptly to everyone affected. Explain what was decided and, where useful, which alternatives were considered; why the choice was made, including important evidence, criteria, and trade-offs; who owns each next step and when it is due; and what remains uncertain and when progress will be reviewed or the choice reconsidered.

For example: “We will use a shared progress tracker for a four-week trial because it provides early visibility with little setup effort. Maya will create it by Friday; project leads will update it each Monday. We will review missed deadlines and team feedback at the end of the trial.” Clear communication turns a decision into coordinated action and makes it easier for the team to learn and adjust.