tough-call

Tough Call: Real Officer Set-Ups In Cataclysm

by

Maslow's Hierarchy of Needs
Welcome back for another issue of Tough Call, with me, Viktory.

Disclaimer: What follows is the summation of my opinion based upon the responses I received from over a dozen guild masters when I asked them about their officer corps. Given the content of my last two posts, I felt it would be relevant to take an honest look at how guilds are setting up their government structure these days. This does not mean you should change your guild structure right away.  It does mean, however, that if you were looking to make a change, you can perhaps derive some supporting arguments from a few successful GMs cited below.

A few weeks ago I put out a call for GMs to help me get an idea how their guilds are operating, and, more importantly, what sort of  hierarchy they have put in place to make their guild succeed.  Out of the numerous responses I received, two solid trends emerged:

  1. There are a LOT of different ways to set-up your guild hierarchy, each with their own respective success rates and ease of implementation.
  2. There are far fewer vanity positions in play these days. At least among the sample group at my disposal, it seems there are most GMs expect more output from their officers.

I am happy to see that the days of  “So-and-so has been with us for a long time, so they are an officer now” are largely over.  Only 2 of the GMs who responded to my survey said they had non-specific officer roles (as in “we all do a bit of everything”, which really leads to “everyone assumes someone else is doing the dirty work”).

To get my information, I asked each GM three quick questions, and let them tell me the rest (and believe me, guild managers love to tell you about their guild, its environment and their genius set-up to solve all problems.)

First Question: “What officer positions do you use, and do they report directly to you or is there a chain-of-command?”

Most Common Positions:

  • – Raid Leader (separate from a role leader)
  • – Melee DPS / Tank / Ranged DPS / Healing role leaders
  • – Bank Officer
  • – Recruitment Officer

Some GMs also reported using Morale/Relations officers and an officer rank for Loot Council or Loot Master, separate from other officer duties.  I’m not sure that I’d classify these jobs are something that needs a full-time officer, but I’m also extremely hesitant with the idea of a part-time or “junior” officer.  If it wasn’t so prevalent, I’d lump “Bank Officer” in with this lot.

As for command structure, it’s fairly unanimous that members report to their respective role leaders, who then in turn report to the GM.  I do wish, however, that I had devised a way to get more information about how the recruitment, bank, and morale officers interact with this command structure.

To me this combo represents a stark contrast to the landscape I saw when I started raiding back in Karazhan.  Instead of a GM who ran every aspect and had a few cronies as officers (which is what typically gave loot council-style raids such a bad rep), we are seeing 25-man guilds shift into fully-fleshed organizations.  Positioning the GM as the Chairman of the Board seems to be the clearest way to define duties/responsibilities, and is an efficient way to make sure the various aspects of the guild function at peak performance.

Second Question: “Have you had to add any officer positions since the end of Icecrown Citadel?”

The answers to this question fell in two distinct patterns:

  • Organization increase: bank officer, recruiter, defined class leads.
  • Expansion increase: recruitment officer, 2nd raid leader, PVP leads.

This should tell you that if your guild isn’t growing or refining, you’re stagnating.  12-24 months from now you will be doing things differently; the faster you can figure out what that will be, the better the transition will go.  After all, these are guilds that had 4-5 years of experience and still found roles to add and needs to address after ICC.  Learn from their example and succeed.

Third Question: “If you had to cut one officer position (not person) today, who would it be?”

A few GMs refused to answer this one, or gave responses that never answered the question, but the consensus was either the bank officer or morale officer would be the first to go.

As I stated above, I’m not sure that these are full-time jobs anyways.  In my guilds we’ve always just defaulted to the most likable officer being de facto “HR guy.”  I am very interested to hear any feedback about ways that a bank or morale officer could contribute on-par with what a raid leader, role leader or PVP lead does.

As always, leave any question, comments or epic knitting patterns in the comments below. (I’m trying to get someone to knit me a bad-ass scarf to wear while podcasting).  Also, if you have a situation that you’d like to have me address in a future column, feel free to send it to viktory.wow@gmail.com.

