liveBook · Manning

Psychological safety

As explained in 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.

An engineer is struggling with a service codebase and has missed a project milestone. Can they say what went wrong in a one-on-one without fearing reprisal? Psychological safety means people can take interpersonal risks—such as raising a concern, admitting a mistake, or sharing a different perspective—without fear of reprisal. For an engineering manager, it is a foundation for trust, open communication, and inclusion. section 4.2.1 section 3.2.6

Build that environment through everyday management habits:

  • Listen patiently in one-on-ones and team meetings. Ask about people’s goals, expertise, and challenges, and invite feedback through surveys when another channel would help everyone have a voice. section 3.2.3
  • Address bad behavior promptly and apply expectations consistently. Lead by example, encourage knowledge sharing, and treat mistakes as opportunities to solve problems constructively. section 3.2.3
  • Be clear about mission, goals, expectations, project updates, and obstacles. Give development feedback in one-on-ones, while protecting sensitive information and feedback sources. section 3.2.3 section 4.2.1
  • Show accommodation and empathy for different circumstances. Inclusion efforts can help people understand perspectives unlike their own, but they require ongoing practice beyond programs or policy documents. section 7.5.3

When a milestone is missed

In a one-on-one, a manager shares difficult peer feedback and makes room for the engineer to explain their struggle with the codebase. They agree on training, mentoring, and a gap analysis, while temporarily adding project support. A safe discussion does not erase the missed deadline or the need to improve; it helps reveal the problem and makes a response possible. section 3.2.6

Psychological safety also matters when a teammate faces a personal tragedy during a critical project. Invite them to express what support they need, prioritize their well-being, and plan for possible schedule changes. Be candid with stakeholders about the project impact without making the teammate’s circumstances a reason to withdraw support. section 1.1.3

Safety is not a promise to disclose everything or avoid hard conversations. Share information the team needs, protect sensitive details, and deliver clear feedback. The practical check is whether people can speak honestly—and whether their manager responds fairly and constructively. section 3.2.3 section 4.2.1

How Think Like a Software Engineering Manager covers it

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 it assumes
Introduces psychological safety in plain workplace terms while assuming responsibility for team communication and employee support.
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.
How it connects
Connects psychological safety to trust, transparency, performance feedback, inclusion, and learning from mistakes.
Cover of Think Like a Software Engineering Manager
liveBookmanning.com
Read Think Like a Software Engineering Manager on liveBook Get the book at manning.com

Also explained in

Compare how 3 books explain psychological safety →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Think Like a Software Engineering Manager. The section links point to the parts of the book it draws on.