Psychological Safety is not Impunity

Дата публикации: 17-09-2026 22:00:00

You can find him in the retro, though he rarely says much. He doesn't need to. The team has learned to write around him. Watch what happens to a good idea in this room. Someone proposes a real improvement, and before it's even finished, you can see a couple of people glance, just slightly, toward the corner where he sits. The idea gets softened. Then shelved "for now," because everyone already knows he'll sink it, loudly and personally and for the rest of the afternoon, and nobody has the energy for that today. He has never been given a scrap of authority. He runs the team completely. Every agreement it makes is shaped, in advance, around the question of what he'll tolerate. The team would tell you it values inclusion. What it has actually built is a hostage situation with snacks. This is the thirteenth of the Wizard's Rules, and it's the one agile culture is least comfortable hearing. Like the last one, it's a later Rule, confirmed by the old wizard but never given a number: "There have always been those who hate, and there always will be." Read carelessly, that sounds bleak, or worse, like permission to call everyone who disagrees with you a hater. It's neither. It's a piece of realism most agile thinking quietly refuses. The rule's own teaching is that hate is a permanent feature of people, not a bug you can patch. You will not retrain it away with a better workshop. And you cannot crush it out of someone by force, punishment, or exile, because those only feed it. The one thing that ever works against it is truth and care, held with a spine. Anything else fails, or makes it stronger. That last part is where agile teams get into trouble, because they hear "truth and care" and drop the spine.Skepticism is signal. Sabotage is not feedback.Here's the distinction the rule forces, and the one open cultures resist hardest: not all resistance is the same thing, and running it all through the same inbox is exactly how the worst of it wins. Most resistance is a gift. The critic who picks your idea apart is testing it, and a tested idea is a stronger idea. The colleague who digs in their heels is often a protector, someone who has seen real damage before and is trying to prevent another round of it. Both of those carry signal. You want them. A team with no critics isn't safe; it's just quiet. But some resistance isn't testing the idea or guarding against harm. It's there to make the work fail, to drain the energy out of the room. That isn't feedback. Treating it as feedback, giving it the same patient airtime, the same "let's understand your concern," is not inclusion. It's just surrender. Call it the worst-actor veto. The unspoken authority a single destructive person accumulates over a team that has decided it isn't allowed to set a boundary. Nobody voted for it. It builds quietly, one softened agreement at a time, until the whole team's behavior is organized around one person who never has to say what he wants, because everyone is already managing what he won't have.Where openness curdles, and what it costsIt shows up in three confusions, and each one quietly trades a fundamental away. There's the team that designs every agreement around its worst member. The norms get written not for the people who want to do good work, but to avoid provoking the one who doesn't. That team has handed its Decision Mandate, its authority over how it works, to a person it would never consciously put in charge. The saboteur didn't take the team's decisions. The team gave them away, to keep the peace. There's "psychological safety" stretched until it means impunity. Safety was supposed to mean people can speak the truth without being punished for it. Somewhere it got bent into "no one faces a consequence for anything," including for the behavior that makes everyone else unsafe. And that's the irony that bites: unlimited tolerance for the harmful person destroys Trust and Candor for everyone else, because the honest people go quiet the moment they learn the bully has a permanent free pass. Protecting the worst actor is how you lose the very safety you thought you were defending. And there's the team that treats every objection as equally valid, and so can't act on any of them. It can't tell the cynic who might be right from the saboteur who wants the thing to burn, so it either starts punishing useful criticism or romanticizes destruction as "just how he engages." Either way, Outcome Ownership goes, because a team that can't separate signal from sabotage can't own a result. It's too busy negotiating with the person who'd prefer there wasn't one.Four signs the worst actor is running the team1. One person can derail any improvement, forever, without ever proposing a better one. Blocking is the whole contribution. There's never an alternative on the table, only the veto. 2. Agreements get softened before they're even proposed. Someone says "[name] will never accept that," and the idea quietly shrinks to fit. The boundary is being set by the person who should be inside it. 3. People avoid useful topics because they know how it'll go. The real conversation doesn't happen, not because it's unsafe in general, but because it's unsafe near one specific person, and everyone has mapped exactly where the landmines are. 4. Leadership asks the team to be patient, and never protects it. The team is told to keep extending grace to repeated harm, while no one with authority ever sets the limit. Coaching the harmed to be more understanding is not the same as addressing the harm.One move: sort the resistance before you answer itThe next time you hit resistance, don't ask whether it's positive or negative. Ask what kind it is, because the right response to each is different. If it's a critic testing the idea, invite the evidence and use the signal. If it's a protector who fears real damage, explore the concern and reduce the risk. If it's a saboteur, blocking movement and going after people, then set the boundary, take back the veto, and escalate it if it doesn't stop. The whole discipline fits in two sentences. Don't punish criticism. Don't romanticize sabotage. The counteraction to the Thirteenth Rule is to set the boundary the team has been too afraid to set, and to set it from care for the work rather than hatred of the person. That distinction is the entire thing, and it's why this Rule and the Eleventh are two halves of one discipline. The Eleventh Rule was embrace life, seek strength without hate: don't let your strength curdle into contempt for people. This one warns you not to let your care curdle into helplessness in front of them. The boundary you set isn't the force the rule says always fails, the punishment, the campaign to crush someone. It's the opposite. It restores the team's Decision Mandate over its own norms, it makes Trust and Candor real by protecting the honest instead of the harmful, and it lets the team own its Outcome again. You protect the people doing the work. You do it without hating the one who isn't. Before you extend patience one more time, ask one question. What's the last agreement this team made that it would have made differently if one specific person weren't in the room? If you can name it instantly, that person is running the team, and nobody ever gave them the job. They just took the seat you were all too careful to defend. The Rule doesn't care whether you believe it. That's what makes it a Rule. Take this Rule into your next team agreement and ask: are we writing this for the people who want the work to succeed, or around the one person who doesn't? If this Rule cut close, pass the blade on. Share.
Welcoming your comments on this!
Don't want to miss any of these articles? Have the “Fundamentals before Frameworks” series in your mailbox.Wishing you an inspiring read and a wonderful journey.Scrum on!



Image

Схожие новости

#	Наименование новости	Тональность	Информативность	Дата публикации
1	The Real Meeting Happens in the Hallway	0	7.52	15-09-2026
2	Reality Doesn't Need Your Permission to Escalate	0	5.48	10-09-2026
3	Your Retro is a Support Group, Not an Engine.	0	8.63	08-09-2026
4	You Can't Choose the System. You Choose How You Act Inside It.	0	5.62	24-09-2026
5	Nobody Owns Whether it Worked.	0	8.63	29-09-2026
6	Your Team Isn't Slow. Your Handoffs Are.	0	8.51	22-09-2026
7	TEAMWORK: From the Individual Lens to the Collective Lens	0	8.82	14-09-2026
8	Scrum's Protocol Is Easy to Copy. Its Agenda Is Not.	0	14.4	27-09-2026
9	5 Things the Product Owner Shouldn’t Be Doing	0	16.4	29-09-2026
10	Cognitive Trap: Planning Certainty	0	8.36	21-09-2026

Классификация: . Схожих патентов: 0. Схожих новостей: 10. Тональность: 0. Информативность: 6.08. Источник: www.scrum.org.