Leadership & CommunicationMeetings, writing and decisions · Lesson 9 of 21

Making better decisions as a group

Article · 13 min · 8 min lecture

Video lecture

Making better decisions as a group

13 chapters · about 8 min · full transcript

Coming soon

Chapter 1 of 13

Group decisions

  • Why they go wrong
  • Who decides, and how
  • Frame and discuss
  • Decide and commit
  • The pre-mortem

The narrated lecture is in production

Every chapter is scripted and ready. Browse the chapters and read the full transcript now — the video will appear here when it’s published.

Chapters

Why group decisions go wrong

Groups can make better decisions than individuals because they combine knowledge and perspectives. But they often fall into predictable traps:

  • Groupthink: desire for harmony suppresses dissent.
  • Anchoring: the first number or idea mentioned dominates.
  • Authority bias: everyone defers to the most senior person.
  • Confirmation bias: people seek information that supports their existing view.
  • Unclear decision rights: nobody knows who decides, so decisions drift.

Step 1: clarify how the decision will be made

Before discussion, state who decides and how:

MethodWhen to useWatch out for
Leader decides aloneUrgent, low-impact or confidentialLow buy-in
Leader decides after consultationMost important decisionsConsultation must be genuine
Majority voteMany equal stakeholders, moderate stakesLosing minority disengages
Consensus (all can live with it)High need for commitmentSlow; can water down decisions
Delegate to the group or an individualExpertise sits with themMust respect their decision

Frameworks such as RACI or RAPID (Recommend, Agree, Perform, Input, Decide) help make decision rights explicit.

Step 2: frame the decision well

  • What exactly are we deciding? (One sentence.)
  • What criteria matter? (Cost, time, risk, customer impact, strategic fit.)
  • What options exist? Always generate at least three, including "do nothing".
  • What information do we need, and what is good enough given the stakes and time?

Step 3: improve the discussion

Techniques that reduce bias:

  • Independent input first: ask people to write their view or estimate before discussion (reduces anchoring and authority bias).
  • Senior people speak last.
  • Devil's advocate or red team: someone argues the strongest case against the preferred option.
  • Pre-mortem: "Imagine it is a year from now and this decision failed. Why?"
  • Separate facts from opinions: label clearly.

Step 4: decide and commit

State the decision clearly, including the reasoning and the key trade-offs accepted. Ask for commitment: people may disagree but should support implementation ("disagree and commit"). Record it in a decision log.

Decision log entry
Date: 12 March
Decision: Enter Saudi market first; UAE in phase 2
Decided by: CEO after consultation with leadership team
Options considered: KSA first; UAE first; both simultaneously
Key reasons: partner readiness, market size, regulatory timeline
Trade-offs accepted: slower UAE revenue; higher initial travel costs
Dissent noted: CFO preferred UAE first due to lower setup cost
Review point: after 6 months, compare against KPIs

Reversible and irreversible decisions

Distinguish decisions that are easy to reverse (try something, learn, change course) from those that are hard to reverse (major investments, public commitments). Move quickly on reversible decisions; invest more time and analysis in irreversible ones.

Worked example

Illustrative. A fictional e-commerce startup in Lahore had to choose a payment provider. In the first meeting, the founder stated a preference, and everyone agreed. A board adviser suggested restarting: each team member independently scored three providers against agreed criteria (fees, reliability, settlement time, support, integration effort). The independent scores revealed that the founder's preferred provider scored poorly on settlement time, which mattered greatly for cash flow. The team chose a different provider, and the founder later described the process as the most useful change to how they made decisions.

Hands-on: a decision record and a pre-mortem you can run in 20 minutes

1. One-page decision record (keep them in a shared folder or wiki so decisions are findable):

DECISION RECORD — [title] — [date]
Decision needed:   (framed as a question with options, not yes/no only)
Decider:           (one named person or body)     Rule: consult / consent / vote / consensus
Input from:        (names/roles)                   Informed: (who hears afterwards)
Type:              one-way door (hard to reverse) | two-way door (easy to reverse)
Options considered: A / B / C with main pros, cons and risks
Evidence:          (data, sources; flag assumptions)
Decision:          
Why:               
Dissent recorded:  (who disagreed and why; "disagree and commit" agreed?)
Review date / signal that would make us revisit:

2. Pre-mortem (20 minutes, from Gary Klein's technique):

1. "Imagine it's 12 months from now and this decision has failed badly." (1 min)
2. Everyone writes reasons it failed, silently and independently. (5 min)
3. Round-robin: one reason each until all are shared. (7 min)
4. Pick the top 3 risks; agree a mitigation or an early-warning signal for each. (7 min)

3. AI as a devil's advocate (anonymise sensitive data):

We are about to decide [decision] for [context]. Our preferred option is [A] because [reasons].
Argue the strongest case against A and for the best alternative. List assumptions we
are making that could be wrong and what evidence would test each. Do not decide for us.

Use the output to widen the discussion. It is not evidence, and it cannot know your organisation's context.

Common mistakes

  • Starting discussion before clarifying who decides.
  • Only one option considered.
  • Leader states preference first.
  • Endless consensus seeking on low-stakes decisions.
  • Decisions not recorded, so they are reopened.

Quick self-check

Think of your team's last significant decision. Could everyone say who made it, what options were considered and why the chosen option won? If not, use the decision log template next time.

Decision-making under time pressure

When time is short, decide who decides, set a deadline for input, and accept "good enough" information for reversible choices. Communicate the decision and the reasoning quickly, and schedule a review point. Delaying a decision is itself a decision, often with hidden costs.

Learning from decisions

Judge decisions by the quality of the process as well as the outcome. A good process can still produce a bad result through bad luck, and a poor process can get lucky. Reviewing decision logs periodically helps teams learn which processes lead to better results over time.

Key takeaways

  • Group decisions suffer from groupthink, anchoring, authority bias and unclear decision rights.
  • Clarify who decides and how before discussion; frame the decision with criteria and options.
  • Collect independent input first, have senior people speak last, and use pre-mortems or devil's advocates.
  • Decide clearly, record reasoning and dissent, and move faster on reversible decisions.

Check your understanding

Quick questions to lock in the lesson. They don’t count towards your certificate.

  1. Why ask team members to write their estimates before discussion?
  2. Which decision deserves the most analysis?
  3. What does 'disagree and commit' mean?

Put it into practice

For your next team decision, use independent written input, have the most senior person speak last, and record the result in a decision log.

Enrol for free to save your progress

Reading is always free. Enrol to keep your place, take the final assessment and earn a verifiable certificate.