Conflict Resolution

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.

The Art of the Post-Raid Debrief

by
The other day, I was chatting with one of the other raid leaders from a different team in our community. We got onto the topic of raid feedback after the raid ends.

Their team uses a system where they post individual debrief threads in Discord sorted by date. People dig into logs, break down their performance, and share what they’ve learned or where they messed up. It’s super detailed, and honestly, it works for them. Especially for the log-savvy folks who live in Warcraft Logs and can extract key information from a night.

Our approach in Last Call is a little different.

We keep it mostly team-focused. When we review fights, we share insights with the whole squad. Once in a while, if there’s something that needs to be addressed, such as a key mechanic someone consistently missed, we’ll mention it if it’s a learning point for everyone. We don’t want to turn our review into a firing squad. The point isn’t to shame people on their class rotation or anything. If I missed one Ancestral Swiftness, that’s not really going to move the needle (but I’m still going to file that information away because I could’ve played that Shaman better).

It’s to improve as a group.

Debriefing After Stix: A Real Example

Let me give you a recent case. We were working on Stix, and during our post-raid breakdown, we pulled a bunch of things out of the logs:

  • Defensive cooldown usage: Who popped a defensive when they were supposed to? Who forgot? Who panicked and overlapped three cooldowns on the same hit?
  • Trash ball behaviour: Did players avoid the crab shells? Did they accidentally miss a Scrapmaster and turn into a small ball instead of a medium or large one? Every little bit of damage helps on Stix, and that includes how well you manage those ball mechanics.
  • Interrupts: This is huge. Did we have full coverage on Scrapmasters?

Even on wipes, every pull gives you data. And the more you learn from that data, the faster you kill the boss. We shared a table with player information that showed who missed Scrapmasters or rolled into Bombshells. In this situation, we had to spotlight players who were making errors. Either they weren’t seeing information, or they weren’t responding to it and these are both things we have to correct one by one. Over time, the team did improve as a whole, and the number of mistakes went down as everyone became more familiar with what to look for and what to avoid. Without having waded into the weeds of the information, we would not have realized that the Scrapmaster in the Purple Diamond section (the one near the wall) was the one that frequently got overlooked.

Our coaching point then was if you are assigned diamond, specifically look for the Scrapmaster that’s near the wall because chances are you balled right by it or it happens to blend in with the wall that it’s just missed.

The Debrief Toolkit: What We Look For

Here’s what we usually include in our team debriefs:

  • Positioning: Anyone consistently getting hit by frontals or mechanics they should’ve dodged?
  • Cooldown assignments: Were healing CDs used where they were planned? Were any wasted? Was anyone holding a CD too long out of fear? The flipside holds true as maybe we used a raid wide ability somewhere that didn’t warrant it.
  • DPS optimization: Were people using potions and cooldowns on time? Did they get value out of their major windows? Are they targeting the right ads including Scrapmasters?
  • Death analysis: Were deaths avoidable? Did they come from mechanics, poor healing coverage, or missed externals?

You don’t have to go full detective mode. Even picking two or three key points per night can make a big difference.

Tools We Use

  • Warcraft Logs: The core of any good debrief. Parses, cooldown usage, deaths, damage taken—you name it.
  • Viscerio’s Combat Replay: Great for showing positional data and understanding how the raid moved during a fight.
  • Method Raid Tools Logs: Super helpful for tracking planned cooldowns vs. actual usage.
  • Warcraft Recorder: This one’s a game-changer if you’re not already using it. It captures in-game footage automatically, making it easy to review exact moments, callouts, and spatial awareness issues. Bonus: It’s great for training, clip sharing, or spotting issues that don’t show up in logs.

Tone Matters More Than You Think

If there’s one thing I’ve learned as a raid leader, it’s that tone makes or breaks your debriefs.

You could have the most accurate breakdown in the world, but if it comes across like a scolding session, no one’s going to internalize it. Worse, they’ll tune out or even resent it.

We try to keep things constructive. We highlight the good stuff. “Great use of Pain Suppression on that 2nd phase soak.” “We handled the adds way better this pull.” Stuff like that. Wins get celebrated just as much as fails get analyzed.

Final Thoughts

A raid doesn’t end when the boss dies or wipes your raid group. It ends when you understand why it went the way it did.

Debriefs help bridge the gap between one raid night and the next. They’re how you carry lessons forward. And the better your team reviews together, the stronger you’ll be on the next pull.

Start small. Pick one fight. Pick one thing. Talk about it. You might be surprised how much smoother your next raid night goes.

How Safe is your Guild Bank from Social Players?

by

Imagine my surprise when I received a note from a fellow on the same server one lovely morning. One of my players was accused of stealing loot from a different guild’s bank and before promptly quitting.  The accused’s alt just helped themselves to various items. I’m not actually sure what items were taken or what the full value was.

Most GMs are bound to deal with guild bank thefts at some point in their careers. Either their bank gets stuff stolen from or a different guild’s bank gets raided (via alts) and they’re left dealing with the offenders.

In a fair number of cases, the accused would’ve simply been kicked out. And I’ll be the first to admit, it’s the easiest solution. You kick the player and your hands are washed of having to deal with them ever again. Your guild’s reputation is left (relatively) intact.

I responded back to the accuser saying that I’d look into it. But this is a player I didn’t have much interaction with as they were on our PvP roster. In the end, I notified my PvP team leader about this because the player was under their division.

“One of our players was accused of this. Any ideas about them? Here’s the guild they were in and here’s the character of the accuser.”

What happened?

