Leadership

It’s Not What You Preach, It’s What You Tolerate

by

We had a raider recently who didn’t even realize we’ve been using raid plans the entire season.

Slide numbers were being called out, cooldown assignments had been posted, and key positioning diagrams had been up for every major encounter. Yet somehow, this person (who had been with us for multiple weeks) acted like it was brand new information.

Look, mistakes happen. Miscommunication happens. But this wasn’t a one-off moment of confusion. It was part of a larger pattern.

And it reminded me of a concept from the book Extreme Ownership by Jocko Willink and Leif Babin: the “tortured genius.”

The Problem with “Tortured Geniuses”

This isn’t about someone dealing with mental health challenges or emotional instability. In the context of leadership, a “tortured genius” is the person who’s talented but toxic.

  • They never accept responsibility.
  • They always have an excuse.
  • They point fingers the moment something goes wrong.
  • They’re too good to follow instructions, but never at fault when things break down.
  • And they assume their DPS or logs are enough to justify any lack of accountability.

These players are a trap. They often look good on paper, and they might even be “top performers.” But they are absolutely corrosive to your team if left unchecked.

What You Tolerate Becomes the Standard

One of the most powerful lines in Extreme Ownership is this:

“It’s not what you preach, it’s what you tolerate.”

You can talk about standards all day. You can write raid plans, post cooldown assignments, link guides, and review logs. But none of it means a damn thing if your actions don’t match your words.

If you let someone show up unprepared, ignore instructions, dodge feedback, and stay in the raid team week after week, then that becomes your standard.

The rest of your team sees it. And whether they say something or not, they’re thinking:

Why should I bother putting in the effort if that guy doesn’t have to?

Red Flags: How to Spot the Behaviour Early

Sometimes you don’t realize what’s happening until the damage is done. Here’s what to look for before it gets to that point:

  • They aren’t in Discord for strategy discussions.
  • They never reference or acknowledge raid plans.
  • They need constant reminding of their assignments.
  • They respond to feedback with sarcasm, excuses, or silence.
  • They do well on meters, but that’s where their contribution ends.

If you’re seeing this, you’ve got a “tortured genius” on your hands. And it’s time to deal with it.

How to Handle It (Without Nuking Morale)

Start with a direct 1:1 conversation. Be clear, but not confrontational.

“We’ve noticed a consistent pattern of missed prep and dodged feedback. That’s not going to fly on this team.”

Lay out your expectations: reading plans, owning mistakes, showing up to strategy sessions, and staying engaged with the team. These aren’t optional, they’re the baseline.

If they want to improve, give them the tools. Offer a second chance. Track their behaviour over a week or two. But if nothing changes?

You already know what needs to happen.

Removing a high-output player who’s dragging down team culture is addition by subtraction. You don’t build a CE-calibre team by tolerating passengers with attitudes.

Culture Over Numbers

Cutting someone isn’t about drama or proving a point. It’s about setting the tone.

If you want your team to value preparation, ownership, and collaboration, you have to reinforce that with actions. That means cutting loose the ones who refuse to buy in (even if they can crush a target dummy).

Culture on a team can be fragile. If you let one person ignore the standard, that standard crumbles.

It’s not what you preach. It’s what you tolerate.

Ask yourself the hard question. What are you tolerating right now?

The Mug’zee Pivot: When (and How) to Change Your Raid Strategy Mid-Progression

by

Although we killed Mug’zee last night in Last Call, I wanted to put pen to paper on a strategy change last week that didn’t ultimately work out well for us.

Our raid progression is never linear. It tends to crescendo and decrescendo. Your team strategizes, plans carefully, and yet sometimes the team hits a wall. That’s exactly where we found ourselves recently on Mug’zee.

With a fresh 3% DPS buff for our raid (15%), we saw an opportunity. Maybe we could shake things up, make an aggressive strategic pivot, and secure the kill faster than anticipated.

But the thing about strategic changes is that they’re easy to plan, but a lot trickier to execute.

Strategy Change Fundamentals

