Speaking-up anxiety

What it really means

Speaking-up anxiety is not just nervousness about public speaking; it is a specific social risk calculation. Employees weigh possible outcomes (being ignored, laughed at, penalised, or labelled a troublemaker) against the perceived benefit of speaking. That perceived risk shows up even when content is important, leading teams to lose access to frontline knowledge.

How it appears in everyday work

• Hesitant contributions: employees preface comments with disclaimers (“I might be wrong, but…”).
• Delayed input: useful ideas arrive only after private messages or in 1:1s, not in meetings.
• Over-reliance on elites: only senior or confident voices dominate discussions.
• Silent meetings: low participation despite high stakes or clear gaps in knowledge.
• Post-meeting regrets: people later say “I should have said something” in private.

These signals are subtle and frequent. Individually they may look like politeness or caution; together they form a pattern that erodes decision quality. Tracking where ideas originate (meetings vs. 1:1s) can reveal a speaking-up gap.

Where leaders commonly misread silence

Managers often interpret silence as agreement, apathy, or incompetence. Those are easy but risky conclusions:

• Interpreting silence as agreement can lock in poor decisions because dissent never surfaces.
• Treating low participation as disengagement may lead to tighter controls that further suppress voice.
• Confusing reserved personality (introversion) with speaking-up anxiety misses the social risk element—introverts may speak up when the context feels safe.

Related concepts worth separating from speaking-up anxiety include:

• Psychological safety: a team property that makes speaking easier; low psychological safety is a common cause but not identical to an individual's anxiety.
• Impostor feelings: internal doubts about competence that can reduce willingness to speak, yet impostorism focuses on self-evaluation while speaking-up anxiety emphasises perceived external costs.

Leaders who conflate these concepts choose the wrong remedies (for example, public pep talks for an issue that requires structural change).

A product team holds weekly demos. A junior developer notices a security gap but says nothing during the demo. Afterward she tells a peer in a private message. The peer raises the issue in the next retro; the team decides to ignore it because it looks low priority. Two weeks later the bug causes a customer outage.

A different managerial response: at the next demo the manager explicitly invites concerns and explains there will be no penalty for raising problems. She also creates a short anonymous reporting channel for technical risks. The junior dev reports the issue; the team patches it the same day. The concrete change—public invitation + anonymous channel—reduced the activation energy for speaking.

Practical first steps managers can take

• Model the behavior: share your own doubts and near-miss stories first.
• Normalize small disclosures: make short, routine prompts part of meetings (e.g., “What could go wrong?”).
• Create low-cost channels: anonymous forms, short pre-meeting written prompts, or safe offline check-ins.
• Set explicit norms: define what respectful dissent looks like and how it will be handled.
• Train for response: teach leaders to thank, probe, and separate critique of ideas from critique of people.
• Measure distribution of input: track who speaks, in what forums, and where ideas originate.

Start with low-friction actions that change expectations (modeling, explicit invite). Measurement and norms make those behavior changes stick by signalling the organisation will respond differently.

What makes speaking-up anxiety worse — and what to avoid

• Public dismissal or sarcastic responses that teach people staying silent is safer.
• Zero-tolerance reactions to mistakes that turn any suggestion into a personal risk.
• Overemphasis on speed and flawless execution without structured learning rituals.

Avoid quick fixes like blaming individuals for not speaking. Instead, treat silence as a signal about process and context. Changing response patterns is more effective than exhortation.

Questions leaders should ask before reacting

• Who benefits from the current decision-making rhythm, and who pays the costs of silence?
• Are there recurring issues that only surface in private channels?
• Which forums are safe for which kinds of input, and who owns each forum’s norms?

These questions help move from attributing motives to diagnosing structural contributors so interventions target the root causes.

Where to focus measurement and follow-up

Track: source of ideas (meetings vs. 1:1 vs. anonymous), participation spread across levels, and outcomes of raised concerns (addressed vs. ignored). Small experiments—like changing an agenda prompt or piloting anonymous reports—let you test what reduces anxiety without large investment.

If silence feels systemic, begin with clear, observable changes: leader modeling, a prompt on every agenda, and a low-friction reporting mechanism. Monitor whether more issues are raised and whether they are acknowledged and acted upon.