The best guilds don’t walk into a raid improvising. They study the boss mechanics. They assign roles. They communicate positioning, priority targets, and contingency plans. Everyone knows what they’re responsible for before the first pull.
The worst guilds improvise everything and then blame each other when the wipe happens.
Look at your team right now. Do they know the raid plan?
Not the company vision in the abstract. Not the values on the wall. The actual operational plan… what we’re trying to achieve in the next ninety days, how each function contributes to that goal, what success looks like at the role level, and how they’ll know if they’re off track.
Most leadership problems I’ve observed aren’t motivation problems. They’re clarity problems. The team is willing to work. They’re not sure exactly what they’re supposed to be working on, in what priority, toward what outcome.
And the leader often doesn’t realize this, because the plan is clear in their own head. It just never made it out of their head at the level of operational specificity the team actually needs.
A clear raid plan names the objective, identifies each person’s role in achieving it, and defines the signals that tell you if the execution is on track. It’s revisited regularly. It’s updated when conditions change. It’s communicated until every member of the team could explain it without prompting.
If your team can’t do that right now, the plan isn’t clear enough.
Go clarify it. The wipes will stop.
If you asked three team members right now to explain the company’s top priority, would the answers match?

Leave a Reply