Most of the advice written about groupthink was built for a room I have never sat in. It assumes you have a board, a chair, a facilitator, and a dozen senior people whose job is partly to disagree with each other. That is not the world most of us run in. In a business of five to twenty people, the owner is usually in the room for every call that matters, there is no HR department to enforce a process, and nobody was hired to play referee. The friction is different, and so are the fixes.
I have managed sales teams for a long time, and I have led a business turnaround where the margin for a bad call was thin. The pattern I watched most often was not people shouting each other down. It was the opposite. A decision would get floated, the most senior or most confident voice in the room would lean one way, and within a minute everyone else had quietly folded in behind it. No argument, no visible disagreement, just a room agreeing to agree. That is groupthink in a small business, and it is quieter and more dangerous than the version in the textbooks.
What groupthink actually looks like in a small team
The term comes from the psychologist Irving Janis, who used it to describe how cohesive groups can prioritise harmony and agreement over a realistic appraisal of the options in front of them (Janis, 1972). His case studies were government and military decisions. The mechanism, though, scales all the way down to a team meeting in a warehouse office.
In a small business it rarely presents as blind loyalty. It presents as deference. When the team is tight-knit and you all see each other every day, the social cost of disagreeing with the boss is high. Pushing back on the owner’s idea is not an abstract debate; it is a thing you have to do to a person you will share a kitchen with tomorrow morning. So people don’t. They nod, the meeting ends early, and the owner walks out thinking the plan had unanimous support when really it just had no oxygen for dissent.
Two features of small teams make this worse than it would be in a larger organisation. The first is simple arithmetic. Fewer people means less natural disagreement. In a team of forty, the odds that someone holds a genuinely different view and is willing to say so are reasonable. In a team of six, one dominant voice can carry the whole room without anyone consciously suppressing anything. The second is proximity. The closer and more personal the working relationships, the more a disagreement feels like a relationship problem rather than a work problem.
The classic conformity research backs this up. Studies of group conformity going back to the 1950s suggest that a meaningful share of people will agree with a clearly incorrect group position rather than stand alone against it, even on questions with an obvious right answer (Asch, 1955). If people will fold on something objectively verifiable, they will certainly fold on a judgement call like whether to hire someone or which software to buy.
The generic corporate advice on this topic, whether from governance platforms aimed at boards (Boardwise, n.d.) or process-improvement blogs (EO Johnson, n.d.), tends to recommend structures a small business does not have and cannot justify: independent directors, formal red-team exercises, standing review committees. The principles underneath are sound. The delivery needs to fit a team that meets around a single table. Here is what I actually do.
Tactic 1: Make pushback a job, not a personality trait
The single most useful change I have made is to assign a rotating devil’s advocate for any decision that matters. Before the discussion starts, one person is named and told their job for this meeting is to argue against whatever the group seems to be leaning towards. Next meeting, someone else takes the role.
This works because it removes the personal risk. When disagreeing is your assigned task, nobody reads it as you being difficult or disloyal. You are doing the thing you were asked to do. I have watched quiet staff members, who would never volunteer an objection, pick apart a plan with real skill once they had explicit permission to do it. The role also stops one naturally contrarian person from becoming “the negative one” who gets tuned out. Rotating it means everyone practises the skill and nobody owns the reputation.
The trick is to take it seriously yourself. If you are the owner and the devil’s advocate lands a good hit on your idea, you have to visibly take it on board, or the whole thing becomes theatre and people learn that dissent is decorative.
Tactic 2: Collect opinions before the loudest voice speaks
The cheapest and most effective intervention is to gather views before the group discussion, not during it. Once the room has heard the owner or the senior person signal a preference, most people anchor to it without realising. If you collect input first, opinions form independently.
It does not need to be fancy. Before a meeting on a real decision, I ask people to send me their view in a sentence or two, or I have everyone write their position on a card before anyone speaks. Then I read them out, including the ones that disagree. The point is that the quiet and the junior members get their view into the room before the consensus forms, rather than after it has already set. This is closely tied to the broader problem of getting reserved staff to contribute at all, which I have written about separately in my guide to building psychological safety in a small business team.
Anonymity raises the quality of what you get back. People are markedly more honest when their name is not attached, especially when the honest answer is “I think the boss is wrong.” If you want the mechanics of that, my piece on getting honest answers through anonymous feedback covers why the anonymity matters and where it breaks down.
Tactic 3: Bring in one outside perspective
A small team has a shared context, which is a strength most of the time and a blind spot when it comes to big calls. Everyone knows the same things, assumes the same things, and has absorbed the same habits. That is exactly the condition in which a bad idea can feel obviously right to all of you at once.
The fix is to get one perspective from outside the shared context before you lock the decision in. It does not have to be a paid consultant. It can be a mentor, a peer who runs a similar business, or a trusted customer who will tell you the truth. I sit on both sides of this as a business mentor through the Digital Leap Moreton Bay program, and the value is rarely some brilliant insight. It is usually just a person who is not inside your assumptions asking, “Why this and not that?” and forcing you to answer out loud.
One outside voice can break a false consensus faster than any internal process, because that person carries none of the social cost your own staff are quietly calculating.
Tactic 4: Separate generating ideas from judging them
A lot of good input dies in the first thirty seconds because someone criticises it before it is fully out. Early criticism does not just kill the idea being discussed; it teaches everyone watching to keep their own half-formed thoughts to themselves. In a small team where there are only a handful of ideas to begin with, you cannot afford that attrition.
I keep the two phases apart. First, we generate: every option goes up, nothing gets shot down, and “that won’t work because” is not allowed yet. Only once the options are all on the table do we move to evaluating them. Keeping these separate means timid or unpolished ideas survive long enough to be considered, and it stops the meeting from collapsing into a defence of whatever got said first. It also slows down the rush to agree, which is the engine of groupthink in the first place.
Tactic 5: Name who actually decides
Here is a failure mode specific to small teams. Because everyone is consulted on everything and the lines are blurry, people assume a decision needs consensus when it does not. That slows real calls to a crawl and, worse, it distorts them. When a group is chasing unanimous agreement, the decision drifts towards whatever offends nobody rather than whatever is right.
The fix is to be explicit, before the discussion, about who decides and who is being consulted. Input is not the same as a vote. I will happily gather everyone’s view on a hire or a purchase, and I want that input to be real and uncomfortable if it needs to be. But the team should know from the outset whether this is a decision I am making with their counsel or a decision we are making together. Naming that up front does two things: it frees people to give honest input without feeling they are haggling over a veto, and it stops consensus-seeking from quietly becoming the decision rule by default. Formal frameworks exist for mapping this out, but for a team of ten a single sentence at the top of the meeting usually does the job.
This is also consistent with how Australian workplace guidance frames consultation. The point of consulting staff is to genuinely consider their views before a decision is made, not to hand the decision to a vote (Fair Work Ombudsman, n.d.). Consultation and decision rights are different things, and keeping them straight is what stops both groupthink and paralysis.
A small example of how this plays out
A business owner I was mentoring had a team of about eight and was close to signing a twelve-month contract for a new job-management system. In the meeting where they reviewed it, the owner was clearly keen. The demo had gone well and they had already half-committed in their own head. Everyone in the room could read that, and the conversation became a short run of agreement. The contract was about to be signed on the back of a meeting where not one person had raised a concern.
What surfaced the problem was not a formal review. It was a single pre-meeting question I had asked the owner to put to the team in writing and anonymously: “What is the strongest reason not to buy this?” Two of the eight responses, from staff who had sat silent in the room, flagged that the new system did not handle the way their casual staff clocked on, which was the exact workflow they used every day. That was not a small detail. It would have made the tool a daily source of friction for half the team. They renegotiated, the vendor added the feature, and the contract that got signed was a better one.
Nobody in that business was incompetent and nobody was dishonest. The staff who spotted the flaw simply were not going to say it out loud in a room where the owner was visibly sold. The anonymous pre-meeting question gave their concern a path to the decision-maker before the consensus closed over it. That is the whole game.
Where a tool fits
Most of this is behaviour, not software, and I would be lying if I said otherwise. You can run every tactic above with index cards and a bit of discipline. What a tool buys you is consistency and a record. The reason I built Business Review 360 was that the “collect concerns before the meeting” step kept falling over in practice. People forgot, the owner was too busy to chase responses, and the good objections arrived after the decision was already made. Business Review 360 is designed to give a small team a standing place to log ideas and concerns ahead of a decision, anonymously if they prefer, so the quieter and more junior voices reach the decision-maker before the room settles. It is a practical tool for one specific habit, not a governance system, and it only helps if the behaviours around it are real.
Groupthink in a small business is not a dramatic failure of leadership. It is the slow, comfortable drift towards agreement that happens when disagreeing is socially expensive and nobody’s job is to make it cheaper. The fixes are small, cheap, and repeatable. You do not need a board. You need to make dissent a normal part of how the room works before the decision is made, not a brave act after it.
References
Asch, S. E. (1955). Opinions and social pressure. Scientific American, 193(5), 31-35.
Boardwise. (n.d.). How to avoid group thinking in corporate leadership and decision-making. https://www.boardwise.io/en/blog/how-to-avoid-group-thinking-in-corporate-leadership-and-decision-making
EO Johnson. (n.d.). How to avoid groupthink in decision making. https://www.eojohnson.com/blog/how-to-avoid-groupthink-in-decision-making
Fair Work Ombudsman. (n.d.). Consultation and cooperation in the workplace best practice guide. https://www.fairwork.gov.au/tools-and-resources/best-practice-guides/consultation-and-cooperation-in-the-workplace
Janis, I. L. (1972). Victims of groupthink: A psychological study of foreign-policy decisions and fiascoes. Houghton Mifflin.
FAQ
What is the difference between groupthink and just agreeing with each other?
Genuine agreement survives scrutiny. If you actively invite the strongest objection and nobody can find one, that is alignment. Groupthink is when the agreement formed because disagreeing felt costly, not because the idea was tested. The tell is whether any real counter-argument was ever voiced. If every decision sails through with zero friction, you are almost certainly not hearing the objections rather than not having any.
Is groupthink really a risk in a team as small as five people?
It is more of a risk, not less. Small teams have fewer independent viewpoints to begin with, and the relationships are close enough that disagreeing with a colleague or the owner carries real social cost. A single confident voice can carry a room of five without anyone consciously suppressing a contrary view. The smaller and tighter the team, the more deliberate you have to be about creating space for dissent.
How do I get staff to disagree with me without it feeling like a challenge to my authority?
Make it a structured request rather than an open invitation. Assigning a rotating devil’s advocate, or asking for the strongest reason against a plan in writing, reframes disagreement as a task you handed out rather than a challenge someone chose to mount. The other half is your own reaction. If you visibly take a good objection on board at least some of the time, people learn that dissent is wanted. If you argue back every time, they learn to stop.
Do I need software to manage team decisions, or is this just a process problem?
It is mostly a process problem, and you can run all of these tactics with nothing more than a notepad and some discipline. Software helps with the one step that tends to fall over in a busy small business: consistently collecting concerns before a meeting and keeping a record of them. A tool makes that habit automatic rather than something the owner has to remember to chase. The behaviours matter more than the tool, though, and no software will save a team where dissent is quietly unwelcome.
When should a small business not bother consulting the team on a decision?
When the decision is time-critical or genuinely reversible at low cost. Not every call needs input, and pretending otherwise just adds meeting overhead and trains people to tune out. The consultation tactics here are for decisions that are expensive to get wrong and hard to undo: a hire, a contract, a major purchase, a change to how the business runs. For a quick, low-stakes, easily reversed call, make it and move on. Naming which kind of decision you are facing, out loud, is itself a useful discipline.