accountability

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.

Tough Call: Are your officers carrying their weight?

by

tc-carryweight-480

Welcome back for another week of cupcakes and snugly puppies. 

Psych!

We both know we’re not here for that, so let’s get down to business. What follows will be Part 1 of an 18-part epic series.  When I am through, angels will descend from on high and carry the compiled works to the Vatican for safe-keeping.  Ages from now, historians will place this up there with The Illiad, Kafka’s Metamorphosis and Hitchhiker’s Guide. 

Hey, a guy can dream right?

Recently we discussed the important roles and differences between the GM and the Raid Leader.  In a 10-man strict guild, you may be able to get by with only have these two officers and some trusted guildies from whom you can expect honest answers.  However, I find that even 10-mans and almost certainly 25-man raiding guilds run better with multiple officers.

In my experience, and from what I’ve been told by other leaders, there often arises a situation where guilds have officers who seem to be the Deputy of Do Nothing.  (As opposed to my own favorite title: Deputy of Awesome.)  I have found that this unique problem can stem from three sources.

  1. Not a Leader – These are the officers who may be great players, may be long-term guildies, but once they become an officer, they don’t really do much other than give their opinion when prompted by the RL or GM.
  2. Fatigued Leader – They were great officers but are not just phoning it in, and are only around out of a sense of obligation.
  3. No-Confidence Leader – They would do a great job, if they thought they had the back-up and the RAA to do it.  As it stands, they feel that the average member has more say than them and may be tired of the squeaky wheel getting the oil.

The Deputy of Do Nothing is a drain on your raids efficiency and on the potency of your leadership team.  As the Captain of this ship, it’s up to you to diagnose this malaise before it spreads to the rest of the crew.*

(* unless, of course, they have no authority while in raid and everyone knows it.  In which case, carry on.)

Not too long ago, I read an article about someone who’s trying to have a “Guild Without Officers”.  While I don’t agree with this idea, I thought the insights below were especially suitable to this conversation:

“I look back on how it used to be, with too damn many officers, all of whom did very little to actually help the guild, preferring instead to treat officership like some sort of insiders club where they could talk amongst themselves in their little clique. I recall making rules and chivvying and cajoling and beating my head against the brick wall that was getting anyone else to step up and take responsibility for anything.”

How do I spot this before it’s too late?
Part of being the GM includes an unwritten commitment to your members that you will make sure the rest of your leadership team has the responsibility, authority and accountability to handle their respective areas.  Therefore, you MUST make sure that among your GM duties you include your due diligence.  Kick the tires, shake the branches and see what turns up.

  1. Talk to your members.  I’m sure you’re probably running heroics, or BGs or whiling away the hours getting that fishing feast while in Mumble with your teammates/members.
  2. Try to recall the last time you had an in-depth conversation with your officer.
    • Did they prompt the conversation or did you?
    • How many solutions did they present to the problems your team was encountering?
    • How many of those solutions have been implemented?
  3. Review how organized/engaged their part of the team is on your forums. If this is something that is important to you or your guild community, your officers should be on top of it.
  4. Lastly, think of what you would be doing if you were in their position.  Don’t think that just because you don’t play healer, you can’t tell a healing officer what to do.  Management skills are not class-specific, and chances are you were once doing their job.  At minimum, you will come up with some ideas to discuss next time you talk to them. At best you’ll see that there are opportunities that you both can capitalize upon.

How do I prevent this?

The first step in preventing anything, is to clearly state your expectations upfront.  After all, human nature dictates that people will operate to the level that is expected of them, and if you don’t set that bar, you’re asking them to decide how to run your guild.  You and I both know that the reason you promoted someone to a position of authority is because you trust their opinion, intelligence, communication skills and reliability.  So the only thing missing is your guidance/structure to tell them how you want these skills applied.

  • Rule #1: Do NOT promote all your friends.
  • Rule #2: DO promote everyone you can trust in your absence
  • If Rules 1 & 2 overlap, you should either make more friends are trust more people.
  • Clearly define the duties of each officer position
  • Grant them authority to do their job as they see fit. Nobody can do a job well if they think they have to ask permission.
  • Agree upon how often you expect feedback from them. Ex: Post-Raid Debriefings, Weekly Status Reports or End-of-Tier strategy sessions.
  • Make sure their position is easy enough for the rest of your team to understand. You don’t want anyone saying “what does he do again” or “he’s an officer just because he’s friends with XYZ, he doesn’t do anything”.  
  • Make sure they are NOT the type of person who settles for just doing their job description.  Good leaders appreciate new talent and new ideas.  Encourage those people who could probably do your job.  They will keep you fresh and your team will benefit.
  • Let them know that it’s acceptable to come to you for help BEFORE a fail.  
  • Establish a routine or set reminders for yourself to remember to review these steps and refine them where needed.

Next week we will continue and discuss what you can do once you’ve spotted the problem.

As always, comments, suggestions and questions are appreciated.  Also, the CD of my stand-up routine is available at the table by the door.  I’m here all week.  Tip your waitress!

Raid Leading Backbone

