Psychological safety and the experience behind team silence

Look for learning in observable moments

The study draws attention to learning behavior as well as a sense of safety: seeking feedback, discussing errors, sharing information and examining how work is done. Reducing safety to friendliness can leave those practical moments unexplored.

For your team, a useful question might be whether people can reveal where they are stuck and seek help. Recall a recent difficulty. Who knew about it, when did it become discussable, and what happened next? Begin with what you can describe.

Return to one meeting before interpreting the silence

A quiet room can feel like lack of interest when you are carrying the conversation. Yet the reason remains unknown. The question may have arrived suddenly, the decision may have sounded final, or an earlier interaction may still matter to someone.

Revisit one meeting. What exactly did you ask? Was there time to think? What did you say first when a person began to answer? Notice the sequence before explaining what you intended. Then ask someone how they experienced that exchange.

Try changing the first response

When a colleague offers a different view, you might pause before explaining and say, “I would like to understand what you are noticing.” You do not need to agree. The experiment is to understand their information before deciding what to do with it.

If the idea is not adopted, explain the criteria considered and what remains open. At a later conversation, ask how the exchange felt from their side. Follow-through offers another concrete moment to reflect on together.

What HR can explore beyond contribution counts

Alongside asking whether people feel able to speak, invite examples of what happened after they did. Did a concern receive a response? Was an agreed check completed? Did raising the issue leave an unnecessary burden with the person who raised it?

Agree privacy boundaries before gathering examples. Discuss common patterns without asking individuals to defend their feedback. Explore workload, reporting relationships and status as part of the context, rather than placing every condition on the team leader.

Choose a small observation for this week

Choose one question or one response rather than redesigning every meeting. Notice whether you learned something new, delayed your own explanation, or returned with an answer you had promised. Two useful signals are enough for a first reflection.

If the room remains quiet, avoid declaring the experiment a failure. Ask whether advance questions, a written response or a later conversation would offer a more workable way to participate. Let the team help shape the next attempt.

Connecting the research with coaching

A coaching application is to revisit what happens after someone speaks, rather than starting with a target for more contributions. The practical questions below are reflective applications, not additional findings from the study.

What to keep in view

This was a field study in one company. Its associations should not be treated as universal causal effects or as evidence for a particular coaching program. Use the perspective to investigate the experience of your own team.