When good teams make poor decisions: using disagreement, dissent and clear ownership

A team can be experienced, committed and genuinely close, and still make a poor decision. Trust helps people share information and work together under pressure. But the same wish to stay united can quietly suppress doubts. People hold back concerns, assume silence means agreement, or go along with a weak option because questioning the group feels more costly than supporting it.

The opposite problem is also common. Disagreement is treated as a personality clash to be smoothed over, when it is actually telling the business something important: that two parts of the operation want different things, that an assumption is weak, or that nobody is sure who decides. Fixing the relationship while ignoring the cause guarantees the same argument next month.

This article explains how to read conflict as information, why cohesive teams are especially prone to certain decision failures, how to build dissent into important decisions without making every meeting a fight, and why every decision needs a named owner and a plan for action.

Harmony is not the same as health

A team that never disagrees may be well aligned. It may also be fearful, disengaged or dominated by one voice. A junior employee may stay silent not because they agree, but because challenging the owner or a senior colleague feels risky. In work where mistakes are costly, such as safety, quality or large financial commitments, an unspoken concern can be far more dangerous than visible disagreement.

So treat silence carefully, particularly from people with less authority. And treat conflict as a signal worth understanding before trying to make it go away.

Conflict is information

Disagreements have many sources, and personality is only one of them. Before trying to resolve a conflict, ask what it is about:

Treating every conflict as interpersonal can repair a relationship while leaving the real cause untouched. Repeated arguments between the same two functions usually point to a structural problem, such as conflicting targets or a poorly designed handoff. The owning the handoffs between departments article looks at that kind of problem.

Five ways to respond

There are five broad ways to handle a disagreement, and each has its place:

• Collaborate when combining perspectives could produce a better answer than either side’s.
• Decide firmly when delay is costly and someone has legitimate authority to choose.
• Compromise when the issue can genuinely be split, such as sharing a resource.
• Avoid when the issue is minor or the timing is wrong.
• Accommodate when preserving the relationship matters more, or the other person clearly knows better.

The common mistake is compromising by reflex. Splitting the difference between two technically incompatible options can produce something worse than either. Sometimes the right answer is to choose one deliberately.

Not every disagreement deserves equal effort. Some differences can simply be accepted. Concentrate on conflicts that affect a significant decision, an important relationship or a recurring handoff.

Why cohesive teams decide badly

Groups have real advantages: they pool knowledge, see more options and are more committed to carrying out what they decide. But group decisions also have well-known failure modes:

• Holding back: people withhold doubts to avoid friction.
• Groupthink: the desire for unity overrides critical evaluation.
• False consensus: everyone assumes everyone else agrees.
• Hasty decisions: the first plausible option is adopted before alternatives are explored.
• Polarisation: discussion pushes the group to a more extreme position than any individual held.
• Diffused effort: when everyone shares responsibility, individuals do less.

Strong teams are particularly vulnerable to the first four, because their identity is built around competence and trust. The better a team believes it is, the harder it can be to notice that its decision process is failing.

Three stages of a good decision

It helps to separate three stages:

1. Divergence: surfacing different information, interpretations and options.
2. Convergence: evaluating options, making trade-offs and deciding at the right time.
3. Commitment to action: turning the decision into named responsibilities, timing and follow-through.

Weak teams fail at all three. Strong teams often fail more subtly: they become very good at converging and quietly stop diverging. They decide efficiently but examine too little.

Design dissent in before you need it

Constructive challenge should not depend on someone’s courage on the day. For important decisions, build it into the process:

• Ask the less senior people first, before the owner or manager states a view. Once a senior person has spoken, the discussion tends to converge around them.
• Separate idea generation from evaluation, so the first idea does not crowd out the rest.
• Require alternatives before choosing a preferred option.
• Assign someone to test the assumptions, or ask the group to imagine the decision has failed and explain why.
• Ask each side what would have to be true for the other side’s position to be right. This moves the discussion from advocacy to evidence.
• Record minority views on high-consequence decisions.

None of this means permanent opposition. The aim is to separate social agreement from the strength of the evidence. The bad news early article looks at how businesses teach people whether challenge is safe.

Separate the person from the idea

Disagreement stays useful only while it is about the idea. Once a discussion moves from “this assumption looks weak” to “sales are always difficult” or “he never supports anything new”, learning stops and people defend themselves instead. A few habits help keep challenge focused:

• Describe the evidence, not the motive: “the last three jobs ran over on this step” rather than “you always underestimate”.
• Challenge the proposal, not the proposer, and invite the proposer to test their own idea.
• Thank people for raising concerns, especially when the concern turns out to be wrong. The goal is to keep concerns coming.
• Deal with personal friction separately, privately and promptly, so it does not leak into decisions.

Leaders set the tone. When the owner responds to a challenge with curiosity rather than defensiveness, the rest of the team learns that challenge is part of the job.

Prepare the decision, not just the meeting

Many poor decisions are made in poorly prepared meetings. For significant choices, circulate a short note beforehand: the decision required, the options, the key facts, what is uncertain and who will decide. Describe the problem without implying the answer. People who arrive having thought about the question contribute far more than people seeing it for the first time, and quieter members have a chance to form views before the discussion starts.

Match the challenge to the stakes