by

**Image from “Patton” courtesy of 20th Century Fox Films**

I have a fault. Well, I have lots, but the one I’m going to talk about is my propensity to be “too nice”. Ever since I was a kid, I’ve hated confrontation. I wanted everyone to be happy. People in Team Sport (my guild) have called me “The Politician” (without all of the negative stigma from current American politics). I try to make sure everyone is listened to and catered to as much as possible.

However, with regard to leading Team Sport’s Raid Team, I’ve hit the biggest snag. I can’t be “The Politician”. I have to be a leader. Previous incarnations of Team Sport raiding were very casual. If people happened to be online that night, we raided. If not, no big deal. As time went on, I noticed a few of us were very passionate about getting a raid going, while others were very lackluster about the whole ordeal. I always tried to get us raiding while not being inconsiderate to those that weren’t interested that particular night. Everytime we came close to getting something solid going, it would fall apart. Someone would have a real life issue (totally understandable) or just randomly disappear on a WoW break. Each time it would fall apart, I would most likely take my raiding desires elsewhere but found myself always back in Team Sport once it looked like raiding was possible again.

With about 2 months left to the expansion, I worked with a buddy of mine to throw some much-needed structure into the system. It started out great. We did a merge with another small guild that had the same issues, and we killed 10-man Arthas within one month. This proved to me that our team has what it takes to be a good progression crew. We just need some structure and drive.

The Present

We’ve had a good amount of guildies return to the game from “retirement”. A lot of them seem incredibly excited to raid the current content. However, when I mention this new structure (scheduling, accountability, responsibility), a few have balked at it. The main goal of the team is to actually progress through content while it’s still current, not eventually bash through it when it’s old news and nerfed to the ground. To do that, I’ve been working diligently to implement some guidelines:

  • Consistency – I justly understand and sympathize with real-life issues. Sometimes I have to work late, or I have something important that needs to be taken care of on a raid night. However, the core of us have done what we can to work our schedules around being able to raid together. We raid 3 hours each night, 2 nights each week. I don’t think it’s too much to ask for core raiders to be consistently available (within reason…don’t miss the birth of your child or risk getting fired).
  • Responsibility – A cardinal rule of raiding is being prepared. Make sure your gear is enchanted and you have flask and food available. Take the time to look up the fights. Don’t take unannounced AFK breaks or breaks that are longer than what the Raid Leader has set forth. Pay attention and look for ways that you can contribute.

If a Team Sport raider can’t consistently be available, or just lacks responsibility and preparedness, they’ll be placed in a standby slot (at best) or just not on the team (at worst). I’ve made it clear that we’ll do more casual raiding nights any other evening of the week (akin to the “if we have people on, we raid” mentality), but the Raid Team core wants Tues/Thurs night to be focused and dedicated.

The Challenge

There are some that have thought that it is too much to ask. I’ve been told that I’m making raiding “feel too much like a job” and that I’m “taking the fun out of it”. Frankly, I expected this out of some. These are people that have always enjoyed the “casual” mentality of our old raid style. I don’t blame them. It was fun when we all had the time and were just kind of strolling around Azeroth, hittin’ up a raid when we could. However, many of us don’t have that kind of time or mentality any longer. That is the precise reason these changes were made.

I’ve been recruiting to fill those spots that were once occupied by the more casual players or ones with unpredictable schedules. It does pain me to be looking for other people instead of the long-standing Team Sport members that I’ve been playing with for 3+ years, but it’s just not fun for the Raid Team core to log on, and find out we’re not raiding because of people that we can’t rely on.

So the challenge I face: How do I institute this structure and work toward the raid’s success, while still maintaining in-game friendships with those that simply don’t want to be a part of a Raid Team like that?

Matticus already told me: “Don’t be friends with your raiders.” I get that. It makes sense. It’s why there are corporate rules of management not fraternizing with employees. It muddies the water. However, I feel it’s possible that I can be strict and firm with regard to the raid, and then just be myself whenever it’s not about the raid. The trick is to let them all know that’s what’s going on.

I need to continue to be firm on what the goal of the raid team is, and how we plan on achieving that. I also need to be diligent about communicating what’s going on with the raid and its raiders. If I make sure everyone’s aware of what’s expected, then they can’t legitimately get angry when something is not up to snuff.  I have to hold the raid accountable, as well as hold myself accountable.

Have you ever dealt with being a Raid Leader of your friends? What tricks have you used to keep things moving forward without sacrificing friendship?

On that note, Team Sport is looking for a melee DPS or two for core slots. Other roles are full. However, if you’re interested in being a part of the team in a standby role, those applicants are always welcome. Outside of raiding, we’re very active in PvP and regular casual gameplay. We’re an Alliance guild on the Ner’zhul server (PvP-PST). Further info and an application @ http://teamsport.guildlaunch.com.

Accountability Starts at the Top

by

This is a guest post by Arkom.

