Our small IT team handles a large user base, a heavy ticket load, projects, and responsibilities from another team. Some requests belong to a business process that may be automated later, while users often bypass the portal and contact us directly, including after hours.
Leadership has been reluctant to enforce support boundaries. What can we realistically do ourselves to make the workload manageable?
Put the demand and capacity problem in front of your manager in writing. Track incoming tickets, the backlog, time spent on that business process, project work, and interruptions for a few weeks. Estimates are fine if you label them as estimates.
Then ask for a priority decision rather than just asking for more help. For example, if support takes most of the available time, which projects should move, and who owns the business process until automation arrives? Keep a record of the answer and update it as the backlog changes. You may not get more staff, but at least the tradeoffs are visible instead of being absorbed through extra hours.
Make the ticket path easy and use the same response every time. If someone walks up with a nonurgent issue, help them submit a request instead of fixing it on the spot. Keep the form simple enough that people can actually use it, then triage it on your side.
You could also ask for approval to send a short message explaining where requests go and how they get prioritized. Frame it as making sure requests are tracked and reach the right person, not as a warning to users. That may be easier to approve than a policy with penalties.
6y~mortarclip_293:
Make sure there is a clear route for genuinely urgent issues too. A portal-only message won't help much if nobody knows what to do during an outage.
Don't assume you can enforce a strict ticket-only rule when leadership has said people may approach IT however they want. Agree with your manager on what you can consistently do, such as logging direct requests and prioritizing them alongside other work. Avoid rejecting tickets or escalating users as a new policy without approval. That can leave you carrying the conflict alone.
The personal phone calls and people interrupting private spaces are a separate issue from ticket hygiene. Document specific incidents and ask your manager, HR, or the appropriate workplace contact for a clear response. You can also stop using your personal number as a support channel and direct people to the approved route, subject to any actual on-call arrangements.
If meetings involve sensitive security information, raise the repeated interruptions as a confidentiality risk as well as a distraction. Ask for a practical arrangement, such as a private room and an agreed way to reach the team for emergencies.
Automation next year doesn't solve the queue now. Break down that business process and see whether the owning team can take any part of it back, or whether a simpler temporary workflow would reduce the manual work. Even a rough estimate of the hours and equipment costs involved gives their manager something concrete to consider.
If leadership won't make a decision or provide support after you've documented the impact, looking at other jobs is a reasonable fallback. You don't have to wait for things to get worse before exploring options.
Answers are reviewed before publication.
Kavrin.8s:
Include work that never becomes a ticket too. Otherwise walk-ups and direct messages can make the reported demand look smaller than it is.