liveBook · Manning

Psychological safety

Psychological safety is a belief or condition in which people feel able to speak up, ask questions, disagree, contribute, and take interpersonal risks without fear of humiliation or punishment.

How 3 Manning books explain it

Think Like a Software Engineering Manager

A psychologically safe workplace is an environment where people can express perspectives, concerns, and ideas without fear of interpersonal punishment or humiliation.

How it is used
Supports engineering managers in building trust, inviting honest communication, and handling performance concerns without silencing employees.
How deep it goes
Defines interpersonal risk without reprisal and gives management practices and scenarios, rather than a formal measurement method.
Examples
Uses a missed project milestone, a teammate’s personal tragedy, and inclusion initiatives to show safety in different situations.
What you can do after
Practice/perform safer one-on-ones, candid feedback, consistent responses to bad behavior, and supportive planning when employees face difficulties.

Read how Think Like a Software Engineering Manager explains psychological safety →

Collaborative Software Design: How to facilitate domain modeling decisions

Psychological safety is a shared belief that people can speak openly, take interpersonal risks, and address difficult issues without undue fear of negative consequences.

How it is used
Protects participation during collaborative modeling, especially when groups confront conflict, bias, competing perspectives, or difficult concerns.
How deep it goes
Defines safety boundaries and gives facilitation practices, but stops short of a comprehensive intervention framework for every group dynamic.
Examples
Uses divergent visions, named alternative models, different communication styles, mistakes, emotional expression, and withheld advice as examples.
What you can do after
Apply it via neutral facilitation, active listening, delayed advice, and modeling multiple perspectives during collaborative sessions.

Read how Collaborative Software Design: How to facilitate domain modeling decisions explains psychological safety →

"Looks Good to Me"

A team condition in which people feel safe to ask questions, seek clarification, and contribute ideas without fear of negative consequences.

How it is used
Uses psychological safety to encourage clarification, help-seeking, and contribution before issues become code-review problems.
How deep it goes
Explains causes, preventive practices, and inclusive communication options without presenting measurement methods or formal assessment.
Examples
Uses misunderstood requirements, hidden bugs, clarification requests, and meeting, chat, written, and one-on-one contributions.
What you can do after
Apply it by establishing clarification norms, discussing features, defining acceptance criteria, and offering varied ways to contribute.

Read how "Looks Good to Me" explains psychological safety →

Related concepts

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.