Not to put too much pressure on the IT guy you’re trying to hire, but here are 10 MORE things your IT guy needs to know how to do.
You can check out the first 10 here.
Ready to hire right? Check out our list after the jump…
1. Back Up
If this person doesn’t know how to back up files (and test the back ups) then this person doesn’t deserve to be be paid staff. Losing your data is heart breaking (and for those who have, you know what I’m talking about).
2. Documentation
Documenting the IT environment, the processes, and what has happened with “whatever” is happening back there is critical. This person needs to know how to do it and do it well enough so that if he finds himself talking to St. Peter at the Pearly Gates then someone can pick up the slack for him without problem.
3. Overtime and On-Call
Working in IT is synonymous with overtime and working at night. This person, if they haven’t understood this principle by now, needs to be aware that being on-call sometimes requires doing stuff at strange hours of the day (and by that I mean ‘night’).
It’s tough to be in IT, but that’s their burden to bear!
4. Cabling with Style
Running cables seems obvious but it’s really an art form. Labeling them right, color-coding them, and more is serious business. Long term it’s invaluable for fixing problems.
5. Energy
They don’t have to be geniuses knowing everything there is to know about kilowatts and more but they do need to know the basics of electricity and management, especially heating and cooling.
6. People Management
IT needs to know how to manage people, and not just in a “managerial” type position but managing relationships well. Not a “people” person? Good luck with that.
7. Project Management
This person needs some basic project management skills or they’re going to drown themselves in chaos.
8. Fiscally Responsible
This person needs to know how to manage a budget and know when to save and when to spend. He/She also needs a backbone enough to ask for more money when necessary. Things like “Operating Costs” and “Capital Projects” should be understood by the person (and the differences between the two).
9. Willing to Learn the “Business”
There is more to an organization than just Information Technology. This person needs to be willing to engage with the rest of the “business” and not just hole-up in the basement. Their ability to provide the most effective solutions will require understanding of the rest of the organization.
But you knew that already.
10. Spiritually-Minded
This kind of goes without saying but your IT guy needs to be spiritually-minded, trusting God with all things including info-tech.
I thought I’d mention it anyway.
Gedy says
What an awesome post. This is so true!
John Saddington says
🙂 thanks!
Yohan Perera says
I strongly agree with you in the last point (Spiritual…). But not on 3rd point (overtime…), at least not always.
John Saddington says
yeah. on-call. ugh.
Chris Dattilo says
Good continuation of the list, but like last time I have an addition. Can you tell I’m working with a lot of IT guys:)
Humility – maybe it’s because I’m a woman. But I find I often get bluff and bluster about IT stuff that isn’t backed up by actual knowledge. When things aren’t working I get “the node scripting is hooking into depracted PHP calls…” gibberish. When what they really mean to say is “I have no idea what’s going on, I’m going to sit down and try to figure it out.”
This trait also exhibits itself in an aversion to calling support (of any kind). Women have no problem asking directions, and asking for them to be repeated. My son and husband on the other hand love to, if forced to ask directions, nod like they know exactly what’s going on, but then drive off in the wrong direction. This seems to work with IT (many times, not all times).
Humility to say “I have no idea, but I’m going to try and figure it out“ or “I’m going to call support make sure I’m understanding this correctly, I’ll get back to you.”
John Saddington says
hehe. great perspective, and YES on the humility side…!!
Scott Fillmer says
Both the first 10 and the second 10 were great lists of what an IT person should be able to do. I am a little shy on my scripting skills but I can get around in SQL and write html/css/php so maybe that makes up for it 🙂
Aaron Melton says
Correction:
You really should make that an offsite backup.
Gene Simonalle says
Well,
That’s a great list of some skillsets needed for IT in a church. But I don’t think those are ‘entry level’ skills, but what makes a decent team lead for a medium sized church.
How have you communicated the value of a well rounded and skilled IT team member to a church finance board? As a senior IT guy working outside the church, I know that I am making more than two pastors put together–and while the market may bear that cost the finance committee doesn’t!
It seems like what Paul said in 1 Cor. 9 still applies, that he is worth his compensation for his labor for the gospel, but there are those against it.
What have you seen in your experience?
Gene
John Saddington says
gene, thanks for dropping by!
that’s a great question. facts and figures help, but sometimes it’s a hard sell. overtime i’ve won people over. also, sharing other stories and bringing “testimonials” have helped from trusted partner orgs and ministries.