The meeting ends. Everyone nods. Two people walk out, open a side channel, and type the objection they had the whole time. The decision ships anyway.
You have watched a version of this. It happens on teams where people like each other, where nobody has ever been punished for disagreeing, and where you have said out loud that you want the objection raised in the room.
Gallup puts a number on how common this is: only three in 10 U.S. workers strongly agree that at work, their opinions seem to count. Gallup's estimate is that organizations moving that ratio to six in 10 could realize a 27% reduction in turnover, a 40% reduction in safety incidents, and a 12% increase in productivity.
Researchers Have a Name for What Your Team Is Doing
Researchers study this under two labels. In Elizabeth Morrison's 2014 review of the field, upward voice is when "employees voluntarily communicate suggestions, concerns, information about problems, or work-related opinions to someone in a higher organizational position." Silence is withholding that same input, "depriving their organization of potentially useful information."
The definitions sound symmetrical. The behaviors underneath them come apart.
Silence Has Its Own Drivers
Sherf, Parke and Isaakyan tested whether silence is simply the absence of voice in a 2021 Academy of Management Journal paper. Across a meta-analysis and a six-month panel study, they found voice and silence are distinct constructs with different drivers and different consequences.
Two findings are useful to a manager. The meta-analysis put the correlation between voice and silence at ρ = −.15, weak enough to treat them as two separate behaviors that happen to look like opposites. The same meta-analysis found burnout tracks far more closely with silence (ρ = .32) than with voice (ρ = −.11), a gap the authors report as statistically significant. The six-month panel study reproduced that pattern over time. Sitting on something you wanted to say costs the person holding it more than saying it would.
Voice and silence also answer to different levers. Psychological safety in that data relates more strongly to silence than to voice, while perceived impact, the sense that input will change something, relates more strongly to voice. So safety is a legitimate lever on silence, and it is one input among several. You can raise how safe your team feels, watch meeting participation climb, and still have the same three people withholding the same three concerns. Safety is a skill your team has to keep practicing, and practicing it does not finish the job.
The Rules People Carry Into the Room
The closest thing the literature has to a root cause comes from James Detert and Amy Edmondson's 2011 study of implicit voice theories, which they define as taken-for-granted beliefs about when and why speaking up at work is risky or inappropriate.
Their first study interviewed employees at a large corporation and surfaced fine-grained, unspoken rules that kept people from offering even constructive suggestions. A second study tested whether those rules generalized beyond that one company. Two further studies built survey measures for five such beliefs and established that the five can be told apart from one another statistically and predict silence on top of what was already accounted for. Detert and Edmondson's summary of the four studies together is that implicit voice theories are widely held and significantly augment the explanation of workplace silence.
A multi-level study by Knoll, Neves, Schyns and Meyer, published in Applied Psychology in 2021, asked whether those beliefs are held collectively, across 696 employees in 129 teams at 67 organizations. Implicit voice theories turned out to be shared at the team level, and those shared beliefs explained variance in employees' motives for staying silent above and beyond perceptions of organizational voice climate and manager openness. Two teams can post identical climate and openness scores and differ in how much gets said, because they absorbed different rules about when saying it is appropriate.
What People Are Afraid Of Is Specific
The fear driving the decision is concrete. Milliken, Morrison and Hewlin's 2003 study interviewed 40 full-time employees and found 34 of the 40 could name at least one occasion where something at work troubled them and they felt unable to raise it with their boss.
The fears cluster into five. Being labeled or viewed negatively, as a troublemaker, a tattletale, or a complainer, was the one raised most often, by 30% of respondents. Damaging a working relationship followed at 27.5%, futility at 25%, fear of retaliation or punishment at 22.5%, and not wanting to upset or embarrass someone else at 20%. Most people named more than one, so the figures sum past 100. What drives the decision, in the authors' framework, is the anticipated outcome of speaking up, which employees forecast from their own past experiences and from what they have seen and heard happen to the people around them. Forty interviews is a small qualitative sample, so read the percentages as a ranking and not as a population estimate.
Silence Compounds Into an Organizational Property
Morrison and Milliken's 2000 paper on organizational silence argued that this stops being an individual trait once enough people do it. Silence, in their account, is "less a product of multiple, unconnected individual choices and more a product of forces within the organization" that systematically reinforce it.
They trace those forces to two things senior managers carry. One is fear of negative feedback, especially feedback coming up from below. The other is a set of implicit beliefs: that employees are self-interested and not to be trusted, that management knows best on almost every question, and that unity and agreement are signs of organizational health while dissent is a problem to be avoided. Those beliefs harden into structure, including centralized decision making, no formal channel for upward feedback, and visible impatience with the person who pushes back.
Employees then read those conditions collectively rather than one by one. Morrison and Milliken call this collective sensemaking, and they argue it converges on two shared beliefs that define a climate of silence: that speaking up about problems is not worth the effort, and that voicing one's opinions and concerns is dangerous. Densely interdependent work speeds the convergence up, because people compare notes more often.
Your Skip-Level Leaders Are in the Room
Detert and Treviño conducted 89 interviews at a multinational technology corporation and found that willingness to voice a concern is shaped by leaders several rungs up, both through direct contact and through the signals that travel down. Employees named skip-level leaders, those two to five levels above them, as reasons to view speaking up as risky or futile nearly as often as they named their immediate boss.
A manager who has done everything correctly in their own one-on-ones can still preside over a quiet team, because the rule was set two levels above them. Fixing your own behavior is necessary and insufficient.
The Manager Half of the Exchange
Employees are only one side of this. Fast, Burris and Bartel published a 2014 study in the Academy of Management Journal on why managers suppress input without intending to.
In their field study, managers with lower self-efficacy, meaning less confidence in their ability to meet the competence expectations of their role, were less likely to solicit input, and less voice reached them as a result. In their experiment, lowering managers' perceived self-efficacy causally decreased their willingness to ask for suggestions, led them to rate employees who spoke up anyway more negatively, and cut how much of that input they went on to implement.
The mechanism they name is ego defensiveness. A manager who feels shaky about their own competence processes a suggestion as a threat and shuts it down, often without registering it. The weeks you most need your team's input are the weeks you are least likely to ask for it.
What to Change
Surface the rules directly. Implicit voice theories are beliefs, which makes them nameable and teachable. Ask your team what the unwritten rules are about when raising something is inappropriate here: which topics, which audiences, which meetings, how far up. You will get answers, and those answers are what you are actually managing.
Audit what the levels above you broadcast. Watch how leaders above you respond in all-hands Q&A, what happens to the person who pushes back in a large forum, and how bad news travels up. Name what you see to your team instead of letting them infer it.
Solicit on a schedule, especially when you feel least competent. The ask disappears exactly when your confidence dips, so put it on a cadence that survives your mood. A standing question in a standing slot beats relying on yourself to remember.
Measure silence separately from voice. Participation counts tell you who spoke and nothing about who decided against it. If you run a diagnostic on a team that has gone quiet, ask about withheld input specifically and work through the underlying causes in order. Distributed teams get fewer ambient chances to correct these beliefs, which is one reason remote communication needs more deliberate structure.
Beliefs Change Through Repetition
These rules got installed by watching what happened to other people over many months, and they come out the same way, through repeated experience of raising something and having it land without cost. Reps overwrite them. An announcement in a team meeting has no comparable effect.
That is the principle QuestWorks is built on. Teams run one 25-minute quest a week on QuestWorks' own cinematic, voice-controlled platform, with Slack or Microsoft Teams handling install, invites, and admin. The whole team plays on the same game day, seated dynamically into groups of three to six, so everyone is making calls under time pressure at once. Inside a quest, correcting a teammate, flagging a bad plan, or arguing for the unpopular option costs nothing, and it happens dozens of times per session. Participation is voluntary and nothing from it feeds performance reviews.
Leaders get a Team Intelligence Score, a 0-100 composite refreshed weekly with an eight-week trend line and named sub-scores including Role Clarity and Decision Velocity, alongside a "Do this week" action list. Pricing is $199 per month per team with 10 seats included, or $1,990 per year. Teams start with a 30-day free trial covering four game days, no credit card required.
The Takeaway
A quiet team is running a belief system, built from specific forecasts about reputation and relationships, reinforced by signals from leaders they rarely meet, and met halfway by managers who stop asking when they feel least sure of themselves. Every one of those is addressable, and none of them respond to being told that this is a safe space.
