Last year, a new evaluation system was instituted at the University to help both managers and employees with the evaluation process. Some of the goals included:
- Creating a system that was more objective.
- Creating a system that rewarded people based on the work they did and its quality.
- Creating a system that helped both workers and managers agree on clearly defined objectives.
Now in its second year, the ADP is becoming a bit more refined, and thankfully we didn’t have to do a full self-evaluation like we did last year. We do, however, need to provide supporting documentation for our ADP. The goal of this is to let our evaluators know what we did this year; they might have a general idea, but they might also have forgotten some things. We all want to avoid a situation where our evaluation score is low and we are told that, “If only you had done X, you would have gotten a higher score!” This might happen in a situation where you didn’t know you needed to do X, but it might also be that you actually did do X, only your evaluator didn’t know… and now it’s too late to change the evaluation because it has moved up through the great bureaucracy and been dutifully stamped and filed.
So, we file supporting documentation regarding what we have done this year. Not everything we have done, by any means, but the notable high points that we want remembered and considered in our evaluation.
When I describe what I do for a living, I first have to say that I work in the Computer Services Help Desk at Missouri State University. Within the context of IT, a Help Desk is generally just a call center, or a repair shop: help people with software, answer questions, replace broken computers, etc. That’s certainly a part of what we do, but my job rarely involves that kind of work. My second statement is always something along the lines of:
I don’t do much of the repair work anymore. Instead, I spend a lot of time researching and writing, trying to find new solutions to help people work more efficiently (specializing in open source solutions) and I also do a lot of web development. I maintain our unit’s web servers, our wiki, and I do a lot of speaking at conferences or just sessions at our University about different topics.
Since I put the time in to outline my year’s activities, I thought I’d post them here to further clarify on this. It’s nothing special, and most of it probably won’t make sense to someone who doesn’t work here, but if you’ve ever wondered what I do, this is it. It’s over-simplified and doesn’t go into any detail, so a project that consumed more than three months of this year is condensed into “Experts wiki went live in June,” but you get the idea.
Our three objectives for Centralized User Support Specialist this year are:
- Participate and contribute to the successful implementation of the ERP system.
- Maintain competency and currency through professional development. (PDF)
- Provide accurate and appropriate training and documentation. (PDF)
At this time last year, I thought that 2008 was going to be a breeze. I’d had a really busy year, and I was looking forward to a nice, easy coast downhill to 2009. Instead, I ended up doing about twice the amount of work I did last year, and I did it more efficiently in less time.
Looking forward, I can’t begin to imagine what next year will hold. The training labs have been built and in use for some time. The wiki is up and stable. The Luminis portal went live last Wednesday. There’s obviously still work to do, but it’s maintenance, not new projects. What can they throw at me next year that could top this year’s challenges?
And yet, I was wrong before. I have a feeling that 2009 is going to be very interesting indeed.