Marcus Andrey Study
Ler em português Library

Framework · People leadership · 3 min read

Psychological safety

A shared belief that the team is safe for interpersonal risk-taking. It lets you build a team where people raise problems, admit mistakes and question ideas early.

HighPsychological safetyLow
Comfort zone

High safety, low standards. Pleasant, but nobody is stretched.

e.g. "Looks fine, let's ship it."
Learning zone

High safety, high standards. People speak up, stretch and learn fast.

e.g. "I may be wrong, but this field is missing."
Apathy zone

Low safety, low standards. People do the minimum and stay quiet.

e.g. Nobody asks questions in critique.
Anxiety zone

Low safety, high standards. People work hard but hide problems.

e.g. The data issue appears at handoff.
LowMotivation and accountabilityHigh
Amy Edmondson's safety × accountability matrix: aim for the learning zone, where high safety and high standards meet.

Use it when

  • Your team only shows polished work, and problems surface late, near handoff.
  • Quiet designers rarely speak in critiques or team meetings, and the same two voices decide.
  • Something went wrong in a release and you want the team to learn from it, not hide it.

How to use it

  1. Frame work as learning problems. Say clearly where the uncertainty is: "We don't know yet how operators use bulk edit. We need everyone's eyes on this." Output: a project kick-off that invites questions instead of silence.
  2. Admit your own fallibility. Say "I might be missing something, what do you see?" and mean it. Share one of your own mistakes and what you learned. Output: the team has heard you be wrong out loud.
  3. Respond productively to bad news. When someone raises a problem, thank the messenger first, then ask what they need. Your first reaction teaches more than any team value. Output: people bring problems to you earlier.
  4. Make mistakes discussable. Use retros and short "what we learned" posts, and focus on the system, not on who was at fault. Output: a regular place where mistakes become learning.
  5. Give quiet voices structured space. Use round-robins and written input before discussion, such as 1-2-4-All. Output: every person has spoken before the loudest one decides.
  6. Keep the standards high. Safety without accountability is a comfort zone. Keep clear goals and honest feedback, using Radical Candor. Output: high standards and high safety at the same time.

Worked example

On an internal operations platform, a new UX lead notices that designers never question the product managers' requests. In a retro, she opens with her own mistake: "I approved the export flow without testing it with operators. That's on me." She then asks everyone to write one thing that slowed them down this month, before anyone speaks.

Before After two months
Designers show only finished screens in critique. Two designers bring early sketches each session.
Problems appear at handoff. A designer flags a data issue in week one: "I may be wrong, but this field doesn't exist."
The same two voices decide in team meetings. Written input first; quieter designers' ideas get picked up.

The team health check question "I can raise problems and tough issues" moves up over the next two quarters.

Watch out for

  • Confusing safety with niceness. Avoiding hard feedback to keep people comfortable leads to the comfort zone, not to learning.
  • Punishing the messenger, even slightly. A sigh or "why didn't you tell me earlier?" at bad news teaches people to stay quiet.
  • Saying it, not doing it. "This is a safe space" means nothing if you interrupt or decide alone. Behaviour builds safety, not slogans.
  • Measuring it once. Safety changes with every new person and every incident. Track it over time with a Team health check.

Template

Use this as a monthly self-check before your team meeting.

Month:

This month I...
[ ] framed at least one project as a learning problem
[ ] admitted a mistake or a gap in my knowledge out loud
[ ] thanked someone for bad news before reacting to it
[ ] made one mistake discussable (retro, "what we learned" post)
[ ] used written input or a round-robin so quiet voices got space
[ ] kept a high standard and gave honest feedback

Signals I noticed (who spoke up, who stayed quiet, what surfaced late):

One thing I'll do differently next month:
Source
Amy Edmondson

Books to go deeper

"See on Amazon" links are affiliate links. As an Amazon Associate I earn from qualifying purchases, at no extra cost to you.

Saved only on this device.

↑ ↓ to move · Enter to open · Esc to close