Raid leading is like a lot like Project Management. What is a project?
A project has:
- A start (We start at 6pm)
- An end (We end at 9pm)
- A specified scope (What is going to be accomplished, the goal)
- A plan (The order and actions that need to be done to accomplish the goal and who is in charge of doing them)
- Resources (your great group of DPSers, Outstanding Tanks and Miraculous Healers)
- Communication (Call this in vent, healers using addons to see when someone needs special attention, etc.)
- Constraints (We need 2 tanks and three healers for this fight, this one cannot have more than 2 melee dps)
- Assumptions/Expectations
- Lessons Learned (A review of the project’s results with an emphasis on what was done well and what can we do better. I’ll go more into details about this in another post.)
This is a very high level view of a project and as you can see, there’s a lot of similarities with projects done within a business. Each of these parts is essential to a good project but the one that kills projects more often than not is Assumptions/Expectations.
Going into a project or a raid, every member of your team will have assumptions and so will you as the raid leader. When those assumptions are not written out clearly for everyone to understand, you will find that your assumptions and those of your team members can vary wildly.
You may assume that when you send out an invitation to your team for a raid on Wednesday at 6pm and say “Be ready”, that it covers it all. “Being ready” is very vague. To ensure a fast paced and enjoyable raid, try to be as clear as you can and ask for feedback or questions so you can dissipate as many assumptions as possible prior to the actual raid.
Here is a quick checklist that we use at BT:
- Be on time – It’s a question of respect towards your teammates. If you are not there 5 minutes before first pull, you will be replaced. If you are going to be late, please let us know on the board ahead of raid time.
- Have enough flasks, food and consumables for the whole 3 hours of raiding.
- Have every piece of gear properly gemmed and enchanted.
- Review the strategies of the raid’s planned fights.
To help your members, give them the information they need to “Be Ready”.
Tonight, we’ll focus on Ominitron and then Magmaw. Zierlyn, you will be using your offspec and help heal this one. Idkittens, you’ll be kiting the adds on Magmaw, etc.
There are other assumptions that should be communicated to your team whether it’s in your raiding FAQ or in your invites.
- Don’t AFK outside of the planned hourly break. If it’s needed, then tell your raid leader.
- Have vent configured and working.
- Have your PC in working order (I remember one of our members’ whose laptop had to be shutdown after overheating so much it melted a counter top).
- Make sure that you are free of other obligations during raid time. By signing up, you’re committing to these three hours with your team.
- When the raid leader calls a wipe, stop healing, die quickly and then regroup as fast as possible for another attempt.
I know seeing lists like these may worry some people and make them think “It’s a game, relax.” I agree, it’s a fun game and we’re playing it with other people. These 9/24 other people have made the commitment to do all of these things and have a good time together. By being late, stealth afking, showing up without the proper gear and needing to port back, you’re showing a lack of respect to them. Your time is not more important than your teammates’.
As a raid leader, you need to make sure your people have clear expectations of what’s expected out of them and what they can expect out of you and the other raiders. This is one small thing that will lead to smoother, more enjoyable and thus more successful raids.

Where’s the section about ‘scope creep’?
Actually, there was a good example of that last night in our raid. I had to bail (still furious about it) because of huge lag spikes to the instance server. The raid composition was affected and after downing Omnitron and Magmaw, the team did not head to Conclave of Winds as planned but instead went to Halfus Wyrmbreaker.
This was an unplanned scope change that was difficult as nobody had prepared that fight.
Close enough on the business metaphor?
Yeah, close enough. And here I thought I was going to tease you. Next time I’ll bring up Who Moved My
Fish FeastCheese?So wait – Outstanding Tanks, Miraculous Healers, but just DPS? Poor plain old DPS.
Kidding, great list though. I don’t think any of those are unreasonable expectations at all, and really are more of a minimum level of readiness than anything else. Even someone who doesn’t look at a raid in as logical/organized a fashion should have no problem with the fundamental concepts of consideration for their teammates and simply being part of a team.
I said “Great group of DPSers”, Rades. What more do you guys want? An iWin button?
What more do you guys want? An iWin button?
Aw, those are all broken anyway.
Tell that to your brother, who turns up late for raids HE is running XD
Ouch! Well, to me, the key to running a smooth raid starts at the top. The raid leader must adhere to his own expectations. The officers must do the same. If they’re not showing by example, the whole system will crumble quickly.
It does depend on the expectations your brother has for his raid though. If he’s ok with people being late, then I guess him being late is not as bad. I remember being late for a raid once due to an internet issue and the other officers called our house immediately to see what was wrong. Through countless raids, they can expect me to be online a minimum of 15 minutes before the pull as surely as they can expect me to run a readycheck before a boss pull. That last one is actually a running joke in our guild that we cannot fight a boss unless there has been a readycheck. <.<
This post warmed my geeky little MBA heart!