The incident report had a name on it.
Three engineers sat at the table. Their manager opened the post-mortem with the standard framing: “This is a learning exercise, not a blame session.” Then he spent forty minutes systematically naming every decision the engineer on the report had made, with that engineer in the room.
Nobody challenged the framing. Nobody had to. The message landed before the first slide.
What the Room Is Actually Measuring
When someone fails publicly, the rest of the team doesn’t watch to see if justice gets served. They watch to calibrate their own exposure.
The question they’re answering isn’t: “did this person deserve consequences?” The question is: “what happens to people here when something goes wrong?”
One answer produces a team that surfaces problems early, while they’re still fixable. The other produces a team that hides problems until they’re too large to hide. People manage appearances instead of the work. They optimize for not being the name on the next report.
You’ve seen the second version. A standup full of green lights on a project that’s clearly failing. An incident review nobody takes seriously because the real conversation is happening in side channels. A team that doesn’t surface a critical flaw until the release is already in production.
That’s what humiliation builds. Not discipline. Concealment.
The Humiliation Trap
Leaders reach for public humiliation because it feels decisive. It releases tension. It signals that you have standards, that you noticed, that there are consequences here.
All of those things are true.
What’s also true: humiliation names the person, not the behavior. It makes the failure about who someone is rather than what they did. That distinction matters because it’s the difference between information your team can act on and damage your team has to manage.
A behavior is correctable. A person who’s been publicly marked is managed, worked around, and eventually replaced. The team adjusts: this person is a problem. They move on. The behavior that caused the failure is still in the system. Nobody addressed it. They were too busy watching what happened to the person.
Humiliation also misreads the failure. Most failures aren’t character problems. They’re design problems: unclear process, wrong incentive, missing constraint. Treating them as character problems doesn’t fix the design. It just assigns blame and leaves the vulnerability in place.
And the rest of the room updated their priors. The next person who sees a problem developing calculates whether surfacing it early is worth the risk of becoming the name in the next report. One public punishing of the person who brought bad news closes those doors for months.
The framing was “learning exercise.” The lesson was something else entirely.
What Accountability Actually Looks Like
Real accountability is strict. It names what happened, names the behavior, attaches a consequence, and closes.
The differences from humiliation:
It targets the behavior, not the person. “The staging verification was skipped” is accountability. “You were careless” is humiliation.
It’s proportionate: the response matches the actual impact of the failure, not your frustration level or how much tension is in the room.
It happens at the right scope. Private failures get handled privately. Public failures require a public response, but brief. You name what happened, name what changes, and stop. Extended autopsy in front of the team isn’t accountability. It’s performance.
It ends with clarity on what changes: not “do better next time” but the specific step, the person who owns it, and when you’ll check. That’s information a team can act on.
The goal isn’t to make the person feel bad. The goal is to make the behavior visible and the expectation clear. Leaders who confuse those objectives get teams that are very good at appearing accountable while the actual problems drift.
The Script
Here’s what it sounds like when it lands right:
“The deployment broke the integration and it cost three hours of customer downtime. That’s the impact. The staging verification step was skipped: that’s the behavior we’re addressing. Here’s the process change: [specific]. Here’s who owns it: [person]. Here’s when I’ll check: [date]. That’s it. Do you need anything from me to make the fix work?”
Short. Specific. Behavioral. Closed.
No passive-aggressive “remind me why we have a checklist.” No extended autopsy. No lingering. Name the behavior, name the change, move.
If the failure was serious enough to warrant real consequences... a performance plan, removal from a role... those conversations need a private setting, specific language, and the same behavioral focus. “This isn’t working at the level the role requires” is strict accountability. “I can’t believe you let this happen” is humiliation wearing accountability’s clothes.
The outcome of the first: a person who knows where they stand and what has to change. The outcome of the second: someone focused on surviving the room rather than fixing the behavior. And a team that’s quietly recalibrated what information is safe to surface.
After you’ve rebuilt incentive structures and created the conditions for honest reporting, accountability is the moment the system gets tested. The room watched when you changed the metric. They’re watching again now.
Hold the line on behavior. And protect the person’s dignity.
This is part of a series on leadership, silence, and human systems. Previously: Incentives Don’t Lie (They Just Don’t Care). Next: The Leader as Buffer (Revisited).
ZenOne also produces trance and techno music. The mixing arc behind his productions is at zenonemusic.substack.com.