Skip to content
Go back

Meetings: The More People You Invite, the Fewer Ideas Come Out

Illustration of a crowded meeting table with only one active voice

In 1958 three Yale researchers ran a simple experiment. They asked students to generate ideas about a problem. Some worked in groups of four. Others worked alone, and their ideas were then pooled with duplicates removed: what the literature calls a “nominal group”, a group on paper only.

The nominal groups produced more ideas. And the ideas were judged better.

Taylor, Berry and Block weren’t attacking a passing fad. Five years earlier Alex Osborn, an advertising executive, had published Applied Imagination, the book that invented brainstorming and claimed a group produces roughly twice as many ideas as the same individuals working separately. That number didn’t come from an experiment. It came from the author’s professional experience.

It has been redone many times since. In 1987 Diehl and Stroebe reviewed the studies and added their own to work out why it happens. In 1991 Mullen, Johnson and Salas ran the meta-analysis: the productivity loss of real groups compared with nominal ones is systematic, and it grows with group size.

Seventy years on, brainstorming in a meeting room is still the default reaction when an idea is needed.

The three reasons groups produce less

It isn’t that people become stupid in groups. There are three distinct mechanisms, and each has been isolated experimentally.

Production blocking. In a conversation only one person speaks at a time. While you wait your turn you have to hold your idea in memory, and meanwhile you generate no others. If someone then says something similar, yours no longer makes sense and you drop it. Diehl and Stroebe identified this as the main cause: when they experimentally removed the wait for a turn, the gap narrowed considerably. In a group of eight, each person has on average one eighth of the talking time, and all the remaining time to forget what they meant to say.

Evaluation apprehension. Half-formed ideas are the ones that lead furthest, but they’re also the ones that expose you. In front of colleagues, and especially in front of a boss, the threshold for what gets said out loud rises. Nobody needs to criticise: the possibility is enough.

Social loafing. In 1913 the agricultural engineer Maximilien Ringelmann measured the force exerted by people pulling a rope, alone and in groups. In groups, force per person fell as the group grew. Karau and Williams in 1993 meta-analysed 78 studies on this effect: it’s robust, and it’s stronger when the individual contribution can’t be distinguished from everyone else’s. In a twelve-person meeting, the individual contribution is indistinguishable by definition.

MechanismWhat triggers itWhat reduces it
Production blockingA single shared speaking channelGenerating ideas in writing, in parallel
Evaluation apprehensionHierarchy and an audienceAnonymous collection before discussion
Social loafingIndividual contribution not identifiableAssigning named responsibilities

The common thread is group size. All three get worse as you add people.

The cost that doesn’t show up in the calendar

A one-hour meeting with eight people doesn’t cost eight hours. It costs more, and the extra part isn’t visible anywhere.

Sophie Leroy in 2009 described what she called attention residue: when you switch from one task to another, part of your attention stays attached to the previous one, and performance on the new task suffers. It’s worse when the first task was interrupted without being finished, which is exactly the situation of someone pulled away from work by a meeting.

Gloria Mark and colleagues in 2008 measured how long it takes to genuinely get back into a task after an interruption: about 23 minutes on average. Two meetings scattered through an afternoon don’t cost two hours. They cost the afternoon.

On overall load there’s direct evidence. Luong and Rogelberg in 2005 followed workers day by day and found that the number of meetings in a day was associated with greater fatigue and a higher perceived workload, regardless of how much work there actually was. Rogelberg and colleagues in 2006 showed the relationship isn’t the same for everyone: people with a strong drive to complete things suffer more from time spent in meetings.

Then there’s what the people involved think. Perlow, Hadley and Eun in 2017 surveyed 182 senior managers: 71% considered meetings unproductive and inefficient, 65% said meetings kept them from completing their own work, 64% said they came at the expense of deep thinking. It should be said this is an opinion survey, not a performance measure: it tells you how people feel, not how much they produce.

An agenda on its own doesn’t do it

The most repeated advice about meetings is to have an agenda. It’s good advice, but the evidence says that on its own it moves almost nothing.

Bang and colleagues in 2010 studied the top management group meetings of several Norwegian organisations, measuring both formal characteristics and actual behaviours. What predicted perceived effectiveness and the decisions reached was goal clarity and the way people communicated, not the mere presence of a document listing the points.

Kauffeld and Lehmann-Willenbrock went deeper in 2012: they video-recorded real meetings and coded every single utterance. Groups where solution-focused statements chained into one another performed better. Groups that fell into complaining cycles, where each complaint triggered another, did worse, and the effect showed up in organisational indicators later on.

It isn’t the format. It’s what gets said inside it.

A meeting with one more person invited isn’t a meeting with one more person. It’s a different meeting, in which everyone else speaks less.

Fewer people, ideas written first, clear roles

  1. Ask what has to come out of it before booking it. If the answer is “to align”, it isn’t a meeting: it’s an update, and a written message does it better without synchronising eight calendars.
  2. Have ideas generated beforehand, in writing and alone. Ten minutes where each person writes their proposals, then you pool them. This is the nominal group from the 1958 studies, and it’s the single change with the most evidence behind it.
  3. Cut the invitees, not the minutes. Trimming from sixty to forty-five minutes moves little. Going from ten people to four changes the mechanism. Whoever is needed to decide stays, the rest read the summary.
  4. Give each person a named role. Who decides, who brings the data, who writes the conclusions. Social loafing eases when the contribution is identifiable: that’s what the meta-analysis says, and it costs one line in the invitation.
  5. Cluster meetings into the same block. Given how slow the return is after an interruption, three back-to-back meetings do less damage than three scattered ones. This matters even more in remote work, where the gaps between calls disappear.
  6. Break complaining cycles. When the discussion spirals, bring it back to what gets done and who does it. That’s a feedback skill, not corporate etiquette.
  7. Close with a written decision. Who does what by when. If you can’t write it down, the meeting produced nothing and it’s better to know immediately. In structured projects this flows naturally into phase management.