Tough Call: How do I turn them around?

by

ComputerRepair

The other day it occurred to me that as a leader, we are judged twice: Once by how we handle success, and once by how we handle problems.

So by now you’ve determined that one of your officers needs to step up their game and contribute more to your rampantly successful organization.  Presuming you still feel they can be a valuable part of your leadership team, this leaves you with two standard options:

  1. Ignore it and hope the situation fixes itself
  2. Violently strike, shake or punch them
  3. Coach them to success

Method 1: Ignore it

Let me know how this works. 

Actually, I’d bet that a fair amount of people are reading this because they’ve already tried this method and realized it never changes.

Method 2: Violence

“We have not yet developed the technology to punch someone over a standard TCP/IP connection.”

– Lodur

So unless you’re a Jedi and can Force Choke someone, this method is sort of a wash, too.

Method 3: Coaching/Wake-Up Call

Part of leadership is motivation, and that doesn’t start and stop with your members.  Your officers need back-up, direction, vision and support on a regular basis.  The only thing that changes is your tactics and means of implementation.

Of course, how this situation came to be and what path you choose from here is largely based on your leadership style.  What follows below likely fits best within an organized style of leadership.  If you run a more chaotic/organic guild, some of this could seem foreign. 

As with any relationship, the GM/Officer paradigm requires give and take.  You both need to know what is expected of each other, so there are no assumptions later on.  It really helps to lay these things out, and to write them down.  Do not presume you will remember all the details later, because you won’t. 

Re-Defining their Responsibilities

Their domain: Are they in charge of all melee, or just tanks?  Do they coach healers outside of the raid, or is that done by the Morale Officer?  In your head, who should be going to them before coming to you?

  • Expectations: What goals have you set for their area of responsibility?  Just “play well” isn’t really a goal.  Zero missed interrupts, DPS that ranks on WoL every night, better cooldown coordination between healers.  These are examples of things they can work on.  Remember, people derive comfort from achieving goals.  
  • Extra Duties: Are they expected to pitch-in on recruiting?  Are they expected to be the sole recruiter for their area?  Do they need to make sure they set aside time to assess your back-ups?  Do they need to contribute to strat development before raid?
  • Rules are there for a reason: Whether it’s your rule or a rule they made up, we are judged by how and when we implement our rules.  If an officer feels like a particular rule (such as talking to players before cutting them, or organising who sits out on which fight, or ensuring loot is distributed correctly) then the situation needs to be examined.
  • Assistance: Tell them what you can do to help them, and when you want/expect to be asked for help.
  • Clarity: Be clear about when and how often you want to update each other.  Some guilds can do this quickly each night, some prefer a weekly officer meeting.  Develop a routine.
  • Desire: Ask them if these are all things they want to do.  Perhaps they are good at some things and not yet ready for others.  If falls to you to decide what they should be handling and when you should be giving them more to do.

Hand-in-Hand with all that, comes your fair share of the culpability.  After-all, it’s your guild, and, even though a lot of GM tasks are intangible, everyone needs to know what you’re doing so they can follow with confidence.

Defining the GM’s Responsibility

  • Tell them what you do for them
  • Tell them what additional things you will do for them now
  • Be clear with what you expect to be a GM-level issue, and what you think is best handled by them
  • Be very clear that your job is to ask questions, and this is just something you will need to do. Nobody should be offended when you make your inquiries.  Afterall, “not checking is not managing”.

Hopefully these tips will give you some good ideas when you find yourself having to coach one of your officers.

Next week: How Cataclysm has changed Guild Structures

As always, please leave your questions/comments/feedback/marriage proposals below.  I love to read them on these rainy spring days while curl up in my official Matticus Snuggie*.

Note: No such product exists.

Tough Call: Are your officers carrying their weight?

by

tc-carryweight-480

Welcome back for another week of cupcakes and snugly puppies. 

Psych!

