Jump to content

Recommended Posts

Posted
27 minutes ago, HyperTech said:

Completely agree. To be honest, the issue in question comes more from the MAT. I suppose they don't want to open themselves up to potential issues when they already have an SLA in place. The MSP would be open to it, as I know they support other schools/MATs and collaborate with the in-house teams on a closer level. But ultimately, it isn't their decision to make. As others have said, when you are a "Doer" it is frustrating having to wait hours for a print driver to be installed.

 

I suppose, as you mentioned - it just creates a unnecessary "barrier" to workflow. I think the school finds it especially hard, as they have had an in house technician for nearly 15+ years.

Well said.  Some of it is senior leadership politics, but from an MSP perspective we also have to retain sensible control of systems we’re responsible for.  If something goes wrong — even if caused by others — it still lands with us and can jeopardise relations.

 

Most school-employed staff I’ve worked with are excellent (I've both line managed and directly employed to work for our MSP) but there are occasional “gung-ho” moments where good intentions plus partial knowledge can cause bigger issues.  That said we’re all human and mistakes happen.

 

It’s a balancing act.  I don’t support restricting access to the point jobs can’t be done (and the end users ultimately suffer), but the right level of access will always depend on the school, the people involved, and the MSP’s accountability.  Again, rather depends on the politics that are at play.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...