Before diving in, let’s cover why you might even consider shifting gears in the middle of progression. Generally, you look at:

  • Significant raid-wide buffs or nerfs (like we received).
  • Roster adjustments (for us, going from 4 healers down to 3).
  • Persistent performance issues or plateaus where your current approach feels stuck.

These pivots aren’t guesses. They’re carefully calculated risks that raid leaders take, hoping for a big payoff (like skipping an entire problematic phase, such as the 3 Gaol set).

Why We Made the Change

The newly implemented 3% DPS buff felt like our window of opportunity. We previously planned for a 4-minute DPS push on Mug’zee. But with the added firepower, a tighter 3-minute push strategy suddenly felt achievable, letting us bypass the notoriously dangerous “third jail set.”

To enable this, we made the call to drop from 4 healers to just 3, adding one more DPS to meet our new aggressive goal. It was bold. But the math checked out (on paper, anyway).

The Reality Check

Initial pulls seemed promising, but reality quickly set in. With one fewer healer, we felt the squeeze immediately. Damage was higher than anticipated, healer mana started running dangerously low, and our throughput suffered. Our mine popping was no longer consistent, and we suffered sporadic deaths.

Despite careful planning, something became clear fast: our margin for error had shrunk drastically. Mechanics we used to comfortably heal through suddenly became critical threats.

What We Learned (And Why It Wasn’t a Mistake)

Did we secure the kill with the new aggressive strategy? No. But we got something valuable: a clear understanding of our actual DPS and healing thresholds. We identified exactly what we needed for the faster push, and it gave us concrete data.

We pivoted back halfway through the night, returning to the safer, original 4-minute strategy, and immediately saw results. Our best pull got Mug’zee down to 0.4%, proving our initial instincts were fundamentally solid.

Timing and Feedback: What Could’ve Gone Better

One notable hiccup: we waited too long to fully engage our healers for their feedback. It wasn’t until our mid-raid break that we stopped to reassess and found ourselves burning valuable raid minutes sorting things out. In hindsight, quick temperature checks after the first few attempts would’ve saved us significant time. We should have asked healers more frequently (maybe every 20 minutes or so). We still needed to give them a few reps to get accustomed to the change in damage coming in.

Early and frequent feedback loops are essential during major strategy shifts.

Raiders Grumbling? That’s Normal (and Okay)

Naturally, not everyone was thrilled. Some raiders grumbled about the mid-raid strategy pivot, suggesting we should never have tried it in the first place. It’s always easy to say that in hindsight, knowing how things played out. But the truth is, strategic adaptability means accepting uncertainty while failing to gain knowledge.

I still stand firmly by our decision to try. There was undeniable value in the potential to skip an entire challenging phase. It felt mathematically possible with 3 healers, but achieving that strategy would’ve required an exceptionally high individual skill ceiling. Realistically, getting there would’ve taken far more pulls and raid hours than we wanted to commit at this stage.

Best Practices for Handling Strategy Pivots

Here’s how you can manage similar situations better:

  • Quick Feedback Loops:
    Check in with key players and roles (especially healers and tanks) after just a few pulls to gauge viability.
  • Clearly Defined “Pivot Indicators”:
    Decide in advance how you’ll measure if the new approach is worth sticking with. Set those benchmarks!
  • Always Have a Backup Plan:
    Know when to switch back decisively.

Final Thoughts: Adaptability is Leadership

Strategic pivots aren’t failures. These leadership decisions are designed to push the team forward, even if they don’t always pan out. We might not have achieved the 3-minute push, but thanks to what we learned, we were able to secure a clean (or dirty) kill using the original strategy.

Raid leadership is about managing calculated risks and adapting quickly. Even if you fall short, you’re still one step closer.

We’re on to Gallywix!

The Secret to a Strong Next Tier? What You Do in the Offseason Matters

by

With the Liberation of Undermine wrapped and Death Jesters locking in the final boss kill, we’ve officially entered the offseason. There is no more boss progression. No more tuning headaches. Just reclears, loot funnels, and a relaxed breathing room.