If your role has you speaking in front of groups often, much of the problem shifts to how you present: I’ve written about that in public speaking.

My take: meetings exist to share out responsibility

That was the data. This part is what I think, and I’m keeping it separate.

I believe meetings survive not because they work, but because they solve a different problem from the stated one. A meeting distributes responsibility: if the decision was made by ten people, nobody really made it. In organisations where being wrong alone is expensive, gathering a lot of people is a form of insurance. Seen that way, producing few ideas isn’t a flaw in the method. It’s the price being willingly paid.

There’s a less cynical reason too. Many pointless meetings exist because someone fears being left out, and inviting everyone is the cheapest way to offend nobody. The cost of that courtesy isn’t paid by the person sending the invitation; it’s paid by the eight people who spend an hour there.

That said, I’m wary of anyone who declares war on meetings wholesale. Nearly eliminating them risks not making the problems disappear: they move into chat, in a more fragmented form and with nobody closing anything. The point isn’t fewer meetings in absolute terms. It’s that the ones left should have few people, a stated objective and a written decision at the end.

Frequently asked questions

So should brainstorming be abolished? No, it should be split into two stages. Generating ideas works better individually; selecting and developing them works well in a group. The problem is doing both at the same moment in the same room.

How many people maximum? There’s no research-validated number. What the evidence says clearly is the direction: the loss grows with size. Rules like “no more than seven” are practical heuristics, not experimental results.

Does this apply to online meetings too? The basic mechanisms hold: one person speaks at a time, and on video the turn-taking is even more rigid. On social loafing online the evidence is thinner, so I won’t push further than that.

What if the boss wants everyone there? That’s a situation of power, not method. The only realistic lever is proposing the written pre-work: it costs little, takes nothing away from anyone and usually meets no resistance.

Is the “23 meetings a week” figure you see everywhere true? Numbers like this circulate widely without a traceable source, often bounced from one article to the next. I chose not to use them: the figures cited here come from studies with a stated method, and even those should be read for what they are.

Sources

  1. Taylor, D. W., Berry, P. C., & Block, C. H. (1958). Does Group Participation When Using Brainstorming Facilitate or Inhibit Creative Thinking?. Administrative Science Quarterly, 3(1), 23–47. The first comparison of real and nominal groups.
  2. Osborn, A. F. (1953). Applied Imagination. The book introducing brainstorming and the experimentally unverified claim that groups double idea output.
  3. Diehl, M., & Stroebe, W. (1987). Productivity loss in brainstorming groups: Toward the solution of a riddle. Journal of Personality and Social Psychology, 53(3), 497–509. Identifying production blocking as the main cause.
  4. Mullen, B., Johnson, C., & Salas, E. (1991). Productivity Loss in Brainstorming Groups: A Meta-Analytic Integration. Basic and Applied Social Psychology, 12(1), 3–23. The quantitative synthesis and the link with group size.
  5. Karau, S. J., & Williams, K. D. (1993). Social loafing: A meta-analytic review and theoretical integration. Journal of Personality and Social Psychology, 65(4), 681–706. The 78 studies on social loafing and the conditions that reduce it.
  6. Leroy, S. (2009). Why is it so hard to do my work? The challenge of attention residue when switching between work tasks. Organizational Behavior and Human Decision Processes, 109(2), 168–181.
  7. Mark, G., Gudith, D., & Klocke, U. (2008). The Cost of Interrupted Work: More Speed and Stress. Proceedings of CHI 2008. The measurement of resumption time after an interruption.
  8. Luong, A., & Rogelberg, S. G. (2005). Meetings and More Meetings: The Relationship Between Meeting Load and the Daily Well-Being of Employees. Group Dynamics, 9(1), 58–67.
  9. Rogelberg, S. G., Leach, D. J., Warr, P. B., & Burnfield, J. L. (2006). “Not Another Meeting!” Are Meeting Time Demands Related to Employee Well-Being?. Journal of Applied Psychology, 91(1), 83–96.
  10. Bang, H., Fuglesang, S. L., Ovesen, M. R., & Eilertsen, D. E. (2010). Effectiveness in top management group meetings: The role of goal clarity, focused communication, and learning behavior. Scandinavian Journal of Psychology, 51(3), 253–261.
  11. Kauffeld, S., & Lehmann-Willenbrock, N. (2012). Meetings Matter: Effects of Team Meeting Communication on Team and Organizational Success. Small Group Research, 43(2), 130–158. The analysis of recorded utterances and complaining cycles.
  12. Perlow, L. A., Hadley, C. N., & Eun, E. (2017). Stop the Meeting Madness. Harvard Business Review. Survey of 182 senior managers; stated opinions, not performance measures.

This article was written following the process described in how we write. If you find a figure reported wrongly, write to me: I’ll correct it and note the correction at the bottom of the article.

Founder of UpSkillLab, with a Master's in Digital Marketing from the University of Florence. Every article starts from public sources cited in the text and is drafted with the help of AI tools, under my review and editorial responsibility: no purchased content, nothing published without human checking. Read the editorial method or report an error.


Share this post:

See all articles in Career & Work

Next Post
Cafés, Bars and Artificial Intelligence: What Really Changes Behind the Counter