We both know we’re not here for that, so let’s get down to business. What follows will be Part 1 of an 18-part epic series.  When I am through, angels will descend from on high and carry the compiled works to the Vatican for safe-keeping.  Ages from now, historians will place this up there with The Illiad, Kafka’s Metamorphosis and Hitchhiker’s Guide. 

Hey, a guy can dream right?

Recently we discussed the important roles and differences between the GM and the Raid Leader.  In a 10-man strict guild, you may be able to get by with only have these two officers and some trusted guildies from whom you can expect honest answers.  However, I find that even 10-mans and almost certainly 25-man raiding guilds run better with multiple officers.

In my experience, and from what I’ve been told by other leaders, there often arises a situation where guilds have officers who seem to be the Deputy of Do Nothing.  (As opposed to my own favorite title: Deputy of Awesome.)  I have found that this unique problem can stem from three sources.

  1. Not a Leader – These are the officers who may be great players, may be long-term guildies, but once they become an officer, they don’t really do much other than give their opinion when prompted by the RL or GM.
  2. Fatigued Leader – They were great officers but are not just phoning it in, and are only around out of a sense of obligation.
  3. No-Confidence Leader – They would do a great job, if they thought they had the back-up and the RAA to do it.  As it stands, they feel that the average member has more say than them and may be tired of the squeaky wheel getting the oil.

The Deputy of Do Nothing is a drain on your raids efficiency and on the potency of your leadership team.  As the Captain of this ship, it’s up to you to diagnose this malaise before it spreads to the rest of the crew.*

(* unless, of course, they have no authority while in raid and everyone knows it.  In which case, carry on.)

Not too long ago, I read an article about someone who’s trying to have a “Guild Without Officers”.  While I don’t agree with this idea, I thought the insights below were especially suitable to this conversation:

“I look back on how it used to be, with too damn many officers, all of whom did very little to actually help the guild, preferring instead to treat officership like some sort of insiders club where they could talk amongst themselves in their little clique. I recall making rules and chivvying and cajoling and beating my head against the brick wall that was getting anyone else to step up and take responsibility for anything.”

How do I spot this before it’s too late?
Part of being the GM includes an unwritten commitment to your members that you will make sure the rest of your leadership team has the responsibility, authority and accountability to handle their respective areas.  Therefore, you MUST make sure that among your GM duties you include your due diligence.  Kick the tires, shake the branches and see what turns up.

  1. Talk to your members.  I’m sure you’re probably running heroics, or BGs or whiling away the hours getting that fishing feast while in Mumble with your teammates/members.
  2. Try to recall the last time you had an in-depth conversation with your officer.
    • Did they prompt the conversation or did you?
    • How many solutions did they present to the problems your team was encountering?
    • How many of those solutions have been implemented?
  3. Review how organized/engaged their part of the team is on your forums. If this is something that is important to you or your guild community, your officers should be on top of it.
  4. Lastly, think of what you would be doing if you were in their position.  Don’t think that just because you don’t play healer, you can’t tell a healing officer what to do.  Management skills are not class-specific, and chances are you were once doing their job.  At minimum, you will come up with some ideas to discuss next time you talk to them. At best you’ll see that there are opportunities that you both can capitalize upon.

How do I prevent this?

The first step in preventing anything, is to clearly state your expectations upfront.  After all, human nature dictates that people will operate to the level that is expected of them, and if you don’t set that bar, you’re asking them to decide how to run your guild.  You and I both know that the reason you promoted someone to a position of authority is because you trust their opinion, intelligence, communication skills and reliability.  So the only thing missing is your guidance/structure to tell them how you want these skills applied.

  • Rule #1: Do NOT promote all your friends.
  • Rule #2: DO promote everyone you can trust in your absence
  • If Rules 1 & 2 overlap, you should either make more friends are trust more people.
  • Clearly define the duties of each officer position
  • Grant them authority to do their job as they see fit. Nobody can do a job well if they think they have to ask permission.
  • Agree upon how often you expect feedback from them. Ex: Post-Raid Debriefings, Weekly Status Reports or End-of-Tier strategy sessions.
  • Make sure their position is easy enough for the rest of your team to understand. You don’t want anyone saying “what does he do again” or “he’s an officer just because he’s friends with XYZ, he doesn’t do anything”.  
  • Make sure they are NOT the type of person who settles for just doing their job description.  Good leaders appreciate new talent and new ideas.  Encourage those people who could probably do your job.  They will keep you fresh and your team will benefit.
  • Let them know that it’s acceptable to come to you for help BEFORE a fail.  
  • Establish a routine or set reminders for yourself to remember to review these steps and refine them where needed.