It has that same feeling as school being let out for the summer, with the empty hallways and lockers being cleared out.

But make no mistake, this isn’t downtime. The work doesn’t stop just because the scoreboard says we’re done. In fact, this is one of the most important phases for raid leadership and team building.

Offseason isn’t where you chill.
It’s where you prepare to win the next tier.

Rotating in Trials and New Players

This is the perfect time to evaluate new players and trial members looking to join a team for the next tier.

During progression, every pull matters. There’s limited room for risk-taking with new trials. But now? We can afford to rotate in new and returning players during farm clears to give them real reps.

We’re watching for more than just logs:

  • How do they prep for raid?
  • Are they communicative and receptive to feedback?
  • Do they ask smart questions?
  • How’s their mechanical execution under farm-level pressure?

We had a situation where one of our players had a bit of uncertainty regarding gate placement on Sprocket. I messed up on Gallywix regarding the timing of taking a gate. Farm bosses give us a stress-free way to test someone. I like to approach it as a pre-season game before the season starts again.

Testing Main Swaps and Class Flexibility

This is also the ideal time for players to experiment.

Maybe your current main isn’t feeling right. Maybe you’re eyeing a class that looks strong heading into the next tier. Maybe someone’s just burnt out on their current toolkit and try something new.

We’re giving players space to test out alternative classes. This isn’t a promise that swaps will be locked in, but it’s a chance to gather data. Try the new spec or class. See if you like it. See how you perform. We were saved on progression when one of our tanks happened to have a serviceable Prot Paladin to help get us through Mug’zee and Gallywix. This is a great time to get up a second character to have in your back pocket in case your main class gets nerfed to the point of unusability next tier.

Whatever you do, be honest (to yourself and to your leaders). Be open to it. If you’re thinking about swapping, don’t wait until week one of the next tier. Let us test, evaluate, and plan now so we’re not scrambling later to replace the raid buff that your class provided (if you were the only one).

End-of-Tier Interviews and Roster Check-Ins

One of the most important things we’re doing is checking in with every raider individually. Although it’s still too early for that, it’s on our to-do list for the summer leading up to the next tier.

These quick end-of-tier conversations give us clarity on:

  • Who’s staying
  • Who might be stepping back or leaving
  • Who’s interested in changing classes or roles
  • Who’s mentally exhausted and needs a break

Rather than waiting for a “surprise” benching or drop-off mid-progression, we’d rather address it now. This kind of transparency helps us plan ahead, set recruitment goals, and adjust expectations.

Keeping Structure Without Burning Out

It sorely tempting to drop down to zero responsibility during the offseason. But total disengagement can backfire. That’s how people drift, motivation drops, and your team rolls into the next tier completely rusty and unprepared.

So we’re keeping a light but structured schedule:

  • Farm clears with rotating rosters (not everyone needs a 3 vault slot in the raid tier section)
  • Optional off-nights for M+ or chill games (Krunker-strike on Discord has been a hit)
  • Shortened raid nights when we’re on our game

The goal is to stay engaged without overloading anyone.

This Is Where Next Tier’s Success Begins

You don’t build a Mythic team during Mythic progression.

You build it between tiers.

The work we put in now pays off when the next raid hits, and we don’t have to waste two weeks rebuilding momentum.

This is our foundation phase. And the stronger we make it, the smoother our next tier is going to be.

So yeah, the final boss is dead.

But the grind?
It never really ends.

Why Accountability Separates Struggling Raids From Successful Ones

by

Let me set the scene.

We’re working on Stix, grinding through progression pulls. It’s one of those nights where every inch of progress feels hard-earned. We’ve got the opening sequence mostly down, but it’s still not quite clean.

During the Sorting mechanic, one of the Scrapmasters doesn’t get picked up. It stays locked onto one of our players before it promptly one-shots them, just like that. Wipe.

Frustrating, but it happens.

I ask, “Who had that zone?”

Silence.

No one admits it.

That, more than the actual mistake, is what annoys me the most. We talk a lot about being a team, being accountable, and supporting each other through progression. But in that moment, no one wanted to own up to it.