If you’re a guild or raid leader, you have certain expectations for your guild or team members. You establish rules and policies, you set up strategies, and you assign people to handle certain jobs. These aren’t hollow gestures and you want people to follow what they’re told to do. I mean, you do all of these things for very specific reasons. And when someone doesn’t follow along in the spirit of things? You hold them accountable for their actions, right? But what does that mean for you? How do you figure into the grand scheme of things, since you are at the top of whichever chain of command? What should you do when you make a mistake? Have you ever really thought about it?

The View from the Top

When you are in a position of leadership, it’s easy to miss things. You end up being responsible for so many things in your guild or your raid team that some of them will naturally slip by. This is unfortunate, but it happens because we are human and we’re dealing with other humans. We are not infallible. But in this sense, we get a broader view of what’s going on. To paint a mental picture, you can imagine you’re on a balcony, looking down at a crowd on the street. You see the group as a whole, moving to and fro, busily doing the things that they do in their day. Things may appear to be normal and perfect on the surface. However, there may be someone in that crowd who just stole someone’s wallet and no one is the wiser because there are too many people and all of them have their own things going on.

The View Looking Up

The people on your raid team or in your guild, however, have precisely the opposite vantage. In their picture, they may all be standing in that crowd on the street, looking up at you on the balcony. That is to say, as a leader, you are under constant scrutiny. Where you may not see the mistakes of an individual in the whole group every single time, you can bet your dear Aunt Mavis that more than one person in that crowd will see the mistakes you make. That’s sometimes an uncomfortable position to be in, but that’s why you get paid the big bucks. It may also be the reason you pop Extra Strength Tylenol like they were candy.

R. E. S. P. E. C. T. Find Out What it Means to Me

Now that I have you feeling like you’re you’re trying to use the bathroom in a house with glass walls, what DO you do when your human side (not the one referenced in the bathroom bit) shows and you make a mistake? Well, that really depends entirely on what you’re comfortable with. What should be obvious, I think, is that the best course to take in this situation is to fess up to falling short. Admit your error, apologize if that’s necessary, and do your best to not have a repeat performance. The tricky part of this scenario is that not everyone is comfortable with these things. To those people I say, “You’re in the wrong position.” One of the greatest tools a leader has at his or her disposal is the ability to honestly account for their failings. If you just glaze over the issue, ignore it completely, or offer up an empty apology to your team or guild, you’ve severely injured your reputation, your credibility, and the respect that those people have for you.

There’s a common notion that leadership is a position of servitude. Perhaps it isn’t correct in its every facet, but it certainly is true that we are, to some degree, beholden to those that we lead. We have a responsibility for them, which we have taken on of our own free (and sometimes I think, insane) will. After all, those who lead but have no followers have often been referred to by such colorful terms as, “crazy,” “eccentric,” and things that Matticus probably wouldn’t like me to put in his blog. So let’s just say that without people to lead, you aren’t a leader at all. When you damage their respect for
you, when you hurt your credibility, when you tarnish your reputation, you give those people a reason to leave. The more reasons you give them – and believe me, these reasons compound faster than you would think – the harder it will be to get others to join and stay in their place. So if you do have problems with saying things like, “I’m sorry, I made a mistake there and I will do my best not to let it happen again,” you should probably work on that or consider a future in playing games like Solitaire.

Over-stating the Obvious

Am I? I wish I was. Oh, by Ghostcrawler’s chitinous shell, I wish that I was. I sometimes find it hard to believe the number of times I’ve found myself in situations where the leadership’s reply never came at all, or if it did it was completely empty (and that’s much, much worse than not saying anything at all) or something about how their mistake wasn’t a mistake at all, because they’re the leadership and what they say goes. It happens. Perhaps you’ve been in a situation like that, from either the side where the leaders were saying it to you, or being part of the leader group that was saying it. If you have ever been subjected to those things, I’m guessing they didn’t endear you to those who were supposed to be leading you. World of Warcraft is a game and it’s something we play to have fun and unwind. That doesn’t seem to add up with the part where you have this whole crazy responsibility thing to worry about, but it’s true regardless. So when you find yourself at one of those points in your life as a leader when you’ve just boned it in front of a group, my advice is to take a moment to consider what you would expect of one of the other people in that situation. Would you want an explanation? Would you want an apology? Would you want to make them cry by bawling them out loudly and publicly and then yell at them more for crying like the More DoTs!!! guy? Well, for all of those but the last option, I suggest you do the same yourself. Apologize. Explain the mistake. But stand up and admit you were wrong. For that last one? Anger management. Seriously.

When you lead a raid or you lead a guild, the people who run with you or who are members of your guild are putting a trust in you to be an example of what you expect in them. You are in a position that allows you to directly influence the experience they have in this game, for better or for worse. That’s a huge responsibility and it should be taken seriously. If you can’t admit when you’re wrong, you aren’t just making things bad for yourself, you’re making things bad for them, too. Remember, it all starts with you and it all ends with you. And let’s face it, when you do have to take the heat, it kinda sucks, but when you know that you’ve played an important part in making other people’s time in World of Warcraft better, more fun, more exciting, and more entertaining? That’s a pretty great feeling. That’s the feeling that makes it all worthwhile.