Our Cho’gall 25 Video and Heroic Halfus down

We actually killed Cho’gall several weeks ago, but I didn’t have time to properly edit and such. Check out the new guild intro that Brian created for us. Loooove it!

Scored a heroic Halfus kill last night with 5 shots on him. The tough part is definitely making sure the pulls are stable. The second hardest part is ensuring those interrupts are not missed because those shadow novas just destroy. Once I get the perspectives from other players in the raid, I’ll get our kill video up with our Mumble audio. Think I’ll put that on our recruiting page too. If players can’t make the livestream, they can get some idea of how we operate from that at the least.

That boss feels way easier than Nef, that’s for sure. Back to work on taking out the dragon on Monday. We seem to fare better with 6 healers as opposed to 7. I suspect its because the phases go by quicker and there isn’t enough damage being passed out which means overall the healing is less. However, having a 7th healer grants us that extra safety net of being able to account for anything that could trip us up. A 7th means we can counter those Cackle’s easier. Except we’re still taking so much damage. Are we supposed to spread out on those phase 2 pillars to mitigate something?

Have a good weekend!

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?

Question: When do you Call a Wipe?

Keeping the post really short today. Whether it’s in a 5 man, a 10 man, or a 25 man, I’m curious as to under what circumstances your raid leaders call a wipe.

Does it ever frustrate you when your raid leaders do?

Does it annoy you when they should and don’t?

For the raid leaders, does farm versus progression content impact the times you call wipes?

I’ve called snap wipes when we lose 2-3 people in the opening minute of a fight. I’ve called for a continual push even when we were down a half raid.

What’s your take?

Recovering From a Bad First Guild Date

I issued a Valentine’s day blogging challenge earlier on Twitter. It wouldn’t be fair of me to not participate. Any bloggers are welcome to join in. It’s a fun way for bloggers to throw a Valentine’s spin on their posts. If you do accept the challenge, feel free to e-mail or DM me a link to it and I’ll round them all up at the end of the week. I’m sure you can come up with some ideas if you think hard enough.

1327762_rosesPerformance anxiety.

Nervousness.

Fear.

Intimidation.

Those are just some of the few things any prospective raider will experience on their first “date” with the guild. As much as we love to hear a happy ending to a story, the reality is that it isn’t always the case. Here you are, a  player trying to court your new guild. You want them to love you. You want them to be attracted to you. Why? Because you want to be with them too.

But then you screw up.

You stand in the fire. You eat one too many Shadow Crashes. You accidentally dropped a totem in the wrong place.

For whatever reason, your “date” just wasn’t impressed with you at all. Here you are trying to establish a solid foundation with them but you blew your chances because of some silly mistakes. The question they’re asking themselves: Can you be trusted to not screw up again in the future?

Meanwhile, the question you have running through your head is: Will they give me a second chance?

Probably not. At least, not right away. If you epicly messed up, you won’t have a shot. But you know, maybe that guild likes you just enough for another look. But you have to prove yourself.

Communicate

“Hey, I know I screwed up here, here and here. I’m just a little jittery because it’s my first time here. I’ve watched the movies and I know the abilities, but I guess I was just overwhelmed with anxiety. I know I’ll do a better job next time.”

Sometimes a little reassurance to the guild is all that’s needed. Everyone loves a person who recognizes and owns up to their own mistakes. It’s a sign of a truly mature individual who understands they’re not perfect. Now I can’t speak for everyone, but someone who can see where they screw up without having to be told about it is perfect in my eyes.

Listen

Hear out what the guild has to say. If you’re not sure, ask them what you did wrong so you can try to make amends for it. If you know your DPS rotation is messed up, why are you still following the same bad habits? This is especially true if someone is playing the same class as you. Listen to what they have to say, consider it, and see if its right for you. When they drop little hints about what you can do to be better, listen to it.

If that player isn’t you, then you might just need to take a hard look at yourself in the mirror and make the choice between walking away or dealing with it.

Don’t screw up

You were given a second chance. It’s extremely unlikely you’ll be given a third. Don’t mess it up again by choking. They’ve said yes to you again so you better show up and show them who the real you is. Polish up the armor and maybe shotgun a flask.

When they ask you where the nearest raid is, you can curl your muscular Dwarven arm and go “that way”.

Even though you didn’t make the best of first impressions, you might still have a chance to get into the guild of your dreams.

They want to like you

Last thing I want to impart is this:

No one is out to get you.

The guild that you’re going for, you have to remember that they want you to be the one. They don’t want to go back to the recruitment boards again searching for Mr. or Ms. Right. They’re looking for someone who will stick around for a long time.  You’re here because they think they found a potential match and they’re rooting for you to be with them! They want you to ace it so they can go back to drinks! It’s up to you to either validate or prove wrong that claim.

Speaking of which, we’re looking to shore up our roster with a Holy Paladin, an Elemental/Resto Shaman, Rogue and a Mage. But we’ll look at any other classes though. Come check us out.

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.