And that’s a problem.

Mistakes happen, especially in a fight as chaotic as Stix. But when nobody takes responsibility, it makes progression a whole lot harder. Instead of figuring out what went wrong and moving forward, we’re stuck spinning our wheels, digging through logs, and wondering why no one spoke up.

So, how do we fix that? How do we build a raid team where owning mistakes isn’t seen as a weakness, but a sign of progress?

Why Accountability Matters in a Raid Team

In a raid environment, especially on the road to Cutting Edge, accountability is everything. It’s not just about calling people out; it’s about creating a space where players feel comfortable owning their mistakes, learning from them, and adjusting.

Here’s why it’s so important:

  • Efficiency: Owning mistakes saves time. Instead of combing through logs to figure out who missed an interrupt, we know right away.
  • Team Trust: When players feel safe admitting they messed up, others are more likely to follow suit. It creates an environment where everyone is working toward the same goal—getting the boss down.
  • Growth Mindset: Mistakes are part of learning. If you’re too busy covering up what went wrong, you miss the chance to grow from it.
  • Cohesion: A team that communicates openly about mistakes is more resilient. It’s not about pointing fingers; it’s about learning together.

Why Players Don’t Own Up

It’s easy to say, “Just take responsibility.” But in reality, there are a few reasons why raiders might hesitate:

  • Fear of Judgment or Punishment: No one wants to be the reason for a wipe or feel like they’ll be benched for admitting a mistake.
  • Embarrassment: Some players feel ashamed of making an error, especially in front of 19 other people.
  • Not Realizing They Messed Up: Sometimes it’s not intentional. Players genuinely don’t know it was their fault.
  • Lack of Trust in Leadership: If mistakes are used as ammo to criticize rather than teach, players will stay silent.

As a raid leader, I must set the tone that mistakes aren’t something to hide. They’re something to learn from.

Tools That Reinforce Accountability (Without Making It a Witch Hunt)

We’re lucky to have plenty of tools that help us understand what went wrong during a fight. But how we use those tools makes all the difference.

  • Warcraft Logs: Essential for digging into what actually happened, but not the first tool to whip out like a prosecutor building a case.
  • Warcraft Recorder: Sometimes players don’t know they made a mistake. Reviewing footage clears up confusion and helps them see what went wrong from their own perspective.
  • Individual Check-ins: If someone’s consistently struggling but never admits it, a private message can encourage them to speak up without feeling exposed.
  • Group Debriefs: Focus on general improvements first. Use “we” language instead of “you” to avoid singling anyone out.

How to Encourage Players to Own Mistakes

  1. Lead by Example: If I mess up a callout or make a bad judgment, I admit it. Setting that precedent makes it clear that everyone, including the raid leader, is accountable.
  2. Praise Honesty: When a player speaks up about a mistake, thank them. That positive reinforcement builds the habit.
  3. Private Guidance: For players who might feel shy or worried about public shame, I reach out one-on-one to discuss what happened.
  4. Reframe Mistakes as Learning: Instead of saying “You messed up,” I focus on “Here’s how we can handle this better next time.”
  5. Set Clear Expectations: At the start of progression, I remind the team that it’s okay to make mistakes as long as we’re honest about them.

Handling Genuinely Unaware Mistakes

Sometimes, players genuinely don’t know they were the one who missed a mechanic or misused a cooldown. When that happens:

  • Be Specific: Instead of asking vague questions, point to the exact moment. “Who was in X zone when Y happened?”
  • Show the Replay: Use Warcraft Recorder to clarify the moment without being accusatory.
  • Teach, Don’t Scold: If they didn’t realize it was their fault, it’s a teaching moment. Make it clear it’s about improvement, not blame.

Building a Culture of Preparation, Not Perfection

Accountability is about more than just admitting mistakes. It’s also about building a mindset that values growth over perfection.

As raid leaders, we have to model that change. If we’re transparent, consistent, and patient, it sets the pace for everyone else. Inspire improvement by celebrating small wins—like hitting a new phase, sticking to the raid plan, or seeing consistent progress on mechanics.

