Epic Loot

What went well in our raid this week?

We finally nailed the add phase without losing anyone to the cleave.
Voice comms were crisp and callouts came through on time.
Our healers handled the burst damage like absolute pros.
Wipes & Mechanics

Where did we wipe or struggle with mechanics?

We kept standing in the fire during the third phase transition.
Interrupt rotation broke down and a cast got through twice.
People were slow moving out for the spread mechanic.
Strats & Assignments

What should we change in our strategy or roles?

Assign dedicated interrupt order so casts never slip through.
Reposition the raid to stack tighter for healing efficiency.
Swap one DPS to help on adds during the burn phase.
Guild Morale

How is the team feeling and how can we keep it fun?

The mood stayed positive even after a string of wipes.
We could use one more short break during long progression nights.
Some banter got a little sharp when frustration set in.

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, a short review afterward is how the next night goes better. The World of Warcraft Raid Review takes the format of an agile retrospective and reskins it for raid nights, so officers and members can talk through encounters, coordination and morale without it turning into a blame session. The board has four areas. Epic Loot is for what went well: clean pulls, clutch saves, good callouts. Wipes & Mechanics covers where the raid struggled, framed as data to learn from. Strats & Assignments is where the team agrees on changes to positioning, cooldowns and roles, and Guild Morale checks how people are feeling and whether raid night is still fun. Keeping the talk on mechanics and encounters, not individual players, makes people more willing to admit what went wrong. Run it after a progression night, at the start of a new tier or after a rough wipefest, and end with clear assignments so everyone knows their job for the next pull.

World of Warcraft Raid Review retrospective format

Epic Loot

What went well in our raid this week?

Use this area to celebrate wins, big and small. Ask members to call out clean pulls, clutch saves, smart positioning and good communication. Naming what went right tells the raid which habits to repeat 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 on a new boss, to refine the strategy before the next attempt.
  • After a new raid tier launches, to agree on assignments, consumables and expectations across the roster.
  • When a string of wipes is causing frustration and you want to turn it into feedback the raid can use.
  • At the end of a raid lockout, to look back on performance and morale and decide 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?

Want a warm-up your team plays, not just answers out loud? Browse free icebreakers →

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 the next pull.
  • Celebrate at least one win every session, even after a rough wipefest.
  • 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?
It's a retrospective format reskinned for WoW raid teams. Your guild reviews what went well, where it wiped, what to change in strats and assignments, and how morale is holding up.
When should we run a raid review?
Run it right after raid night, especially after progression attempts or a new tier launch. Feedback is most accurate while the pulls are still fresh.
How long does a raid review take?
Most reviews take 20 to 40 minutes. Timebox it so it stays focused and nobody dreads it before the next raid night.
How is this different from a standard retrospective?
The structure is a classic agile retrospective, but the areas are themed around encounters, mechanics, assignments and guild morale, so raiders recognize them straight away.
How do we keep the review from turning into blame?
Keep the discussion on mechanics, strategy and coordination, not individual mistakes. Collecting ideas anonymously first also makes it easier for people to admit what went wrong.
Ready to run this retrospective?Try this retrospective live