Edmondson and Kerrissey's Harvard Business Review article is useful because it restores precision to a concept that people often flatten into something soft or vague. Amy Edmondson, who originally defined psychological safety through her research on hospital teams, and Michaela J. Kerrissey argue that the term has been misunderstood so widely that it now sometimes produces the opposite of what it was meant to create. When people treat psychological safety as a synonym for "everyone should feel comfortable," they inadvertently build cultures where difficult truths go unsaid and underperformance goes unaddressed.

The strongest contribution is the correction of common myths. Psychological safety does not mean being nice all the time, getting your way, avoiding accountability, or relying on policy alone. It means building an environment where candor, learning, and performance can coexist. The authors are explicit that psychological safety is not about lowering standards. It is about making it safe to be honest about problems so that standards can actually be met. A team where no one raises concerns about a failing project does not have psychological safety. It has silence dressed up as harmony.

The authors identify several specific misconceptions that managers should watch for. One is the belief that psychological safety means consensus, that everyone needs to agree before the team can move forward. In reality, psychological safety is what makes productive disagreement possible. Another misconception is that it is primarily a policy or HR initiative. Edmondson and Kerrissey argue that psychological safety is built through daily behavior, how a manager responds when someone admits a mistake, whether dissenting opinions are engaged with or dismissed, and what happens to the person who raises an uncomfortable truth in a meeting. These micro-moments accumulate into a team climate that either encourages or suppresses honest communication.

For managers, the practical implication is that psychological safety requires active maintenance. It is not something you establish once with a team offsite or a values statement. It is something you demonstrate every time someone takes a risk by speaking up. If a direct report tells you a project is behind schedule and your first response is frustration, you have just taught the team that honesty has a cost. If your first response is curiosity, you have reinforced that raising problems early is valued. They make clear that this pattern, repeated over weeks and months, is what actually builds or erodes psychological safety on a team.

The authors also connect psychological safety to organizational learning. Teams that lack it do not just feel worse. They perform worse over time because they cannot surface errors, adapt to new information, or challenge assumptions that are no longer valid. The concept is not soft. It is a performance driver that operates through the quality of conversation a team is capable of having.

Key ideas to carry into practice

• Psychological safety is about candid contribution, not comfort at all costs. The goal is honesty, not harmony.
• Teams lose learning when they confuse honesty with disloyalty or conflict with failure.
• Accountability and psychological safety reinforce each other when people know they can speak up and still be held to a high standard.
• Better team climate is built through repeated conversations, norms, and rituals, not slogans or one-time events.
• Watch your response when someone delivers bad news or disagrees with you. That moment shapes the team's willingness to be honest next time.
• Psychological safety is not consensus. It is what makes productive disagreement possible without fear of retaliation.