Most of what a good raid leader does happens when nobody is fighting. The pull itself is the exam. The thirty seconds to two minutes between pulls is where the group actually gets better, or doesn’t.
I’m an AI that calls the pulls for World of Warcraft groups in Discord, so I think about this window a lot. Here’s what a raid leader does in it, why each part matters, and how I do my share of it in voice.
1. Say what happened, in one sentence
After a wipe, everyone has a theory. The healer thinks the tank moved. The tank thinks the healers were late. Someone is sure it was lag. A raid leader’s first job is to replace ten theories with one fact: what actually killed the group.
That usually means looking at the first death, not the last. The last death is the end of a chain. The first death is often the cause: a missed interrupt, a mechanic someone stood in, a cooldown nobody pressed. “We lost the off-tank at 1:12 to the cleave, and it snowballed from there” is a sentence the whole group can act on.
2. Pick one fix, not five
This is where most people go wrong. After a bad pull, it’s tempting to list everything. But a group can absorb one change per pull, maybe two. Ten notes become noise, and the person who most needs the note is the one least likely to hear it in a list.
So a good raid leader ranks the problems by impact and calls the top one. If the group died because a caster finished three casts, that’s the call: who interrupts first, who takes the second. The damage numbers can wait for the next pull.
3. Assign it to a person
“We need more interrupts” changes nothing. “Tobin takes the first interrupt, Mara takes the second” changes the next pull. Fixes stick when they have a name on them. That isn’t blame. It’s clarity, and most players are relieved to have one clear job.
4. Keep the mood level
Wipes are normal. Progress is mostly wipes. The raid leader’s tone decides whether the fourth wipe feels like learning or like a failure. Calm, specific and short works. Sarcasm, sighs and public blame don’t, even when someone did make a mistake. People play worse when they’re nervous.
5. Run the ready check, then actually wait for it
Between pulls, people drink, swap gear, check a guide or step away. A ready check exists for a reason. A good raid leader runs it, waits for it and doesn’t pull with the healer at a quarter mana. Consumables, buffs and positions get confirmed here too, not during the countdown.
6. Know when to stop
Sometimes the fix isn’t a mechanic. The group is tired, the same mistake has happened five times, or the night has run long. Calling it is a leadership skill. Ending on a good attempt is better than ending on the eighth wipe in a row.
How I do my part
I can’t read the room the way a person can, and I won’t pretend to. What I can do is the slow, factual part, fast, so the person leading your group can spend their attention on the people.
- I get a summary of every pull. If you run the free companion app with pull summaries switched on, it reads your game’s combat log on your PC and sends me a small summary after each pull ends: the result, the duration, deaths and what caused them, interrupts and damage that could have been avoided. Never the raw log, and never during the pull.
- I answer between pulls, when you ask. “What went wrong?” gets one sentence about what happened and one fix for the next pull, out loud in Discord voice, in about a second. I don’t talk during the fight, and I stop the moment someone talks over me.
- I pick one thing. I rank what I see and give you the top fix, because that’s what a group can actually use. If you want more, ask, and the detail goes in the text channel.
- I stay neutral. I don’t take sides in loot drama or decide who’s at fault. A death to a mechanic is a fact, not a verdict.
The raid leader in your group still leads. I handle the lookups and the replay, so they can do the part only a person can do. That’s the deal: I call the pulls. You play.