Handling the Guild Dirty Work

“Nothing so conclusively proves a man’s ability to lead others as what he does from day to day to lead himself.”

– Thomas J. Watson

And I don’t mean scrubbing the toilets.

As leaders, we have an obligation to the players within our guilds. Whenever a boss comes up where something needs to dispelled, I’m the first person to volunteer for it. Not necessarily because I want to, but to show that I can and am willing. The mantle of being an officer comes with a set of unique responsibilities. In order to have the right to ask people to do something, you must be willing to do it yourself.

This is why my raid leader is the first in line when he needs to eat a debuff, maintain constant crowd control or take care of some other craptacular job that no other player really wants to do.

  • Gong banging in Atramedes? He’s always there.
  • Dispelling Blackouts? Sure, I’ll take care of it.

So whether you are a class officer, a role officer or otherwise, it doesn’t hurt to show the troops that you still have it. Because if you keep hiding behind lame excuses and continue giving players assignments you’re unwilling to do, no one’s going to take you seriously anymore. In pickup raids where I’m raiding on my Shaman, I’ll volunteer to tackle any interrupts or purges that need to be done.

To be fair, that’s the only thing I’m really good for on an encounter like the Omnitron Defense System anyway.

Bob Sutton, author of Good Boss, Bad Boss, states that, “Being in a position of leadership is the most reliable way to become oblivious and emotionally insensitive. Fight this by remembering that you’re under a spotlight. You’ll be watched closely by the people you lead – even more so than how you’re observing them.”

Even though you’re an officer, by the nature of your position, you are placed on a much higher pedestal when compared to everyone else in the raid.

Let’s move on to another aspect of dirty work. Let’s go through the not-so-cool responsibilities that officers need to do.

Do not avoid the dirty work

A quality officer must do things that will upset players. As the guild leader, I have to reprimand, gkick and talk to players who need improvement. The last bit is a bit tricky because I don’t have enough knowledge of a class to offer effective feedback. This is where I need my officers to come in play and assist me in supplying that feedback. None of those are responsibilities we need to shoulder alone. Reprimands and giving critical feedback can be a difficult thing to do. If you can’t handle that aspect of it, you might not be the right guy for the job.

Alternatively, grab a guy willing to do the dirty work. I recommend hunters.

In that same book by Sutton, he quotes a study that “Bosses of the most productive work groups confronted problems directly and quickly, issued more warnings and formal punishments, and promptly fired employees when warnings failed.”

Translating that into guilds, productive raid raid groups address any internal problems head on within a reasonable time frame. Denial doesn’t help anyone. You can talk the smack you want, but you better have the guts to confront players as well. Bad officers continue to conjure up some kind of excuse in order to put off what needs to be done. An example would be like me saying I can’t cast Dispel because I don’t have the mana to do it. I’ll be the first to admit that I’m not the best bad cop type of personality. It’s not in my nature. However, I am driven by own desire to excel and succeed in what I do. If it’s a necessity, it needs to be done.

The first thing I’ll do is delegate it. The next thing I do is set an internal deadline for myself where if an officer doesn’t pull off the reprimand, I’ll take care of it personally.

Actually now that I think about it, setting deadlines tends to help in most aspects of life.

Heck, take the extra step and tell someone what deadline you’re setting and what it’s for.

Implementing the two man (or person) rule

I love he said, she said arguments.

It’s difficult to determine and sift through what’s true and what isn’t. Because of recent incidences, I’ve implemented the two person policy. When any type of feedback, reprimand or anything along those lines are being given, there needs to be another officer in the channel with them. They don’t have to be the same class or role. They just need to be players who the GM trusts and who are able to keep each other in check.

No whispers or tells either. Don’t underestimate the importance of tone. Sure there;s no facial contact unless you’re using a webcam. But listening to the tone of someone else is the next best thing you can do to subtly improve communication.

This was an oversight on my part, but I hope this is a step in the right direction.

