Stare Decisis in Loot Council

Just about a month has gone by in the formation of Conquest. Loot council continues to be an interesting challenge because the council never knows what sort of situation will present itself.

In today’s post, I wanted to talk about an important concept that’s not only valuable in the legal arena but also in an LC guild.

Stare Decisis

This is a legal principles where judges have to follow precedents established in previous decisions. How does this apply to WoW with respect to loot council? Because the decisions we make in how we hand out loot are expected to be binding. I’ll typically follow the principle of Stare Decisis but ultimately, I won’t hesitate to go a different way in decisions of loot for progressive reasons.

Unfortunately, the reality is that virtually no two decisions are going to be the same. You will have similar cases and they’ll be decided similarly. For example, we awarded a tier piece to a Resto Shaman completing his 4 set (because Chain Heal is still whoa). But if I had my 3 piece and a 4th Priest token drop, I wouldn’t award it to me purely because of the bonus (since I don’t use Greater Heal that often to justify it). It literally is a case by case decision. This is bad in that we’re not following a precedent but good in that we’re willing to remain flexible. Remember that this is a loot council not a court of law. Items will drop again.

Decision to Reward vs Decision to Gear

For guilds that have started progressing through different raid instances, realize that you’re going to come across a dilemma and I guarantee you that it will happen. Every member on your loot council is going to ask themselves the following question when an item drops:

Should I award this item to the player who has run all the 10 mans and done all the heroics or should I award this item to the player who dinged recently dinged 80 and hasn’t had the time to get as geared as the other players?

There are two schools of thought on this and let me tell you what goes through my head every time.

Reward: I like to reward players for their efforts. They hit 80 earlier on ahead of the curve. They’ve managed to work their way into pug groups to get themselves geared. Without their efforts, the guild would not be where it is right now. Their contribution is important and I want to recognize that.

Minimum standard:  The other perspective is to gear up the weaker geared player since that player hasn’t had as much time to get where they should be at. Especially for progression kills, there’s a minimum standard that every player regardless of class has to meet. To make life easier on your raid group, the weaker players have to be brought up to speed.

The past 2 weeks have been a lot of fun for all of us (I hope). Everyone has either reached the minimum benchmarks that have been set in terms of performance (2000 DPS on Patchwerk) or have exceeded it (5000+ DPS on Patchwerk). Now that the minimum standard has been reached, I can further lean towards rewarding players that can use items off of the second level bosses such as Kel’Thuzad and Malygos.

Mind you, I’m still just one person on Loot Council.

Mixed messages?

Following a decision that was made earlier for loot is good, especially when deciding on subsequent items. But don’t chain yourself to it or lock yourself.  Keep your loot council flexible because they have to adapt.

Don’t hesitate to acknowledge mistakes.

Don’t commit.

Don’t promise.

Don’t over deliver.

Don’t bind yourself.

So like Amava says, consistency does matter.

There was a case last week where a tanking neck dropped. Both of our tanks expressed interest. We were at a dead lock. The tanks wore the same neck and they could’ve equally benefited from it. We were taking too long. I gave the instruction to roll it.

I realized later on in the evening after the raid was done that it was a bad idea. Upon further reflection, I doubt I’ll give that order again. The exact reasons that crossed my mind were the same ones that Amava listed. This would’ve been the only time (not counting our first unofficial raid) that rolls were used to decide loot. Our current tiebreaker is an officer who is not a part of the loot council and does not wish to take part in decisions. That’s a temporary fix that I need to address. My options are to elevate another player to the loot council (a DPS cloth wearer, perhaps) or set it so that in the event of a tie, my choice wins (Overlord Matticus, hmm). 9 times out of 10, we do reach a consensus. But things like tier tokens always take a bit longer since they’re useful for so many players.

By the way Amava, yes I do read your blog when I can. I read it so that you can keep me honest. Keep doing what you’re doing. I won’t punish you for speaking out or voicing disapproval.

Some more food for thought for players looking and still deciding upon their loot systems.

The Delicate Art of Delegation

Last night, I wrote a heartfelt post detailing my trials and hardships in the captaining of Conquest. While I believe the crew is just as (if not more) important than the captain, all executive decisions regarding which way the ship is going rests on his shoulders. I’ve been in guilds where there were co-GMs are multiple leaders. It resulted in a lot of indecision and little progress. That being said, if there comes a time where a significant choice needs to be made, what I’ll end up doing is gathering up my senior staff. I’ll give them some time to illustrate their case for or against. I’ll let them talk it out while I listen and deliberate. But once the time is up, a choice has to be made.

Learned about that from Tom Clancy’s Executive Orders (Jack Ryan). Great book, by the way. I’ve always loved military thrillers.

I noticed a trend that emerged in the majority of the comments.

Joveta says:

“You probably -shouldn’t- be Healing Lead on top of everything else you’re doing. Delegate delegate delegate!”

GoW says:

“please, use your Officers as much as you can.”

Starman says:

“What I found is that having a really good 2nd in Command that you can split the pre setup check list with helps a TON.”

Tatiana says:

“Use your officers. Delegate. You do not have to carry the entire load.”

Lakland says:

“Also- delegate, delegate, delegate! You are raiding with (some) very competent folks. My guess is more than one or three of them has the capabilities to raid lead themselves. Take advantage of their skills and step back – captain the ship.”

Now how exactly does one go about doing that? I can’t simply just ask a person to do something. I don’t know if they’ll even like it or more importantly, want to. I don’t want people to chop wood for me or to cut and shape sails. I want them to yearn for the open seas.

Self motivation is the way to go.

But I do need to have clear cut positions and roles. I’ll see to it that every major position can be fulfilled by 2 people in case 1 person won’t be around.

Let’s use corporate analogy. I’m running out of sailor ones. Not everyone here is technically listed as an officer. But their roles are important, all the same.

Matticus
Position: CEO

Purpose: Makes guild level decisions in regards to guild directions and objectives. Responsible for day to day affairs and overall raid strategy. Plans raid schedules. Oversees preliminary raid preparation and post raid activities. Serves on the board of loot directors.

Sydera
Position: CFO, Human Resources, Director of Restorative Operations

Purpose: Handles matters pertaining to personnel and guild applicants. Oversees guild finances and resources. Quarterbacks the healers. Serves on the board of loot directors.

Kimboslice
Position: Director of Strategic Operations

Purpose: Contributes strategy and tactical approaches to bosses. Also acts as DPS quality assurance. Raid disciplinarian. Quarterbacks the DPS. Heroism caller.

Assuming he stays up longer than 14 seconds against an undercard.

Ice
Position: Lootmaster

Purpose: Ensures all things shiny go to the proper players. Handles the looting of greens, blues and epics. Serves on the board of loot directors. Battle res organizer (assuming the CEO or Director authorizes the use of a Battle res in an attempt, more on this in a future post).

Hassai
Position: Tank

Purpose: Sets the overall pace and speed of the raid. Has been granted full autonomy and discretion in terms of trash pulls. Knows when to pull and when to hold.

Briolante
Position: Tank and Technical Director

Purpose: Handles any unforeseen or unexpected trash mobs. Oversees the guild technical infrastructure which includes the guild website and forums.

With that, I do believe that just about summarizes my staff. I have no doubt that as time goes on, some of their roles will begin to mesh and evolve. Perhaps new problems will occur and solutions will be needed. That does not necessarily mean I have to overthink it or issue out another promotion. I think I’ve got a great team here with their roles properly outlined.

As an aside, it’s course selection time. I wonder if I would benefit from a business management course.

Probably not.