What it is, and what it is not
Psychological safety is the shared belief that you can raise problems, admit mistakes and challenge the plan without being punished for it. It is not comfort, and it is not lowered standards: the highest-performing teams pair high safety with high expectations. Without it, your weekly signals turn green regardless of reality, because reporting bad news costs more than hiding it.
Leader behaviours that build it
- Respond to bad news as information, visibly and consistently. The first person punished for honesty is the last honest report you get.
- Ask for challenge explicitly, and reward the person who provides it.
- Admit your own uncertainty and mistakes; calibrated confidence is contagious.
- Frame work as learning: experiments, check-ins and retrospectives all assume some bets will not land.
Safety is the precondition for everything else in this track: honest check-ins, real target commitment and change that people engage with rather than endure.
The methodology connection
Safety is not a soft topic in a goal system; it is load-bearing infrastructure. Honest confidence scores are the earliest warning system a leadership team has, and they only stay honest where reporting Low costs nothing. Aspirational targets only produce ambition where a well-reasoned miss is genuinely safe to own in the retrospective. And the culture that makes both true is built retail, in specific recurring moments, by what leaders visibly do when bad news arrives, leader behaviour is the signal and culture change is retail working together. The first person punished for honesty is the last honest report you get, and everything downstream of that, targets, check-ins, learning speed, inherits the damage.
Credited to Edmondson, built by mechanism
The concept is Amy Edmondson's; we cite her plainly rather than quietly borrowing the idea. Her research at Harvard established that the teams reporting the most errors were not the worst teams but the safest ones, the only teams where errors surfaced at all. Where we add something is the how. Safety is usually treated as a climate you exhort leaders to create, which is why most advice on it evaporates. We treat it as something a system manufactures in specific recurring moments. Two mechanisms do most of the work: weekly confidence check-ins, where reporting Low is routine and consequence-free, so the admission muscle is exercised every week rather than saved for a crisis; and graded, not scored, retrospectives, where a well-reasoned miss can grade Excellent and a sandbagged hit can grade Poor. Score a team on a percentage and it learns to manage the percentage; grade its reasoning and it tells you the truth. Safety stops being a poster and becomes a property of how the quarter is run.
One line to keep: Safety is not a climate you exhort; it is a property a system manufactures, one honest check-in at a time.