What is the World of Warcraft Raid Review
Whether your guild just downed a Mythic boss or spent the night wiping on the same mechanic, every raid night is a chance to learn and grow as a team. The World of Warcraft Raid Review brings the spirit of the after-action report to your raid group, helping officers and members reflect on encounters, coordination, and morale in a structured, friendly way. It borrows the proven format of an agile retrospective and reskins it for the world of Azeroth, making continuous improvement feel as natural as repairing your gear between pulls. This format works by guiding your raid team through what went well, where the wipes happened, and what to change before the next lockout resets. By focusing the conversation on encounters, mechanics, communication, and group cohesion rather than individual blame, you create a safe space for honest feedback and shared accountability. Topics prompt members to surface insights about boss strategies, raid assignments, voice comms, and consumable readiness so the whole roster can show up sharper next time. The real value is in turning raid frustration into actionable progress. Guilds that review their raids consistently clear content faster, retain members longer, and keep raid nights fun. Use this template after a progression night, a fresh tier launch, or a tough wipefest to keep your team aligned, motivated, and ready for the next big pull.
World of Warcraft Raid Review retrospective format
Epic Loot
What went well in our raid this week?
Use this topic to celebrate the wins, big and small. Encourage members to call out clean pulls, clutch saves, smart positioning, and good communication. Recognising success boosts morale and reinforces the behaviours you want to see repeated next lockout.
Wipes & Mechanics
Where did we wipe or struggle with mechanics?
Focus on the encounters and mechanics that caused problems, not on blaming individuals. Frame wipes as data the team can learn from. Dig into whether the issue was strategy, awareness, gear, or coordination so the group can target the right fix.
Strats & Assignments
What should we change in our strategy or roles?
This is where the team turns lessons into a plan. Discuss raid assignments, positioning, cooldown timings, and any strategy adjustments for next time. Capture clear, actionable changes so everyone knows their job before the next pull.
Guild Morale
How is the team feeling and how can we keep it fun?
Raiding is a social activity, so check in on the human side. Talk about pacing, breaks, attitude, and whether everyone is having a good time. A positive, supportive atmosphere keeps your roster showing up and reduces burnout.
When to use this retrospective
- After a progression night where your guild was working on a new boss and want to refine the strategy before the next attempt.
- Following the launch of a new raid tier to align the roster on assignments, consumables, and expectations.
- When a string of wipes is causing frustration and you want to turn the night into constructive, actionable feedback.
- At the end of a raid lockout to reflect on overall performance, morale, and what to improve next reset.
Suggested icebreaker questions
- If your raid team were a boss encounter, what would our signature mechanic be?
- What is the most memorable wipe you have ever been part of and what did you learn from it?
Ideas and tips for your retrospective meeting
- Keep feedback about mechanics and encounters, not individual players, to avoid blame and keep the guild together.
- Run the review shortly after raid night while the pulls are still fresh in everyone's memory.
- Give quieter members a chance to contribute by collecting ideas anonymously before discussing them.
- End on the strategy and assignment changes so everyone leaves with a clear plan for next pull.
- Celebrate at least one win every session, even on a rough wipefest, to keep morale high.
- Timebox the review so it stays snappy and doesn't eat into rest time before the next night.
Frequently asked questions
What is a World of Warcraft Raid Review?
When should we run a raid review?
How long does a raid review take?
How is this different from a standard retrospective?
How do we keep the review from turning into blame?
New to retrospectives? Read our guide on how to run a retrospective →