Quick Guide to Dirty Work

  • No problem is just going to go away. So don’t delay too long in making the hard decisions.
  • Make the hard decisions to the best of your ability. You’re going to screw them up, but it’ll be a learning experience. If you can’t do it, delegate someone who is willing.
  • Tell players why this is necessary. Example:
    • “The stuff you’re saying in raids, whether you realize it or not, is having a negative impact on our morale.”
    • “You’re not nailing those interrupts. Looking at the same fight for the past 3 weeks, your interrupt success rate is 50%. If there’s something stopping you from doing your job, tell me. Otherwise, I’m going to have to pick up another Rogue”.
  • You do not humiliate, belittle, or bad-mouth people if they’re the ones that are under fire. Of course, you’re free to poke fun at the guy who’s at the top of the meters or if he’s the GM, apparently.
  • Don’t lie to your raid. It kills your own reputation.
  • If you’re not able to do say what needs to be said the correct way, don’t do it until you figure out the best approach.
  • Set an example to the rest of the team. Show them you can compete on meters. Show them you can dispel, purge and interrupt like the best of them.

I’m still learning this stuff. I also need to begin applying these principles.

Thinking about starting your own guild?

Tough Call: When to Recruit

The answer is TODAY. 

(Actually, “yesterday” would have been a better answer, but I’m sure you had a good reason to take yesterday off.  “Today” is also an acceptable answer if you have a sizable nerd-crush on Ann Curry…not that I do or anything…)

As a raid officer, at some point it will come to you to bolster your ranks.  The first step to doing this right is to properly assess what you need and when you need it.  Even if you’re accomplishing all your goals currently, you need to plan for the next round.
As I see it, there are two schools of recruiting:

  1. Gap-Prevention Recruiting
  2. Roster-Improvement Recruiting

Gap-Prevention Recruiting

A wise boss of mine once taught me, “If you don’t have a Plan B, you don’t have a Plan.”. 

This means, of course, that:

  1. Things will go wrong, and
  2. Rarely will they go wrong when it’s convenient to you. 

In raiding, this most frequently means a loss, or temporary depletion, of players.  I’d wager that we’ve all been there at one night or another. 
For me, this used to happen at least once a month during Naxx.  I’d log in, and people who had signed up for raid ended up not being online.  It was Naxx, we ALL were burned out before Ulduar came out, so I can understand the lack of motivation, but I still had the job of fielding a viable raid for everyone who wanted to get the job done.  From those times spent using Trade Chat to fill out a raid, I learned a valuable lesson:

Recruit BEFORE you have a spot you need to fill

Since everyone is already reading Thespius’s Raiding 101 column, I know we don’t have to go over the pros and cons of having back-ups/part-timers.  They’re good; keep them around, be honest with them, and keep them satisfied. 

But what about scenarios where a back-up/part-timer just won’t do?  What about when your main tank has a baby, your invincible priest healer has to start taking night classes, or any of the other myriad reasons people can no longer raid?  Fact is, these situations can leave you in the lurch is you’re not prepared for them.  THAT is why a smart officer will never close recruiting, and will most certainly always look to improve their roster.

Consider this:  A business wouldn’t tolerate an inconsistent supplier, they would immediately find a supplier selling an identical product who can assure them of on-time delivery.  I’m pretty sure this is Fed-Ex’s bread-and-butter, actually.  The same should be true of your raid.  You may love the players you raid with.  I know I’m rather fond of a number of the people I’ve played with over the years.  That said, if one of them had to take off, stop playing, or just became overall unreliable, I would owe it to myself and the rest of the team to take actions to ensure the raid continued.  After all, the show must go on.\

TLDR Version: 

Have a plan in mind for who will take over your vital positions if someone has to depart/goes AWOL. 

Don’t turn away potential recruits just because you’re “full” today.  See what options you can provide them before you burn that bridge.

Roster-Improvement Recruiting

Parental Advisory: When I say “Roster-Improvement Recruiting”, I’m talking about doing what it takes (within your own best judgement) to see content and down some end bosses before they become passe.  This is the one that’s going to fill my inbox with hate mail, but it has to be said:

Not everyone you raid with today will be ready when your group wants/needs to move to the next level.

I would never call the environment I raid in hard-core, bleeding-edge, or anything like that.  What I would say is that we’re a results-driven team.  If you can do your job and do it well, and aren’t a complete dick, we’ll be glad to count you among our ranks.  Everyone competes for their spot and everyone has that much more faith in their team-mates because they know that every spot has been earned.

A team like this never “stops” recruiting.  There will certainly be times when you have a solid group and may not have a lot of NEED to recruit, but you should never flat-out deny someone on the basis that they would have to take a spot from someone you already have.

