Drawing Out Quiet Voices and Managing Dominant Ones in Team Brainstorms

In a product manager interview, you are asked how you encourage participation when you run a brainstorming session. Explain the specific things you do so that ideas come from the whole group rather than from a few voices, and illustrate your approach with an example from your own work. ```hint Ask why someone stays quiet Before listing tactics, think about why a particular person might hold back in a session, and make sure each tactic you describe answers one of those reasons. ``` ### Clarifying Questions - Is the session in person, remote or hybrid? - Who usually attends: only the product team, or a cross-functional group that includes senior leaders and people from outside product? - Is the problem a group that stays quiet overall, or one or two people who dominate the discussion? ### What a Strong Answer Covers - A diagnosis of why people hold back, such as rank, thinking style, fear of judgment, unclear relevance or remote friction - Concrete tactics before, during and after the session, each tied to a cause - How to handle dominant or senior voices without shutting them down - Follow-through that shows contributors their ideas mattered, which drives participation next time - An example with evidence that participation actually improved ### Follow-up Questions - A senior leader in the room keeps steering the group toward their own idea. What do you do in the moment? - How would you know that participation actually improved, rather than that the session simply felt better? - One teammate never speaks during sessions but later sends strong ideas in writing. How do you adapt?