Slashdot Mirror


First Thing IT Managers Do In the Morning?

An anonymous reader writes "When I was a wee-little IT Manager, I interviewed for a position at an online CRM provider in San Francisco, a job I certainly was qualified for, at least on paper. One of the interviewer's questions was 'What is the first thing you do when you get to work in the morning?' I thought saying 'Read Slashdot' wouldn't be what he was looking for — so I made up something, I'm sure, equally lame. I didn't get the job. But the question has stuck with me over the years. What do real IT and MIS managers do when they walk in to the office in the morning? What Web sites or tools do they look at or use the first thing? Remember, this is for posterity, so please be honest."

4 of 584 comments (clear)

  1. Check the sev 1s by MosesJones · · Score: 4, Informative

    The first thing you do every morning is check the sev 1 problems that have occurred when you are out. Next off you look at the 24 hour report to see what is out of whack. Anything odd you follow up on. If everything is fine then you have a cup of strong coffee and wait for the first dumb question of the day.

    Deal with the disasters first, after that everything in the day is a lightweight bonus.

    --
    An Eye for an Eye will make the whole world blind - Gandhi
  2. Re:Coffee machine1st thing I look at by paganizer · · Score: 5, Informative

    yup. first thing is coffee.
    after that, check the whiteboard on the door to my office to see where the problems are; when you have 6000+ systems and a cluster in each state and a few overseas, their is always a problem somewhere.
    If anything is on fire, head to level 2 and check with the nightshift to see what the heck is going on before they escape.
    If the fire is local, walk down to the NOC and see whats up, put out fire if appropriate. if it's in Dallas or Seattle or Guam, see the status of the local admin on the ticket queue, get on the phone if I see something they don't; start a team re-tasking operations at the site if it looks like it's going to take a while; downtime is not an option.
    if it is Biz as usual, walk in, fire up the computer, and check the infrastructure; check the queue on SMS to see if anything major is being pushed today, basically just look around to see if there is anything that is going to require me to earn my salary.
    if everything is smooth, or being handled, check e-mail; then, slashdot until the 10AM meeting.

    sometimes I wonder why I retired. then, I remember. Paperwork sucks.

    --
    Why, yes, I AM a Pagan Libertarian.
  3. ok seriously by cecil_turtle · · Score: 4, Informative
    I've read most of the posts above, and below is my answer. I don't drink coffee and if I eat breakfast that day I do it before work. I don't read Slashdot / etc. while at work, I do that on my own time after I get home. Also the full question was "What is the first thing you do when you get to work in the morning?" (emphasis mine) - so there goes the answers like "shower". We'll also assume that this is a normal work day and an automated monitoring system hasn't paged me with a problem causing me to drive in early and fix it. We'll also assume I didn't just get back from a vacation.

    OK, now with all the qualifiers out of the way, here's what I do first thing:
    • Check voice mail. I will only normally have 1 or 2 at the most unless I've had days off, and I also get voice mails via email so it's likely I already heard it.
    • Skim emails. Again I keep tabs on email even when not working so there's not normally a ton of new stuff, but I like to look over all of the emails, delete spam, and read important things first or things I've been waiting to hear back on. This is not when I deal with less important emails or write lengthy emails to people.
    • Check monitors / logs. For me this means disk space monitors, MRTG bandwidth reports, backup statuses, etc.
    • Check my short-term to-do list, normally created the day or two before that gets updated a couple times per week. Start on a project or delegate a project to a co-worker.
    • If I'm in a waiting stage on all of my short term projects (waiting for parts to ship or waiting on a vendor or waiting to hear back from upper management) then I will make an effort to follow up on those items to help move it along (check tracking numbers, send "reminder" emails, etc.).
    • If all of the above is taken care of, move on to the long-term project list.
    My last comment is that some people have very specific ideas of what an "IT Manager" does or should do. Keep in mind that's a very broad term that will vary from organization to organization, mostly depending on the size. Somebody above made a distinction between an IT Manager and a System Administrator, but when your whole team is two people (like mine) those things don't make much difference. Maybe in some organizations IT managers don't get paged, or don't deal with backups, or whatever, but in smaller organizations the manager is also a staff member.
  4. Re:Coffee machine1st thing I look at by Anonymous Coward · · Score: 4, Informative

    If I had a coffee pot at work, that would be the first thing to tend to. Otherwise, my morning ritual is similar to parent post:

    1. Attach my personal USB drive and boot computer
    2. Check voice mail messages while computer is booting, look for fires
    3. Check company email, look for fires
    4. Check incoming faxes. No fires there, but sometimes directives from On High
    5. Check physical mail box at Front Desk.
    6. At same time, check company grapevine through the Front Desk girls. Find out if they need any favors that I can do (cuz the grapevine works on favor exchanges, and they are key people in the grapevine)
    7. Check Internet news headlines. I use a custom portal with Yahoo and another with Google. I check world news, US news, metro news, Reuters technical news, and slashdot. I'm scanning these fast, looking for things that might be relevant to my job, to the company, or to my cow-orkers.

    This ritual takes 10 to 15 minutes, and more than pays for itself by decreasing the number of surprises I run into during the rest of the day. On the average, the part that takes the longest is checking the grapevine, because these kinds of informal networks need to be nurtured.

    By 20 minutes into the day, I know what is important for that day and can discuss my priorities with my boss. Sometimes that discussion has included bargaining for a couple of hours to research something that turned up on Slashdot that might be important to our work.