Apparently, it was a misunderstanding. Our guy mistakenly took things that they weren’t supposed to thinking that it was open and free to anyone. They returned the goods (and compensated accordingly). As it’s their first time offense, I have to assume that there was no malicious intent (and there’s no evidence to show that there was).

As the player

Before taking stuff, ask.

Or at least, check around and see if there’s a banking policy. There may be certain limitations based on ranks. Sometimes the GM makes a mistake and places you in the wrong rank and you’re not actually supposed to be entitled to certain tabs. If you have access to rare items like enchants, recipes, or other craftables, it’s a good idea to check with someone higher up before helping yourself to it.

As the GM

Lock down your stuff.

Check the permissions.

Check the rank access of the permissions.

Make sure the right people have access to the right tabs. You have a responsibility to ensure that. It’s noble to assume the best out of everyone but it’s also quite foolish to leave the door to the vault wide open and expect it to be respected. Have your bank rules outlined somewhere on your guild website or your forums. Go over the ground rules with all new recruits with regards to withdrawal policies.

Speaking of banking stuff, which one of you left these stacks of Wool Cloth and Volatile Earth’s in my guild bank?

Question: Deciding Upon Disagreements

by

Have you ever been dragged into a discussion between two players? You’re being asked for your opinion or to side with someone, but you just can’t really bring it in you to actually care about it.

Other than flipping a coin, how would you decide and resolve a disagreement when you just don’t give a damn?

“Seriously? You’re asking me to decide which one’s better and could take on the other? Star Trek or Star Wars?”

How to Get What You Want From Your Guild

by

See that image up there? That is one annoyed looking cat. Looks as if someone took away his toy or threatened him with a bath. That’s the same look I exhibit when someone comes complaining to me.

But hey, it comes with the guild leader territory.

Listening to complaints. It probably takes up around 15% of communications.

(Actually, file that post idea away. “Percentage of matters that occupy guild leader time”). 

Most of the time, it’s just hot hair or someone wants to get something off their chest. Generally, complainers aren’t really taken seriously. But y’know? Every so often, there’s a legitimately dissatisfied player.

If you really want to lodge a solid complaint, you need to identify if what you want is an actual change or you just want to vent.

Too often in guilds, players are exposed to people complaining about something.

Maybe it’s someone’s performance.

It could be their lack of attendance.

Perhaps the raid just takes too long to get going.

You know, if you’re looking to secure some kind of change in policy or the way things are done, then effective complaining is called for. If it’s for the second reason (emotional comfort), then really, all you’re looking for is someone to listen to you.

My advice? If you’re going to complain because you want something done differently, figure out exactly what your end game is. The most ineffective complaint is the one where there’s no objective.

What is the end result of your complaint?

Here’s some examples:

  • Consistent faster pulls
  • Less off-topic discussion during raid
  • More booze during break

Once you figure out the outcome, identify the person capable of delivering it. You don’t harass the Warrior if you don’t have any food or water, right?
If I’m on the receiving end of a complaint, I instinctively put up walls because I know what’s coming. Being conscious of this, when I’m lodging a complaint to others (a legitimate one, mind you), I make an effort to be calm and polite.*

Ask yourself this.

Are you looking for results or the satisfaction of being right?

* My friends have picked up on this. When they notice I‘m super extra nice, they immediately get suspicious.

When following through with your complaint, start off with a cushion. This is a statement that prevents your target from feeling that they’re being attacked. Follow it up the meat and potatoes which contains the concern that you want resolved. Then finalize it with a statement proving that you’re not crazy or insane. You want that statement to prove that you are a reasonable person who would greatly benefit from the assistance.

Here’s a fictitious example:

Problem: Concerned about excess, off-topic chatter during a raid.
Solution: Additional focus on the encounters that matter

“Hey Jarvis,

I appreciate the hard work and energy you expend running the raid. Our raid group is an energetic and talkative bunch of players. Can we get them to tone it down during progression boss encounters? The raid would proceed much smoother and efficiently allowing us to get out earlier and awarding everyone precious relaxation time.

Bonus: They get to socialize in a less pressured environment.”

Signed,
Buster

Let’s break it down.

I appreciate the hard work and energy you expend running the raid.

Jarvis is the raid leader. This guy puts up with just about everything and is the linchpin. He might not get too many pats on the back but this is your way of recognizing the little things he’s doing.

Our raid group is an energetic and talkative bunch of players.

You’re reframing and putting a positive spin on the problem. The raid tends to discuss stuff that’s not relevant to what’s going on. This could be due to excess energy or a lack of focus. But, hey, you don’t really know the root cause. Maybe they’re just hyper from all the gummy bears.

Can we get them to tone it down during progression encounters?

Now we’re getting to what you really want. For the sake of your sanity and to prevent yourself from verbally destroying someone, you’re asking the boss if he can do something to calm players down. Maybe all they need is a firm reminder. Who knows? You don’t care how it’s done as long as it’s done. I will add that it’s a nice touch to offer a solution or two that you feel might work.

The raid would proceed much smoother and efficiently allowing us to get out earlier and awarding everyone precious relaxation time.

This is where you appeal to the rewards section. As my uncle Lawrence Reciprocicus always asks when someone calls on him for a favor, “What’s in it for me?”

You want to offer something mutually beneficial that your target would appreciate. In this case, a smoother raid and an earlier clear time.

Now the next time you feel the urge to throttle someone or want to stab a pen through your raid’s eyes, consider voicing your concerns to your leaders first. You gotta do it with discipline and serenity! Violence is never the answer!