![[identity profile]](https://www.dreamwidth.org/img/silk/identity/openid.png)
After spending far too many years supporting large organisations, I have compiled a list of rules which seem obvious, but which managers and other staff have to be constantly reminded of in one form or another. Here's the distilled crack:
OTHER TEAMS
1) We are not here to do the work of local office management, administrators, trainers, local technical staff or other IT teams. They have staffing budgets for a reason.
2) We are not a call logging or secretarial division for other teams.
3) We are not a dumpster for other teams to throw unknown jobs into. ESPECIALLY when those jobs are the responsibility of the team in question.
4) Corollary: We are not a switchboard.
5) We are not here to provide ongoing workarounds for other teams’ incorrectly or inefficiently coded or configured hardware, software or procedures while said teams sit around on their butts for YEARS doing nothing about the problem.
OTHER STAFF
1) We are not responsible for training staff, either in basic computer skills or how to do their jobs.
2) We are not here to take up the slack for lack of correct staff training.
SCOPE
1) We will not provide more than basic troubleshooting for equipment or services we do not have access to ourselves or have never heard of.
2) Just because a piece of equipment is beige or uses electricity, this does NOT mean that it is on our list of supported hardware.
MANAGING OURSELVES
1) We are not in the business of employing staff purely to cover inefficiencies, whether our own, other teams’, or those of management. I don't care if some manager wants to empire-build.
2) Analysts are not to be expected to jump through inefficient extra hoops at the whim of upper management, especially when there is no good technical reason for it.
FUNCTION
1) We are not a ‘friendly face’ for IT, or any other form of managerial fluffiness. We are a technical troubleshooting and repair division, not your secretaries or assistants.
OTHER TEAMS
1) We are not here to do the work of local office management, administrators, trainers, local technical staff or other IT teams. They have staffing budgets for a reason.
2) We are not a call logging or secretarial division for other teams.
3) We are not a dumpster for other teams to throw unknown jobs into. ESPECIALLY when those jobs are the responsibility of the team in question.
4) Corollary: We are not a switchboard.
5) We are not here to provide ongoing workarounds for other teams’ incorrectly or inefficiently coded or configured hardware, software or procedures while said teams sit around on their butts for YEARS doing nothing about the problem.
OTHER STAFF
1) We are not responsible for training staff, either in basic computer skills or how to do their jobs.
2) We are not here to take up the slack for lack of correct staff training.
SCOPE
1) We will not provide more than basic troubleshooting for equipment or services we do not have access to ourselves or have never heard of.
2) Just because a piece of equipment is beige or uses electricity, this does NOT mean that it is on our list of supported hardware.
MANAGING OURSELVES
1) We are not in the business of employing staff purely to cover inefficiencies, whether our own, other teams’, or those of management. I don't care if some manager wants to empire-build.
2) Analysts are not to be expected to jump through inefficient extra hoops at the whim of upper management, especially when there is no good technical reason for it.
FUNCTION
1) We are not a ‘friendly face’ for IT, or any other form of managerial fluffiness. We are a technical troubleshooting and repair division, not your secretaries or assistants.