Example:  Let’s say you’re openly recruiting for a healer as gap-prevention recruiting, when along comes a deathknight asking about joining.  (Isn’t it always a DK when you don’t need DPS?) Assuming they are some-what as progressed as your current line-up, and understand that it’s a competitive environment they’re looking to join, take a moment to consider the opportunity in front of you.  Instead of turning them away, point them towards the logs for your current members and if they can beat that, encourage them to apply.

In an environment like this, a recruit should never be seen as a threat.  Your existing members should see recruits as a chance to improve the raid team in one way or another.

True Story: I intentionally recruit other priests to help push me and keep me competitive.  I know I can handle my assignments, but competition teaches me I can always do it better.  Also, the priest who comes in ready to beat me at my own game is surely a formidable ally to have.

Whether you establish rules that spur further recruitment, or simply keep a high profile for your guild and get applications that way, the key is to always ask yourself “will this player help us get through the next step”. 

Crossing the Finish Line

In the end, I say you should think of your raid team as a racecar.
A racecar can’t go anywhere without all four wheels.  That’s gap-prevention recruiting.
A racecar will go faster with performance parts.  That’s roster-improvement recruiting.
Now go finish the race.

Matticast Episode 8: Patch 4.0.6 and Listener E-mails

Welcome to Episode 8 of The Matticast. This week MattKat, Brian, and special guest Veronica from Ask Mr Robot discuss:

– How Patch 4.0.6 effects healers

– Listener e-mails about raid issues, gearing, and judging tank performance.

Don’t forget you can send us your questions or topic, and be sure to checkout and participate in the listener topic every Wednesday.

Subscribe to the show: iTunesRSS

[powerpress]

Does Your Guild Use Set Interrupt Teams?

Have you ever been in a raid with less than stellar interrupts? I’ve seen it happen many times. A small number of players  seem to have that confidence where they feel they can conquer just about any spells or abilities thrown their way. That is, until the encounter decides to throw a wrench in their plans. It usually sounds a little something like this:

“I got next inter—No, I’m trapped! I can’t do anything!”

If you’re lucky, there’s another player with an interrupt who can bail that player out. If not, the group may have just suffered a large setback. Having dependable interrupters on your raid roster is one of those little things that grant peace of mind to everyone. Your raid leader can rest easy knowing that certain abilities will be shut out. There have been times when I cursed because a key melee player had to run out or died due to some random ability.

From what I’ve seen, raid groups usually have a minimal amount of players for interrupts. This allows for maximum DPS time from other players because if don’t need to worry about catching key abilities, they can focus more on their DPS.

But the case I want to make here is for stability. Doubling up on interrupts can help cut down on the number of wipes due to unnecessary boss attacks going off.

Some examples include:

  • Wind Shear: 6 second CD, 2 second lock out
  • Shield Bash: 12 second CD, 6 second lock out
  • Pummel: 10 second CD, 4 second lock out
  • Kick: 10 second CD, 5 second lockout

This is just the start though. There’s a whackload of other classes with interrupt capabilities (Mages, Death Knights, etc).

How should you set teams?

Your interrupt teams will vary by encounter. A typical setup would involve two teams of 2. Preferably, the interrupters would share similar cooldowns and lockout times. Back in Burning Crusade, there was an encounter called Reliquary of Souls. You could find it in Black Temple. That encounter really brought out the necessity for skilled interrupters who could identify which skills to let go and which ones to shut down (like Deaden, Spirit Shock, etc).

A more recent example encounter would be Maloriak where Arcane Storms and Release Abberations need to be controlled.

Every interrupter should use macros to announce their interrupt skills. Actually, if you want to take it one step further, I highly recommend an addon called RSA. It’ll announce whether you were successful or unsuccessful with your interrupts. Or even if your kick got resisted or if the target is immune! Great to have!

If you have a skilled player who can carry interrupts on their own, then you can definitely disregard this post. I’ll raise my coffee cup to you on that. For the rest of us who sometimes struggle with blown interrupts, that safety net will do more in the long run.

Raid Leading 101: Starting your Roster

**Forgive the absence of last week’s post. I got “blessed” by a crazy work schedule that had me away from my desk a lot. Don’t forget that if there’s anything you’d like to discuss or see in a RL101 post, you can always email me**