If your leaders and core players model accountability, others will follow. You can’t expect players to take ownership if they never see it from the top.

We Didn’t Fail, We Just Learned One More Way Not to Kill the Boss

Creating a culture of accountability takes time. It’s about fostering trust, consistency, and a mindset that treats mistakes as stepping stones.

We have to be relentless about moving forward. That means inspiring improvement and being patient with progression. If we can shift the focus from blame to growth, our team will be stronger for it.

Because in raiding, it’s not about never wiping—it’s about learning how to wipe better each time until the boss finally falls.

How to Handle a Trial That’s Failing (When They’re a Referral)

by

Here’s a situation every raid leader has seen at some point.

One of your best raiders (maybe your top DPS or a senior, long-time player), comes to you and says,

“Hey, my friend is looking for a team. Think we could trial them?”

You trust this player, and they’ve been with you through tiers (or years) of progression. Of course, you say yes. You’re sure their judgment is sound and they’re staking their reputation on them thinking it’ll be a solid fit, right? The new guy goes through the interview process and is able to answer the questions honestly, even if they’re a bit light on recent experience (because they’ve obviously just come back to the game or are trying a new class this time around).

But then the trial starts… and it’s rough.

The friend is average at best. They miss interrupts. They’re out of positions. Their logs are low. Worst of all, their mistakes are holding the raid back from moving forward.

Now you’re in an awkward position.

Do you keep the trial to keep your core player happy?
Or cut them and risk losing both?

Why This Happens All the Time

Raid teams are built on relationships. Referrals are natural. People want to raid with their friends. And most of the time, when a top player vouches for someone, you give them the benefit of the doubt.

But the problem is that being a reliable raider doesn’t automatically make you a good recruiter.

Option 1: Keep the Trial

You value loyalty. You want to avoid drama. And maybe you’re hoping the trial will improve over time.

Pros:

  • Keeps your veterans happy.
  • Avoids an awkward conversation.
  • Buys time for development (if they’re coachable).

Cons:

  • Weak performance continues.
  • The rest of the team starts noticing and asking questions.
  • Resentment builds.

If other players feel like someone’s being carried because of a referral connection, the team’s culture (and possibly trust) takes a hit.

Option 2: Cut the Trial

You have standards to uphold, and you’re on the clock. Performance and chemistry matter. You’re willing to make a hard decision.

Pros:

  • Reinforces your raid’s expectations.
  • Clears up a weak spot.
  • It may actually strengthen team trust long-term.

Cons:

  • You risk losing the original referring player.
  • You might create tension or drama.
  • The veteran player may feel resentful or disappointed.

The leadership dilemma is: Do you value the immediate harmony or long-term standards?

Middle Ground: A Collaborative Fix

Before you swing the axe, try this:

  • Talk to your veteran player first and be honest: “Hey, your buddy’s struggling. I want to be transparent about where they’re at.”
  • Ask if they’ve coached their friend, and if they think the player can realistically improve.
  • Offer the trial an alternate or backup role with a path to earn a position on the roster.
  • Set clear performance goals: “Hit X DPS, avoid Y mechanic, improve interrupts.” Warcraft Logs can help track these metrics on a raid-by-raid basis, and you can measure that progression.

If they meet the bar? Great. If not? Everyone had a fair opportunity, and the squad stays intact.

The Long-Term Cost of Soft Standards

Keeping someone on the team who doesn’t meet the bar (just to avoid losing a better player) might feel like the easier move to make. I can tell you from experience that it rarely works out long-term.

You don’t just risk performance. You risk your identity.

Every raid slot matters if your team is trying to get that CE achievement. Every weak link creates drag.

Make the Hard Call

Leadership means protecting your team’s health, even when it’s uncomfortable.

Be clear. Be consistent. And be fair.

“If one weak link is sinking the boat, it doesn’t matter who brought them aboard.”

Your star player might respect you more for being honest than they would for bending the rules, and giving an exception. And if they don’t?

Then maybe they weren’t the right teammate you thought they were.