Here I am in the middle of a week, watching Max undergo another reclear before the Diablo 4 expansion was slated to launch. He gets to a part where he’s watching another guild go through their kill of Midnight Falls. But take a listen and watch what happens.
This raid just cleared the entire tier and secured their CE.
Instead of celebrating, players immediately started defending themselves about misplays or other errors.
“Yeah I died there because…”
“That wasn’t my fault…”
“I got screwed by…”
No one really paused to acknowledge the kill. That positive moment just seemed to dissipate and fade out.
The raid went straight into deflection. If you’re seeing this in your raid, it’s not just a one-off behavior. It’s now a team-wide cultural issue.
The Instinct to Defend
This type of behaviour doesn’t come out of nowhere. Players don’t wake up one day and decide to deflect responsibility after a kill. It usually builds up over time for a variety of reasons:
- Fear of being called out: No one likes to be criticized in front of everyone else.
- Fear of losing a raid spot: No one wants to get permanently benched.
- Past experiences with harsh criticism: We’re talking harsh, toxic environments, making the game generally unfun.
- A culture where mistakes are punished instead of being learned from: This can range from being made fun of or teased mercilessly.
So what happens?
Players get conditioned to protect themselves first by justifying what happened or blaming things beyond their control. It happens even in moments where it doesn’t matter anymore (like killing the final boss).
Why This Is a Bigger Problem Than It Looks
At first glance, it might seem harmless. Who cares if someone explains why they died after a kill? We need to take a step back though and re-examine this.
If your team feel the need to immediately justify themselves, it means:
- They don’t feel safe making mistakes
- They assume blame is coming
- They prioritize self-preservation over team success
- They’re mentally stuck in “defense mode” instead of “growth mode”
That has consequences. Teams that operate like this will end with one (or all) of the following:
- They learn slower
- They communicate worse
- They take feedback personally
- They spend more time assigning blame than solving problems
You can’t build a high-performing raid like that, and you end up with a raid team that’s stuck in early or mid mythic without the tools needed to progress past that.
The Missed Opportunity After a Kill
Post-kill moments are important.
They’re when you:
- Reinforce good habits. Highlight positive game play from people and recognize them when they’re correctly done.
- Identify real learning points. Show where people “got it” and spread it to the rest of the team.
- Celebrate progress. The team got a new best (even if it’s a new phase or a lower percentage).
- Reset the team mentally. From despair to excitement.
If your raid immediately turns into a courtroom, you lose all of that.
Instead of:
“Nice job, clean that up the adds next pull, and we can see more.”
You get:
“Let me explain why that wasn’t my fault.”
Now you’ve wasted everyone’s time.
Freedom to Fail Is a Competitive Advantage
One of the things Max mentioned is that they had to actively correct this behaviour early in their guild’s history.
They made it clear:
- It’s okay to die
- It’s okay to mess up
- Not every mistake needs a full breakdown
- If it’s not new or useful, move on
That’s the key. Say it with me!
Not every mistake deserves airtime.
If the team already understands the mechanic and what went wrong, rehashing it doesn’t help. It just slows you down and creates tension. High-end teams don’t obsess over every individual mistake. They focus on patterns and meaningful improvements. I don’t know how long your team raids for, but both of mine only go for six hours a week.
What Your Team Should Actually Be Doing Instead
After a kill, your raid should look more like this:
- Quick acknowledgment of the kill
- Identify one or two real issues if needed (or flag it for next week)
- Move on
That’s it.
Not every death needs a speech, and not every mistake needs a defence.
If it’s something new, sure, call it out and learn from it. Absolutely make it a learning lesson for everyone, especially if someone died in a completely new way or missed a mechanic that’s crucial the first time. Go over it once, and talk about it as a team so they know what to expect and how to handle it if it ultimately does happen again. Certain things are worth drilling and repeating until the team gets it, but that doesn’t apply to all mistakes.
If it is already understood, it is wasting precious raid time.
How to Fix It in Your Own Raid
If you’re seeing this behaviour, it needs to be addressed directly.
1. Set the Expectation
Tell your team clearly:
- You don’t need to defend every mistake
- Not every death needs an explanation
- Focus on team improvement, not individual justification
2. Change What You Reinforce
If you constantly call out individuals harshly, players will naturally start defending themselves.
Instead:
- Focus on solutions
- Keep feedback concise
- Avoid turning every mistake into a lecture
Actually, call out the positives. Talk about what you liked. Name players individually who did something good (even if it’s during the pull), and recognize their effort or moves.
3. Protect the Post-Kill Moment
Don’t let it spiral.
If someone starts going into a long defense after a kill, cut ’em off.
“Doesn’t matter. Boss is dead. We’ll clean it up next time.”
We use Warcraft Recorder to capture our game play. It’s not something that needs to be immediately reviewed and it can be looked at after the raid is over. Celebrate the wins, since that’s the tone you want.
4. Normalize Mistakes
Make it clear that mistakes are expected and understood especially in progression. If players feel like every error is being judged, they’ll always be on edge. The team needs to relax and play loosely when starting out.
And that leads right back to defensive behavior.
If your team kills a boss and the first reaction is panic and justification instead of celebration, something is off. That doesn’t mean your players are bad. It means that the raid culture needs adjustment. The best teams aren’t the ones that never make mistakes. They’re the ones that don’t waste time pretending they didn’t.
I’m fortunate enough that this hasn’t happened in my raids yet. But if my team starts pre-emptively defending themselves before I ask questions, I’ve got my lecture in the back pocket ready to come out. If I were to put money on it, I expect it’d be one of my healers trying to present themselves in a positive light but addressing their own shortcomings right away. My first response is going to be, “I didn’t ask! Simmer down! You goofed, that’s okay, this isn’t a deposition!”