So, you’ve made the choice between 10 and 25. You know which feels right for you and your friends. Now you need to look at your roster. Your roster is the list of players on your team that you can pull from to make your raid on any given night. Hopefully you’ve got a group of friends that you’ve started with, which will take some of the stress off of recruiting and assembling your team. We’ll start out with the basics of your raid (this is a 101 course, remember). You need tanks, healers, ranged DPS and melee DPS.

Tanks

Tanks are the classes that will take the brunt of the damage while protecting your raid. The classes that can fulfill this role are:

  • Protection Paladin (“Prot Pally”, “Tankadin”)
  • Feral Druid in Bear Form (“Bear”, “Meatshield”)
  • Protection Warrior (“Prot Warrior”)
  • Blood Death Knight (“Blood DK”, “BDK”)

It’s best in a 10-man raid to have ~3 Tanks on your roster (~4 for 25-man). Most raids encounters will require 2 tanks for encounters. Either your 2 tanks will have to alternate who is tanking the boss, one will tank the boss while the other tanks one or more mobs that join the fight, or you’re doing a Council-style fight.

Your Main Tank (or “MT”) should be your most talented tank and will seldom need a DPS off-spec. The other tanks on your roster (“Off-tanks” or “OTs”) should have a DPS off-spec so they don’t need to be totally swapped out mid-fight. Warriors can spec into Fury or Arms, Druids into Balance or Feral Cat, Paladins into Retribution, and Death Knights into Frost or Unholy.

Healers

Healers are the players that you pay to keep you alive long enough to see the boss take its last breath. Classes blessed with this ability:

  • Restoration Shaman (“Resto Shammy”)
  • Restoration Druid (“Resto Druid”, “Tree Druid”)
  • Holy Paladin (“Holy Pally”, “HPally”)
  • Holy Priest
  • Discipline Priest (“Disc”)

For your 10-man crew, count on having ~4 Healers on your roster (~9 for 25man). You’ll always need a minimum of 2 healers (5 in 25-man) for an encounter, depending on how healing intensive it is. It’s best to have the other healers in your roster work on a DPS offspec in case you need to convert to more DPS in an encounter. Priests can spec into Shadow, Druids into Balance or Feral Cat, Paladins into Retribution, and Shamans into Enhancement (Melee) or Elemental (Ranged).

Melee/Ranged DPS

DPS are the players that put the hurtin’ on the boss. They’re primarily responsible for dealing damage to the boss and any adds that may pop up, as well as crowd control, interrupt, off-heal, or help mitigate damage. Here’s the laundry list of DPS you’ll find:

Melee

  • Enhancement Shaman (“Enh Shammy”)
  • Rogue (Subtlety, Assassination, Combat)
  • Arms or Fury Warrior (“Arms War”, “Fury War”)
  • Retribution Paladin (“Ret Pally”, “lolret”)
  • Feral Druid in Cat Form (“Cat”, “Kitty DPS”)
  • Death Knight (Unholy, Frost)

Ranged

  • Elemental Shaman (“Ele Shammy”)
  • Hunter (Marksmanship, Beast Mastery, Survival)
  • Warlock (Affliction, Demonology, Destruction)
  • Mage (Arcane, Fire, Frost)
  • Balance Druid (“Moonkin”, “Boomkin”, “Boom Chicken”, “Lazer Turkey”)
  • Shadow Priest

In 10-man, you’ll want ~8 DPS’ers (~22 for 25-man) on your roster, with a mix of melee and ranged. There will be some fights that will be better for melee DPS or ranged DPS, so a mix will give you a good chance of success. Having any of your DPS players with a tank or heal off-spec is great, but more often than not, you’ll be better off if your tanks and healers are all main-spec.

Summing It Up

A standard 10-man raid will consist of: 2 Tanks, 3 Healers, 5 DPS.

A standard 25-man raid will consist of: 2-3 Tanks, 6-7 Healers, and the rest DPS.

Of course different raids will deviate from this basic model, but in my raiding experience, this is usually what you’ll find. To start out, aim for those numbers. Once you have your 10 or 25, add 1-2 more for each role to solidify your team. Your raiders will need nights off or have real-life commitments from time to time, and those extra people will help keep your raid going consistently.

Coming up, we’ll look at more advanced roster planning, as well as a couple recruitment tips!