In the beginning... of a new IT department


(Jonathan LaMaster) #1

I’ve recently been asked to be the first full time member of a newly created IT department for a church. 2 campuses with aprox 3k weekly attendees.

They currently have a service contract with a IT support company for more complex need and a employee who splits time between HR duties and IT/Helpdesk. They have Arena ChMS, On Site servers, IP Telephony, etc.

What would you say the focus of your attention would be for the first 3 months? 6 months? 12 months?


(Alex Conner) #2

I recently took on a role like this, where they had on-site folks doing Tier 1 type work but everything more significant was outsourced. I started out with some pretty solid goals on what I’d like to accomplish, but not long after getting deeper into the environment did I find out that I discovered there were some pretty significant and severe issues with the infrastructure that the previous service provider had simply been band-aiding over and over again. This led to things being in a really terrible place (like password changes and mailbox creations wouldn’t stick due to severe AD corruption).

I think probably the best thing you can do to start with is listen to your users and try and establish patterns. Try and understand the biggest pain points and once you’ve been in the mud for a month or so figure out what you can attack with the budget you have and what folks are going to have to live with for a while longer. Try and dig into any recurring issue and find the root cause. Don’t fill your time doing menial tasks just to look busy. Build the processes that they won’t have in place for requesting help, equipment, etc. and make sure you’re on course for best-practices like standardization and license compliance.


(system) #3

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.