psychological safety
Also called: team psychological safety
A shared belief in a team that it's safe to ask questions, admit mistakes, raise bad news and disagree without being punished or embarrassed. It isn't the same as being nice or lowering standards: teams can have both high safety and high expectations.
Psychological safety is a shared belief in a team that it's safe to take interpersonal risks: to ask a basic question, admit a mistake, raise bad news or disagree with the lead without being punished, mocked or quietly sidelined. It is a property of the team, not of one person's confidence.
It matters because problems travel only as fast as people are willing to mention them. Research on teams in hospitals, factories and software has linked psychological safety with more error reporting, more learning behavior and better performance on uncertain work. In teams without it, the person who notices a bug often stays silent, and silence looks exactly like agreement.
Safety is built by what the lead does every week: framing work as uncertain ("we'll miss things, I want to hear early"), asking by name and in writing so quieter and remote people have a way in, admitting your own mistakes, and responding to bad news with thanks first and the fix second. It is not niceness and not lower standards. The strongest teams have both: high expectations and no fear of saying "I think this is wrong".
Example
In mid-May a family tells Klasna's Support team that their refund looks too small. Olha finds the cause: the refund form has used the 32-lesson package's per-lesson price for every package, so families on 8- and 16-lesson packages got back too little. Then the lead finds a note in a ticket from three weeks earlier: Maryna had written "refund amount looks off?" and left it there.
Three weeks of working days is about 3 × 5 = 15 stand-ups Maryna attended without raising it. The cause isn't her courage. In those stand-ups small problems got "let's take that offline", and a colleague had joked about her as "our edge-case hunter".
What the lead changes:
The bad news goes up to the head of operations the same day: what is known, the impact on families, what Support is doing now, and what it needs.
Common mistakes
- Confusing it with niceness. Safety means people can say hard things; standards stay high.
- Reading silence as agreement. No objections in a meeting may only mean speaking up feels costly.
- Asking "why didn't you tell us?" It sounds like blame, whatever you mean; thank first, then ask what made it hard.
- Leaving jokes at someone's expense. Small put-downs teach the whole team what raising an issue costs.
- Relying on open questions in a call. Ask by name and give a written channel, especially for remote and quieter people.
Learn it in the course
- Bad news up, decisions down · Why a quiet person sits on a problem, what a lead does to make speaking up safe, and how to announce a decision you did not make.