Quick answer
Your team is probably quiet because speaking up in front of a leader feels risky, and live group discussion makes thinking out loud hard, not because they have no ideas. Make it safer to speak, give people time to think before they are asked to answer, let ideas arrive in writing, hold back your own view until others have spoken, and show what you do with what you hear.
Five ways to get more ideas from a quiet team:
- Lower the risk before you ask: Show that uncertainty and imperfect ideas are welcome, and thank the first contribution.
- Send the question and agenda ahead of time: Give people a day or two to think, and tell them how their ideas will be used.
- Let ideas arrive in writing first: Use silent writing or a shared document so ideas are not limited by who speaks fastest.
- Speak last and hold judgement: Ask, wait, share your view after others, and keep generating ideas separate from judging them.
- Respond visibly and close the loop: tell people what you will do with each idea, what you will not, and why.
The aim isn’t to make everyone talk more. It’s to make offering an idea feel safer and easier than staying silent.
Many leaders I work with have asked their team for ideas and been met with silence, a few polite nods, or the same one or two voices. It is tempting to read that quiet as a lack of ideas or a lack of interest. Research on voice and silence at work suggests a different reading: people often hold back for reasons that have more to do with the setting, the risk and the format than with the quality of their thinking.
That is encouraging, because setting, risk and format are things a leader can change. This article looks at why teams go quiet and offers five practical ways to shift it, each grounded in research and each small enough to try in your next meeting.
Why teams go quiet
Speaking up in front of a leader involves interpersonal risk. Amy Edmondson’s work on psychological safety describes a shared belief within a team about whether it is safe to take that kind of risk, and her study of 51 manufacturing teams found it was associated with learning behaviour. Reviews of the voice and silence literature suggest that people weigh up whether speaking up will be safe and worthwhile, and that silence can become a collective pattern across a team or an organisation.
Often the rules are unwritten. Research on what are called implicit voice theories suggests that many people carry taken-for-granted beliefs, such as not embarrassing the boss or not speaking until they have solid data. These beliefs appear to help explain silence even when a leader sincerely wants input.
The format matters too. Experiments on group brainstorming found that people often produce fewer ideas in a group than the same number of people working alone, and in those studies having to wait for a turn to speak accounted for most of the loss. Put hierarchy, risk and a format that rewards the fastest talker together, and quiet is a reasonable outcome.
Five ways to get more ideas from a quiet team
1. Lower the risk before you ask
Psychological safety is not built by announcing it. In my experience it is shaped by what a leader does in the first few seconds after someone speaks. Studies of leadership behaviour and employee voice have examined how managerial openness relates to whether people speak up, which fits what I see in practice: people watch what leaders do far more closely than what they say.
- Name what you do not know: “I do not have the answer to this, and I need your thinking.”
- Say why their view matters and how you will use it.
- Invite disagreement explicitly: “What am I missing?”
- Thank the first contribution, especially an imperfect one, and ask a curious follow-up question.
- Share your uncertainty, not your preferred solution. Save your own view for later (see strategy 4).
2. Send the question and agenda ahead of time
Studies of meeting design suggest that using an agenda is associated with people rating a meeting as more effective. In one pair of studies covering more than 1,200 attendees, how involved people felt appeared to be part of the reason. A review of almost 200 studies on workplace meetings recommends circulating an agenda so that attendees can prepare beforehand.
A caution is worth making. This evidence is survey-based, and concerns perceptions of meetings, and none of it tests quiet team members directly or the timing of the ask. I treat it as a sensible, plausible lever rather than proven. In practice, many people simply think better when they have had time to consider a question before being asked to answer it.
A short message does the work. Include:
- The question, in one or two sentences.
- Why it matters now.
- How you will use the answers.
- How people can contribute: in writing beforehand, in the meeting, or one-to-one with you.
- The date, with a couple of days’ notice where you can.
Ask for one rough idea, not a polished proposal. That alone can lower the bar for taking part.
3. Let ideas arrive in writing first, together or asynchronously
Brainwriting, where people write ideas down rather than calling them out, is designed to reduce the waiting, anchoring and social pressure of live discussion. In small exploratory field studies in a high-technology company, alternating individual writing with group sharing and review produced more ideas, and periodic reviews performed best.
The evidence on electronic tools is more mixed. For small groups, any benefit of electronic brainstorming may be an illusion, and people working alone first could do as well. For larger groups of around nine or more, the benefits may be real, although researchers disagree about how strong the evidence is. For most teams, then, the practical lesson is to have people think and write on their own before they talk, whether or not you add technology.
- In the room: give five minutes of silent writing, one idea per note, then collect the notes and read them out or cluster them without saying who wrote what.
- Asynchronously: post one open question in a shared document or board for about 48 hours, add your own contribution last, then use a short live session to cluster, build and decide.
- Alternating: write, share, then write again, so people can build on what they have heard.
4. Speak last and hold judgement until the ideas are on the table
Leaders carry weight in a room. If implicit rules such as not embarrassing the boss are in play, an early opinion from you can close a conversation before it opens. In the brainstorming experiments, inducing a sense of being evaluated reduced productivity even for people working alone, although waiting for a turn accounted for most of the loss in group sessions. Keeping idea generation and idea evaluation apart looks like a sensible response to both.
- Ask, then stay quiet for longer than feels comfortable.
- Speak last, and ask “What else?” once or twice before you do.
- Run two rounds: first generate, with no evaluation, then agree your criteria and evaluate.
- Replace “Any ideas?” with a more specific question, such as “What is one thing we could stop doing?”, “What could go wrong, and what would we do about it?” or “If we had half the time, what would you change?”
5. Respond visibly and close the loop
Silence can become self-reinforcing. In one set of studies in restaurants, managers rated employees who spoke up in supportive ways more positively than those who spoke up in challenging ways. That is one setting, so I would not generalise far, but it hints at why people may be wary of offering a challenge. Whether your team learns that ideas are welcome probably depends less on the invitation and more on what happens afterwards.
- Acknowledge every idea within a couple of days, even if only to say thank you.
- Say what you will do with it, what you will not do, and why.
- Share a short “you said, we did” update so contributions are visibly used.
- Notice your own reaction to a challenging idea, and credit the person who raised it.
- Follow up one to one with people who have said little.
A simple way to start
Choose one upcoming meeting where you want ideas. Send the question two days ahead, open with five minutes of silent writing, speak last, and reply to every contribution within 48 hours. Then notice what changes, and what you would adjust next time.
A few questions to reflect on:
- When I last asked for ideas, what did I do in the first ten seconds after someone spoke?
- Which unwritten rules might my team be following about speaking to me?
- Which way of asking am I most comfortable with, and who does it leave out?
Further reading
- How can I get my team to speak up?: Psychological safety and voice, and how to create the conditions for honest input.
- What psychological safety actually means for teams: A clear look at the research and what it means in practice.
- Psychological safety: Amy Edmondson’s research and what it suggests about building a culture where speaking up feels safe.
- Leadership myth: silent employees are fine: Why silence is better read as a signal than as agreement.
- How can I make my meetings more effective?: Meeting design, agenda, decision rights and follow-through.
- Inclusive leadership: Making sure every voice is heard and valued.
- Team Dynamics Framework: An original model covering alignment, trust, accountability and collaboration.
Want help getting your team’s best thinking into the room?
For You: Leadership Clinic
Bring one meeting or decision where you need more ideas than you are getting. I prepare beforehand, then we spend 90 focused minutes reshaping how you ask, who you ask and what you do with the answers. One challenge, one session, no ongoing commitment.
For You: Executive Coaching
For leadership habits that need more than one conversation. Work with me over time to become clearer, more specific and more skilful in how you invite, hear and use your team’s ideas.
For Your Organisation: Teams & Facilitation
Bring me in to work with your team on how it shares ideas, challenges assumptions and makes decisions together, through practical sessions and facilitated conversations.
Choose the level of support that fits what you are working through.
Sources
Burris, E.R. (2012) ‘The risks and rewards of speaking up: managerial responses to employee voice’, Academy of Management Journal, 55(4), pp. 851–875. doi:10.5465/amj.2010.0562.
Cohen, M.A., Rogelberg, S.G., Allen, J.A. and Luong, A. (2011) ‘Meeting design characteristics and attendee perceptions of staff/team meeting quality’, Group Dynamics: Theory, Research, and Practice, 15(1), pp. 90–104. doi:10.1037/a0021549.
Dennis, A.R. and Valacich, J.S. (1999) ‘Electronic brainstorming: illusions and patterns of productivity’, Information Systems Research, 10(4), pp. 375–377. doi:10.1287/isre.10.4.375.
Detert, J.R. and Burris, E.R. (2007) ‘Leadership behavior and employee voice: is the door really open?’, Academy of Management Journal, 50(4), pp. 869–884. doi:10.5465/amj.2007.26279183.
Detert, J.R. and Edmondson, A.C. (2011) ‘Implicit voice theories: taken-for-granted rules of self-censorship at work’, Academy of Management Journal, 54(3), pp. 461–488. doi:10.5465/AMJ.2011.61967925.
Diehl, M. and Stroebe, W. (1987) ‘Productivity loss in brainstorming groups: toward the solution of a riddle’, Journal of Personality and Social Psychology, 53(3), pp. 497–509. doi:10.1037/0022-3514.53.3.497.
Edmondson, A. (1999) ‘Psychological safety and learning behavior in work teams’, Administrative Science Quarterly, 44(2), pp. 350–383. doi:10.2307/2666999.
Edmondson, A.C. and Lei, Z. (2014) ‘Psychological safety: the history, renaissance, and future of an interpersonal construct’, Annual Review of Organizational Psychology and Organizational Behavior, 1(1), pp. 23–43. doi:10.1146/annurev-orgpsych-031413-091305.
Leach, D.J., Rogelberg, S.G., Warr, P.B. and Burnfield, J.L. (2009) ‘Perceived meeting effectiveness: the role of design characteristics’, Journal of Business and Psychology, 24(1), pp. 65–76. doi:10.1007/s10869-009-9092-6.
Morrison, E.W. (2014) ‘Employee voice and silence’, Annual Review of Organizational Psychology and Organizational Behavior, 1(1), pp. 173–197.
Morrison, E.W. and Milliken, F.J. (2000) ‘Organizational silence: a barrier to change and development in a pluralistic world’, Academy of Management Review, 25(4), pp. 706–725. doi:10.2307/259200.
Mroz, J.E., Allen, J.A., Verhoeven, D.C. and Shuffler, M.L. (2018) ‘Do we really need another meeting? The science of workplace meetings’, Current Directions in Psychological Science, 27(6), pp. 484–491. doi:10.1177/0963721418776307.
Paulus, P.B. and Yang, H.-C. (2000) ‘Idea generation in groups: a basis for creativity in organizations’, Organizational Behavior and Human Decision Processes, 82(1), pp. 76–87. doi:10.1006/obhd.2000.2888.
Paulus, P.B., Korde, R.M., Dickson, J.J., Carmeli, A. and Cohen-Meitar, R. (2015) ‘Asynchronous brainstorming in an industrial setting: exploratory studies’, Human Factors, 57(6), pp. 1076–1094. doi:10.1177/0018720815570374.
Pinsonneault, A., Barki, H., Gallupe, R.B. and Hoppen, N. (1999) ‘The illusion of electronic brainstorming productivity: theoretical and empirical issues’, Information Systems Research, 10(4), pp. 378–380. doi:10.1287/isre.10.4.378.
Image source: Kirill Makes Pics on Pixabay



