Past !votes--Please note that many of the "could not parse/didn't !votes are actually non-votes per my notes below. I probably actually made no votes on those RfA's but only updated the format or something.

My Criteria

There are very few specific criteria that I expect to see out of a potential admin candidate. Most of my criteria are abstracts:

Other factors:

How I Review Candidates

Unless the candidate is clearly not qualified, I will generally spend 1-4 hours reviewing a potential candidate before !voting on the candidate. If I am going to nom them, it will be 2-6 hours! Reviewing a candidate is more of an art, than a science, but I will generally approach my review along the following lines:

RfA Questions

While the basic 3 questions are important, I generally do not pay too much attention to generic questions asked of the candidate. If there is a specific question asked about a specific issue for a candidate, then I will read those questions with interest. Similarly, the only time I ask questions of a candidate is if I am truly sitting on the fence and want the candidate to convince me to support them. Sometimes the best way to do this is to admit fault or that an error was made.

How I !vote

Strong Support I rarely give out strong support. Strong Support means that I am familiar with the candidate and have spent a lot of time reviewing them. Generally Strong Support is reserved for admin coachees---but that is more because I've spent scores of hours reviewing their edits. A strong support means that I've known the candidate for months AND have given them a complete review and not found any problems. If you are a candidate I first learned about via RfA, then you won't get a strong support. Strong support is reserved for people whom I have grown to trust over time and had that trust reaffirmed via a detailed review.

Support In order for you to get a support it means that I have spent 1-4 hours reviewing your edits in detail and didn't find anything that I couldn't live with.

Weak Support usually means that I was too lazy to give a complete review of the candidate. If that is the case, I will indicate that is the reason why. I give weak support when nothing jumps out at me, but I've probably only spent an 20-30 minutes reviewing them. I use weak support because I don't want others to rely upon my review. It could also mean that I am overall pleased, but that there were some concerns.

Neutrals are fairly rare. They are usually an indicator that there were both plusses and minuses to the candidate. It is also a strong indicator that I WANTED to support and saw something that I didn't like. Or a candidate where reason said I should oppose, but something made me want to support. It is usually used when logic and emotion are at odds over a specific candidate.

Weak Oppose usually means that you don't have the experience that I am looking for (length of tenure and/or number of edits) but that you are otherwise a solid candidate. Weak oppose may also be based upon a gut or bad feeling. Generally, I won't spend too much time justifying a weak oppose---I figure it's a weak oppose for a reason.

Oppose usually means that you are failing in some way. I will generally write out a detailed explanation as to why I give an oppose. I will often spend more time on a candidate than when I support.

Strong oppose I only give this where I honestly believe that passing the candidate would be a mistake. I will never give a strong oppose without giving firm reasons for the !vote and diffs/examples supporting the position. I will generally spend the most time reviewing candidates with a strong oppose as I want to ensure that it is appropriate.

As I spend so much time (1-6 hours) reviewing candidates, I don't always vote on every candidate. The only time that I generally !vote on candidates is if I am one of the first 10-20 !voters. The only exception is if the candidate has a close/contentious RfA. In other words, if the candidate is at 40/1/0 I probably will not review the candidate. If, however, the candidate is at 40/15/10 I probably will. I do not !support to pile on supports. If I support, it is because I reviewed the candidate myself and feel comfortable doing so (weak supports may be an exception). Thus, I rarely !vote where the outcome appears to be set one way or another---it's not worth the time. Because of this, I probably oppose a larger percentage of the time than I support---most of the candidates who are qualified will pass without my support. I tend to partake in candidates who are less well known.


Nominees

When I nominate candidates, I will not !vote until the last day of their RfA (or if they reach the 100 milestone). I do this because nominator support goes without saying and I always think that it is silly to take pride in beating the nom. Beat the Nom support has traditionally meant that the candidate was so strong that they beat the nom. As I want my candidates to be as strong as they can, I take my time so that EVERYBODY beats the nom!

Ok, in all seriousness, I take my time because I think people who take pride in beating the nom are often short-changing their investigation into the candidate and I really do think "beat the nom support" is kind of silly. It no longer means that the candidate is so strong that you can support on name recognition alone---for many it is simply a goal to "beat the nom." Yes, this is a littly pointy, but in a non-destructive manner.

Plus, it shows faith that you believe your candidate will pass without having to stack the deck from the getgo.