Next week we will continue and discuss what you can do once you’ve spotted the problem.

As always, comments, suggestions and questions are appreciated.  Also, the CD of my stand-up routine is available at the table by the door.  I’m here all week.  Tip your waitress!

Tough Call: Roles – RL vs GM

by

superman-batman

Welcome back for another issue of Tough Call. This week I want to go over a topic that sets the baseline for a lot of what we do and how we can go about building the most efficient raid without imploding the guild.  Before we can get to that, however, I think I need to offer a fair bit of clarification on last week’s topic.

Stay with me, people

Classification is not “name calling”.  In my last post I discussed one set of archetypes (of which there are many) that could be used to sort out your raiders when determining who to take and what areas of your roster to shore up. The objective is never to belittle anyone, because honestly, putting people down takes too much time and energy that I would rather put towards being awesome myself.  As for the intended message, Calaban & Lument had some great points, and yes, X, you are Rudy.

For the sake of simplicity and efficiency, some topics need to be encapsulated.  This was the case last week.  I could certainly turn that 901 word post into 5,000+ words about how to evaluate, coach, refine, recruit, and even alter raid tactics/comps to support the players you have.  The fact that I omitted many of those elements does not mean that I am against them,or that I do not use them myself, just that they didn’t fit into the mold of that post.  Trust me, there’s plenty of ground to cover when it comes to raid management, and I don’t plan to blow my whole load in these T11 pants. 
One thing I will continue to believe in throughout this series is that no leader should ever “leave well enough alone”, or settle for what they already have. Every team needs to get stronger, better, faster, sexier, etc.  Sometimes this happens with teamwork & growth, sometimes a pep-talk is enough, and oftentimes improvement happens by recruiting new blood. For example, we recently got a new priest who’s giving me a run for my money, and my output has increased because of it. Regardless, there would be no point to me writing this column if either of us was willing to accept the idea that you should learn to suffer through the drawbacks of today without making a better plan for tomorrow. 

Lastly, every raider deserves feedback, and that feedback should be honest and constructive.  Some people do benefit from mentoring, some from competition, and some from caliber of shame-filled guilt trip my mother used to lay on me… you pick which works best and run with it.  Regardless, as I mentioned in the comments, your guild should have some mechanism in place to give your raiders this feedback.  I know our guild has a couple different systems that work, and in the future I’ll elaborate on some of this. 

Now, onto today’s topic:

Lessons in Dichotomy // Who runs this joint?

The person/people managing your raid should not be your Guild Leader.

I don’t care how awesome you are as a GM, how amazing your coordination and multi-tasking is, or how long you’ve been doing both roles.  As we continue, I will illustrate how maximum efficiency and stability dictates that the GM not wear the black hat in raid.

Before we break into a list of what each person should be doing, the key assumption here is that the raid leader/officer is a specialist, hired to do one thing and do it well: motivate the team, execute digital dragons and carry back the rewards. 

The job of Raid Management

  • Make the raid as successful as possible
  • Needs to be Honest, Unbiased, and always performance-oriented
  • Make the tough decisions / wear the black hat
  • Assess players based on what they bring to the raid and how well they are executing
  • Manage the PERFORMANCE of the raid
  • Be a clear and present leader at all times during the raid
  • Get progression, achievements, titles, mounts, fame, fortune, super-model girlfriends

