Guild Leadership Guide

Nobody applies to be a guild master. You end up there because you cared slightly more than everyone else on the night the last leader quit. Then you discover that the job has very little to do with playing the game and a great deal to do with forty people's expectations.

This guide is about the parts of the job that are not in any raid strategy.

The job is decisions, not tasks

New leaders try to do everything: recruit, lead raids, run the bank, resolve disputes, manage the Discord. Within two months they are exhausted and the guild is fragile, because every process runs through one person.

The job of a guild master is to make the small number of decisions nobody else can make, and to build a team that makes all the others. If you are doing tasks, delegate them. If you are making decisions, ask whether an officer could have made them. Keep only the ones about direction, standards and people.

Build the officer team before you need it

A 40-man guild needs, at minimum:

• A raid leader who owns strategy and calls fights. They should not also be the guild master; the two roles pull in different directions on the night.
• A recruitment officer who owns the pipeline and the guild's listing. This is a weekly job, not a launch job.
• A loot officer who owns whatever system you use and is seen to be fair.
• A quartermaster who runs the bank and consumable supply.

Give each of them real authority in their area and say so publicly. An officer who has to check every decision with the guild master is an assistant, not an officer, and the guild knows it.

Choose officers for temperament, not parses. The best raider in the guild is frequently the worst possible loot officer.

Write the rules down before anyone breaks them

Every rule you invent mid-argument looks like it was invented to win the argument. The rules that matter, and that should be written on the guild page before launch:

• How loot works, including the edge cases: two people with perfect attendance, a trial versus a member, an item nobody main-specs.
• What attendance means, what happens when it drops, and how someone tells you they will be away.
• How benching works on nights when 45 people show up, and how the bench rotates.
• What gets someone removed, and who decides.

You will not think of everything. Amend the rules openly when a new case appears, and apply the amendment going forward rather than backward.

Make decisions people can accept

Members do not need to agree with every decision. They need to believe it was made honestly, for a reason, by someone who considered their side. Three habits make that happen:

1. Explain before you decide when you can. "We are moving to two raid nights because attendance on Sundays has been 31 for a month" lands differently from a surprise announcement.
2. Explain after you decide when you cannot. Loot council decisions, benchings, removals: publish the reasoning in a place people can read it.
3. Never decide in the heat of a raid. Say "we will talk about this after the raid" and mean it. Most disputes are smaller an hour later.

Handle the hard conversations early

The raider who is always five minutes late. The healer who parses well and berates people in voice. The friend of an officer who is coasting. Every guild has them, and every leader knows about them long before doing anything.

Have the conversation the first week you notice it, privately, in voice, with a specific description of the behaviour and what you need to change. Most people fix it. The ones who do not have told you what you need to know.

Delaying the conversation does not avoid it. It moves it to a night when everyone is angry.

Protect your officers from burnout

Officers leave for the same reasons members do, plus one: they stop enjoying the game because every login turns into work. Watch for it. Rotate raid leading. Give the recruitment officer a week off every tier. Say thank you in public and specifically.

And protect yourself. Decide, before launch, what you will not do. If the answer is "I will not manage the bank", then do not, no matter how much faster you would be at it.

Know what the guild is for

Guilds fall apart when the people in them wanted different things and nobody said so. Some want server firsts. Some want to log in and see friends. Some want both and will be disappointed either way.

Decide what yours is for, say it in the description in plain words, and recruit for it. "We clear current content on two nights and we do not race" is a clear promise. Keep it, and the people who wanted it will stay for years. Break it quietly by drifting hardcore, or drifting casual, and they will leave without ever quite saying why.

The measure of a good leader

Not the kill screenshots. The measure is this: when you take a two-week break, does the guild carry on exactly as before? If yes, you have built something. If no, you have built a dependency, and it is time to delegate.