Researcher Amy Edmondson defined team psychological safety as a shared belief held by members that the team is safe for interpersonal risk-taking: people can ask, disagree or admit a mistake without expecting embarrassment or rejection. In her study of 51 work teams at a manufacturing company, psychological safety was associated with learning behaviours such as seeking feedback, discussing errors and experimenting, and those behaviours were in turn associated with team performance. ^[1]

The study is also clear about what the concept is not: it is not permissiveness, not a relentlessly positive mood and not simply cohesion. Indeed, strong cohesion can reduce willingness to disagree, as in groupthink. ^[1] So a psychologically safe team is not one without disagreement, but one where disagreement surfaces early and usefully.

Google’s internal research on team effectiveness, covering 180 teams, put psychological safety first among five dynamics that set effective teams apart, followed by dependability, structure and clarity, meaning, and impact. ^[2]

Why do employees stay silent even when they see the problem?

CIPD explains that employees may stay silent when they judge that the risks of speaking up outweigh the benefits, and that power dynamics strongly affect whether people speak. ^[3] Employees do not work out those risks from the written policy, but from what they have seen happen to colleagues: who flagged an error and was thanked, and who flagged one and was accused of obstructing the work.

Many Gulf teams combine factors that make this calculation more sensitive: marked differences in seniority and grade, a mix of nationalities and communication styles, and new joiners who do not yet know where the limits of acceptable speech lie. That is why saying “my door is open” is not enough; the team needs to see what actually happens when someone knocks.

Bear in mind that silence does not show up in reports. A team that raises no problems can look stable and disciplined while small errors accumulate until they surface all at once in front of a customer or a regulator. So a leader needs to go looking for the missing voices rather than waiting for them to arrive.

What does a leader do on hearing bad news?

The first piece of bad news you receive after asking the team for candour is a test of everything you have said. How you respond in the first few minutes teaches the team more than any awareness campaign.

Some details that make the difference:

• Separate the message from the messenger: discuss the problem and the evidence, not the timing of the report or the reporter’s rank.
• Do not make a solution a condition of reporting: “don’t bring me a problem without a solution” makes people delay the warning until they have one, by which time it may be too late.
• Keep the routes distinct: an objection to a work decision is handled within the team, whereas a report of misconduct or inappropriate behaviour goes to the route set out in your organisation’s policy, with the available limits of confidentiality explained.

CIPD recommends a speak-up policy that offers confidentiality and protection from penalty for raising concerns, and training managers to handle sensitive conversations with confidence. ^[3]

How do you open space for dissent before the decision, not after?

Many objections arrive after implementation because the team found no suitable moment before it. One practical tool is the “premortem” described by Gary Klein in Harvard Business Review: the team assumes the project has just failed and generates plausible reasons for its failure. Klein argues that this lets people with reservations speak freely at the outset, so the project is improved rather than autopsied. ^[4] In practice, asking each member to write their reasons down individually before the group discussion helps the quieter and more junior members contribute.

Add some simple habits: explicitly ask for the opposing view before stating your own, give thinking time and a written channel for those who prefer not to speak in the meeting, and let the most junior people speak first in risk discussions.

Phrases a leader can use instead of “Any objections?”

“Any objections?” at the end of a meeting is usually met with silence, because it sets the objector against the group. More specific prompts work better:

• “What is the weakest point in this plan, in your view?”
• “If this failed three months from now, what would the likeliest reason be?”
• “What do we not know yet that could change the decision?”
• “Who can see this from the customer’s or the remote branch’s point of view?”

When the leader admits a mistake of their own, or something they do not know, it sends the team a practical signal that this is acceptable. Edmondson’s study found that team leader coaching and context support were linked to learning behaviour through psychological safety. ^[1]

Hypothetical example

A recent joiner to a technical team objected to the readiness of an online service launch because the login test had not covered users at one of the branches. Instead of questioning his experience or the timing of his objection, the manager asked for that group to be retested within two days and named who would verify the result. He then shared the test outcome, the launch decision and the reason with the team. The point was not whether the employee was right, but that the team saw a route it could reuse for the next objection.

Psychological safety does not mean lower standards

Some managers worry that encouraging people to speak will slide into tolerance of poor performance. Yet Edmondson’s own study rejects reading psychological safety as permissiveness. ^[1] In practice, the team is held to account for conduct and results under fair, fact-based rules, while nobody is penalised for raising a problem or admitting a professional mistake in good faith.

Clarity of roles is part of the equation. Google’s research lists structure and clarity among the five dynamics: every member knows what is expected and how to deliver it. ^[2] A team that does not know its working standards cannot say when the work has drifted from them.

How do you track the practice without fooling yourself with numbers?

Ask the team regularly, through a short survey or in one-to-ones, how easy it is to raise concerns, admit mistakes and ask for help. The questions can be simple statements rated on a scale of 1 to 5:

• I can raise a problem or a dissenting view in this team without it being held against me.
• If I make a mistake at work, it is treated as a chance to learn.
• It is easy to ask my colleagues for help.
• When I flag a problem, I find out what happened next.

Alongside that, review operational indicators: how long feedback took to answer, how much of it was closed with a clear action, and whether the same issue recurred.

Be careful when reading report counts. A rise may mean people are more willing to speak, or that problems really have increased; a fall may mean improvement, or silence. So examine content and context before drawing conclusions, and combine more than one channel, as CIPD recommends. ^[3]

Conclusion

Psychological safety is not declared in a memo; it is built from a leader’s repeated responses to bad news and dissent. Thank the person who flags the problem, verify with evidence, close the loop in front of the team, and keep working standards clear and fair.