Reversible decisions can tolerate quicker judgement and more experimentation, because the cost of being wrong is small. Decisions that are expensive or hard to reverse deserve stronger challenge and evidence. A useful habit is to ask, before a significant meeting, how reversible the decision is and how much challenge it therefore needs.

Participation is not accountability

A meeting with ten contributors still needs one person who owns the decision and its consequences. Otherwise, everyone participated and nobody is responsible. Every significant decision should end with:

• who made the decision;
• what was decided, including the alternatives considered;
• who does what, by when;
• when the decision will be reviewed.

When effort drops because responsibility is shared, the answer is usually not to blame individuals but to make contributions visible and responsibilities specific.

Disagree, then commit

Healthy teams can disagree strongly during the discussion and then commit fully to the decision once it is made, without pretending the debate never happened. That requires two things: people must feel their concerns were genuinely heard, and the decision must be made clearly by someone with authority to make it. If either is missing, decisions get reopened and quietly undermined.

A worked example

This is an illustration. The leadership team of a 45-person printing business, the owner and four managers, has worked together for years and gets on well. In one short meeting, they agree to buy a large new digital press for about $600,000 to compete for high-volume packaging work. The owner proposes it, the sales manager is enthusiastic and the others nod.

Two months later, the production manager admits privately that he had doubts from the start: the building’s power supply would need an expensive upgrade, and the existing operators had no experience with that type of press. He had said nothing because the owner seemed certain and the team “doesn’t do conflict”.

Before signing the purchase contract, the owner reopens the decision with a different process:

• Each manager writes down concerns independently before any discussion.
• The production manager and the finance manager speak first.
• Alternatives are required: leasing a smaller press, partnering with a larger printer for overflow work, or a staged approach starting with one major customer.
• The team asks what would have to be true for the purchase to succeed: enough committed volume, a manageable power upgrade, trained operators within three months.

The concerns surface quickly. The power upgrade is estimated at about $85,000, and only one customer has committed volume. The team chooses a staged approach: an overflow partnership for six months to prove demand, operator training in the meantime and a decision on the press once two customers have committed. The owner is named as the decision owner, the production manager owns the technical readiness plan and the review date is set.

The team stays close. But the next significant decision follows the same process, starting with the people least likely to speak.

How this applies to a small Australian business

In small businesses, decisions are often made quickly by the owner and a few trusted people, which is efficient but vulnerable to unspoken doubts. Practical steps:

• Treat silence as unknown, not as agreement.
• Ask what a conflict is really about before resolving it.
• Hear the less senior people first on important decisions.
• Require alternatives and test assumptions before deciding.
• Match the level of challenge to how reversible the decision is.
• Name a decision owner and record actions and review dates.
• Fix the structure behind recurring arguments.

The resolving workplace conflict professionally article covers handling interpersonal conflict directly.

Signals worth watching

• Important decisions made very quickly with little discussion.
• Specialists who rarely speak in meetings.
• Everyone converging once the owner states a view.
• The same disagreement returning after it was apparently resolved.
• One function always described as “difficult”.
• Action items shared so widely that nobody owns them.
• Concerns raised privately after decisions are made.

Common mistakes

• Assuming harmony means good decisions.
• Treating structural conflict as a personality problem.
• Compromising by reflex on incompatible options.
• Letting the most senior person speak first.
• Confusing participation with accountability.
• Reopening decisions because they were not made clearly the first time.

Frequently asked questions

Won’t encouraging dissent slow us down? For routine decisions, keep it light. For significant, hard-to-reverse decisions, a little structured challenge usually saves far more time than it costs.

How do I get quiet people to speak up? Ask them directly, ask them first, give them time to prepare and respond well when they raise something uncomfortable. People watch what happens to the first person who challenges.

What if the team keeps arguing after a decision? Check whether people felt heard and whether the decision was clearly made. If both are true, restate the decision, its owner and the review date, and ask people to raise new evidence at the review rather than reopening it now.

Should the owner always decide? Not always. Many decisions are better made by the person closest to the work, within clear limits. What matters is that everyone knows who decides each type of question.

What is a pre-mortem? A short exercise in which the group imagines the decision has failed some months from now and lists the reasons. It surfaces concerns people may otherwise keep to themselves.

Does this apply to a business with only two or three decision-makers? Yes, perhaps more so. A small group can converge very quickly, especially when one person owns the business. Asking for alternatives and inviting a trusted outsider, such as an adviser or an experienced staff member, to challenge significant decisions provides the diversity of view a small group lacks.

Questions to ask

• Which disagreements are we treating as personality problems that may be structural?
• Where might silence look like agreement but not be?
• Which upcoming decisions are hard to reverse and need more challenge?
• Who speaks first in our important meetings?
• Does every significant decision have a named owner and review date?
• When did a disagreement last change our minds rather than produce a compromise?

Bringing it together

Good teams make poor decisions when agreement comes more easily than evidence. Treat conflict as information about objectives, resources, authority or evidence, and respond to its real cause. Build dissent into important decisions by hearing junior voices first, requiring alternatives and testing assumptions, and match the level of challenge to how reversible the decision is. Then decide clearly, name an owner and commit. The aim is neither constant debate nor easy harmony, but a way of deciding that uses everything the team knows.

---

Source: KEVOS notes, drawing on teaching material on team decision processes, groupthink, conflict handling styles and leading project teams. Examples and figures in this article are illustrations.