Officers' Quarters: Sweet victory
by Scott Andrews 
Nov 5th 2007 at 11:00AM
Every Monday Scott Andrews contributes Officers' Quarters, a column about the ins and outs of guild leadership.
Back in September, I talked about how to manage the raid after a wipe. So I thought it would be helpful to follow up on that column and talk about the opposite. Specifically, I want to talk about guild-first kills. Guild-first kills are among some of my favorite moments playing Warcraft. I'll never forget my guild's first Ragnaros kill, way back when. It's a huge shot of adrenaline to see that big baddie finally topple over into a motionless, sparkly pile of purple and gold. You've worked hard, you've persevered through any number of failed attempts, and it has all paid off. It's an amazing feeling, isn't it? But as an officer, your work is not yet done!
How you manage the guild-first kill is just as important as managing a wipe.
Just after the victory:
1.) Take the time to celebrate.
Don't start barking orders or calling for loot rolls as soon as the boss hits the floor. Take a few moments to celebrate with your raid. Savor the accomplishment. Be just another raid member for a little while. You've earned it!
2.) Emphasize teamwork.
You may know in your heart that if the main tank hadn't stance-danced that last fear so quickly or if that druid hadn't solo-healed the last 10% of the fight, you'd be toast -- again. But this is not the time to point out such things. The lesson your raid needs to take away from the experience was that, first and foremost, excellent teamwork won the day. Feel free to whisper people or send private messages congratulating them for their outstanding individual efforts, but do it later. Guild firsts are a great bonding experience. Let the raid feel the love as a whole.
3.) Thank -- and remember -- the people who were there.
If this is a boss who has given your guild fits, be sure to acknowledge the people that sacrificed their gold, time, and energy to face an encounter that most assumed would end in failure. Everyone hates that guy who "disconnects" for the night after a wipe or two on a tough boss. That person can bring your raid to a screeching halt. A guild cannot progress without people willing to bash their heads against a wall for a few weeks until everything finally clicks. Don't undervalue such people. Take note of who showed up for the wipefests and who only started coming after the boss was on farm. That will tell you whom you should be bringing along for new content in the future.
4.) Get the loot right.
Everyone who was there will remember who got what, and everyone who wasn't there will want to know. So take your time and make sure you follow your own rules and system to the letter. The raid will be patient with you as they ride the wave of euphoria. So wait until you're able to focus on the task at hand and avoid an embarassing error that can taint the victory.
5.) Take pics!
It goes without saying, but take some good screenshots of the kill (and the killers) for posterity.
When the raid is over:
6.) Discuss why you won with your officers and class leaders.
Just as you need to identify why you're wiping on a boss, you need to figure out exactly why you were successful this time. Don't do this in /ra or /g. You'll risk insulting someone and souring the night (i.e.: "I think we won because Soandso wasn't there pulling aggro."). Keep it in /o or, better yet, post in a private forum so you can look back on the discussion the next time you're up against this boss. There's always room for improvement, so don't forget to talk about what could have been done better, too. Now that you're over this hurdle, make sure you can repeat the success next week.
7.) Use your progress to bolster recruiting.
If you're looking to add some members, now is the time. Guilds that are stuck on bosses aren't nearly as appealing as guilds that are mastering them. So advertise your progress. Don't be obnoxious about it by spamming the Trade channel in Shattrath. Put a big notice on the front page of your Web site. Then post about the kill on your server's forum. Most servers keep a list of raiding progress by guild. Make sure your guild is on that list and make sure your info gets updated. People on the server who are looking for a new raiding opportunity or a change of scenery may be on the lookout for guilds that are progressing through the content they want to see.
What does your guild do after guild firsts? Whatever you do, I hope you have the chance to practice it soon!
/salute
Send Scott your guild-related questions, conundrums, ideas, and suggestions at scott.andrews@weblogsinc.com. You may find your question the subject of next week's Officers' Quarters!
Filed under: Officers' Quarters (Guild Leadership)
Reader Comments (Page 1 of 1)
Vestras Nov 5th 2007 12:12PM
"We'll show you the thrill of victory, and the agony of defeat. And Because we have soccer highlights...the sheer pointlessness of a 0-0 tie."
We had this moment last night, guild first kill on Nightbane. Took a smidge of practice and we had him. Posed for screen caps and much fun was had by all.
I agree that first kills make you feel great, as a guild and at a personal level if you were in there for the kill. It also means more loot is in your reach in many cases.
Ryan Nov 5th 2007 12:40PM
I don't see anything that will change the current 'whoever has the most geared out MS warrior wins' school of pvp balance. I dunno, I guess I'm just bored of arena in general. No objectives, no real strategy other than who do you gib first, it's like the last 10 years of multiplayer gameplay never happened.
Scruffy Nov 5th 2007 4:56PM
Hi. I'm from #3 and I'm not entirely ashamed to admit it.
It one thing to learn a boss fight or some tricky part of an instance. It's quite another to start teaching the MT exactly how to tank (prot pallies excluded).
Most of the time, it's just a matter of learning kill orders, keeping track of CC'd mobs, being aware of pats. You know, everything players in an instance should have learned 20-30 levels ago.
Other details help; information is critical. I play WoW in a window and go running to Wowhead before boss fights. If a caster mob can't be interrupted, say it in party chat so the tank can focus on that and DPS can down it. Mob will fear players? Pull it waaaaayy back.
I mean, the kind of mistakes that are funny in instances level 55 and down are downright disastrous in BC instances. Someone breaks a CC early? Mob fears the tank or a priest or 'lock panics and fears? You're BONED.
If someone mysteriously disconnects in a huff, then you better think about how the other players are doing. Hunter that doesn't trap? Warrior that doesn't thunderclap? Mage and warlocks AOEing instead of focus firing? Priest isn't dispelling? Priest and pally not curing diseases? Pally and druid not curing poisons? Druid and mage not decursing? These things happen when players solo up to 70 then get into instances.
For someone who did instances on the way to 70, experiences like these are immensely frustrating and a total killjoy.
BenMS Nov 6th 2007 2:43AM
Not sure you're in the right post there, #2.
Killing Guild firsts can be an awesome time, and I think taking a moment to congratulate people is important, vastly more so than loot. We generally give it a few minutes before we announce in /g, to let the people who are there to have a bit of time in the sun.