3 of 10Image
2. Time factor
Your emergency may have to wait until the outsourced IT department can get someone on the job. If it involves a site visit, those drive-time issues may strike again. You're also subject to the outsourcer's workload, and many factors can cause your emergency to be pushed back. So it's out of your hands, whereas had IT still been in house, the emergency could have been dealt with immediately.
Man in server room
3. Network and systems familiarity
When your IT is in house, the tech staff know the systems and networks really well. They should, because they probably built them. So they can probably keep it all running more smoothly and solve emergencies far more quickly. Of course, even an outsourced IT department can become expert with your systems and networks, but there will be a learning phase, as well as the possibility that a lack of documentation will cause serious issues.
4. Employee relationships
I've often come across problems in relationships with outsourced staff, although others may not see this point as an issue. In-house IT staff know one another and know how to interact with users.
With outsourced IT, employees may not even get the same engineer every time, which can prevent relationships forming in the way they might do with your own tech team. Of course, you can build relationships with outside staff, but I have seen issues — even, in one case, an engineer being banned from working with a certain client.