The job of the Guild Leader

  • Be the public face of the guild
  • Mediate any issues between guild members (within reason)
  • Take responsibility for the guild’s reputation
  • Oversee / Initiate recruiting
  • Manage the PERSONALITY of the guild
  • Wear the crown, take the heat, buy the drinks at Blizzcon

I know some guilds may be small/close enough that the GM thinks he/she can handle doing both.  I disagree with this because these are two jobs that require different tactics and it’s human nature to have a tough time separating these and/or staying true to the goals of each position. 
Even in a 10-man environment, it is never more efficient to have one person run everything than it is to have separate guild & raid management. This will also decrease/prevent burn-out among leadership.

How the Other Half Lives

Now, this separation also requires a high level of trust/confidence between the two halves.  The raid officer has to trust that there are the right recruitment/retention mechanisms in place to give them the right components for a successful group.  Similarly, since he/she will be handling the fall-out, the Guild Leader has to trust that the raid officer is making the right calls when it comes to who gets benched, who gets invited, who can/can’t main switch, etc. 

Think of it like the relationship between Head Coach and General Manager in pro sports.  These two don’t need to see eye-to-eye on tactics or day-to-day operations, but they do need to have the same objectives and a plan on how to reach them.

Show me an example

A founding member of the guild has lost his drive to raid, but still likes to come and go more-or-less as he pleases.  Further, he uses his relationship with the GM as leverage to get what he wants.  For the Raid Leader, this person represents a liability, as no matter how skilled they are, the risk that they will abruptly stop raiding is ever-present.  If they were given a starting spot, any loot given to this player over another player could be functionally lost at a moment’s notice, and time spent learning a fight with them would have to be adapted or re-learned with their inevitable replacement.  Not to mention the way this would look to other players who may be fighting to prove themselves and break into the starting lineup.

A wise Raid Leader can still utilize this person as a back-up / call-up, borrowing on his skill & experience in the good times, while still prioritizing those players who consistently show up.  Bring the people who have a commitment to making your team succeed, but keep a Rolodex of viable call-ups just in case.

A wise Guild Master will remind the long-term member that the raid team is an ongoing campaign, not something that is won or lost the few times a month this person wants to show up.  The GM will be clear that he expects progression from his Raid Leader, and that not everyone is entitled to raid if they cannot commit. 

Another example

Recruiting!  Without delving into when/how/who to recruit, it’s a very common situation for a Raid Leader to find themself needing to recruit.  Good collaboration between the RL & GM requires that the RL would keep the GM abreast of the development of players within the raid, or at least give them access to any relevant information needed. 

Say you need more melee dps, so you go out and recruit for that spot.  The GM should know WHY the rogue on the bench isn’t being taken over new recruits, so that they can back-up the RL’s decision should the rogue come forward with complaints of favoritism/snubbing/etc.  Similarly, the RL should make reasonable effort to give the GM whatever information he needs to substantiate the roster moves.  Simply “he’s not good” won’t suffice, but “he missed 18 interrupts each of the last three raids” does.

Unfortunately, unlike pro sports, I’ve seen the GM fail the Coach more often than the other way around.  Sometimes this is just simple burn-out, sometimes it’s close-mindedness, sometimes it’s a loss of faith by one of the two people. 

The best advice I can give for longevity is for neither person to say “I can’t….”.  Whether it’s “I can’t recruit another healer” or “I can’t down progression bosses with what you’ve given me” or even “I can’t stand your face”, the only way to maintain success in an efficient raid environment is to always be looking for the next opportunity.  Once you’ve entered into an “I can’t” paradigm, you’re actually realizing that you should have taken action weeks ago, and are now suffering from that inaction/indecision (or worse yet, refusing to realize your responsibility in the matter).  It’s up to you two to always look beyond the current week and stick to your plan you started with.

You do have a plan right?

…please tell me you have a plan.

As always, please feel free to leave any questions or suggestions for future topics in the comments below.  Heck, feel free to leave your favorite bean dip recipes, too.  I need something to do after I’ve cleared the raid and logged off to go watch HIMYM.

Tough Call: Time vs Talent

by

803068_47829639aWelcome back for another episode of Tough Call with me, Viktory.  Today I want to discuss roster evaluation, and specifically, two factors to look at when examining your depth charts.

You do have a depth chart for your raid positions right?

… Please tell me you have a depth chart for your various raid roles and you’re not just bringing whoever shows up first …

(For anyone who doesn’t get the sport analogy, a depth chart basically lists each position and ranks the players have that position in order. You have your go-to guy/gal, the back-up, the back-back-up, etc.)

Editor’s Note: Before we go any further, if you are of the steadfast opinion that nobody deserves to be benched, or that your best friends deserve a spot in every raid, you will likely want to stop now.

Okay, so let’s say you’ve got your full raid roster in front of you and you’re trying to figure out who’s going to make the cut and get a stable spot in your 25-man raid. Obviously you have certain roles you need to fill (tanks, healers, melee, ranged) and certain skills you need players to possess in those roles (AoE heals, interrupts, soak tank, kiting, etc).  You’ve got a lot of criteria to look at when deciding who is THE BEST player for you to bring to your raid. 

(Remember, “take the player, not the class” implies “take the best possible player”.

One of the more common downfalls I’ve seen leaders suffer, and one of the worst traps I’ve seen players try to spring on their Raid Leader, is the substitution of Time for Talent/Aptitude.

A few weeks ago I told you that “preparation is king”, and while that still holds true, by now you should be seeing who actually knows what’s expected of them, and who’s just reading a script.  In fact, if we think of raiding like a foreign language, we can come up with three archetypes.

Native Speakers

Some players have a lot of natural talent.  These players are the mage who always does crazy DPS and makes it look easy, the guy who plays a utility spec and still manages to do competitive DPS, the healer who can instinctively spot issues with the raid and react in a clutch moment (see Matticus in his prime*).  Everyone loves to have these guys around, especially when they don’t act entitled or get lazy because they think they’re too good to need to put in the grunt work.

*Note: I said “see”, not “listen to”.  He’s a horrible story-teller.

Fluent Professionals

Other players have to work hard to produce the output you’re looking for.  Think Rudy here, the guy with a lot of heart who does his homework and gives you the results you’re looking for.  As a leader you know that he’s always reading up on the relevant websites, maybe talking to other progression raiders who play his spec, and is constantly seeking ways to improve.  Through their effort, they are just as good, or nearly as good as your top tier guys.  The key here is that you DO see them improving, carrying their load, and not causing wipes.

I think a “perfect raid” is filled with a solid mix of these two personalities.  However, we need to minimize or weed-out the last group:

Tourists

The personality to absolutely avoid is the “trained noob”, to borrow a term from Pure Pwnage.  These are players who bring sub-par skill, spend a lot of time logged on, but instead of learning and absorbing their class mechanics, they may have only learned the accepted boss strat.  These are the guys at the cafe with their French-to-English dictionary out, trying to look-up each word the waiter just said, because they were not expecting that response.

Players like this will present a liability to your raid anytime things deviate from the norm.  Get bad RNG on a boss, or timers that don’t line up with the abilities the boss is using, and you can bet that these players will be toast.  Customize the Tankspot strat to meet the capabilities of your raid, and you just may find these guys out of position and thoroughly confused.

Don’t be fooled by people who have a lot of time and very little aptitude.  It all comes down to who can get the job done. 

It is up to you, as part of raid management, to spot the player who may have raid knowledge, but not raid awareness, and figure out a solution.  Determining who’s a “fluent professional” and who’s just a “tourist” will help boost your raid output (and morale) immensely. 

If it’s my call, I’d put that person as far back on my depth chart as possible, only bringing them when I must class-stack, or when other players are missing, and I’d definitely keep recruitment open until I found a good core that was made up all “native speakers” and “fluent professionals”.

Please leave any questions or suggestions for future topics neatly stacked in the comments below.  Shoot, if you’re so inclined, leave details of your most epic knitting accomplishment, too. Those are always cool.