Your IT technicians are overloaded.
The tickets just keep coming in. Strategic projects are being pushed to the back burner. And your backlog seems to be growing instead of shrinking.
If this sounds like your IT department today, the obvious conclusion is that you need more IT staff.
And you might.
But before adding headcount, it's worth asking yourself a few questions. Your answers can help determine whether your district truly has an IT staffing problem, or whether your team's technical capacity is being consumed by something else.
What Is Technical Capacity?
When people talk about IT capacity, they often think about the size of the team and the number of hours available in a workweek.
But technical capacity is something different.
It's your IT team's ability to perform the technical work that keeps the district moving forward: resolving issues, completing projects, improving systems, strengthening cybersecurity, supporting instruction, and helping staff use technology effectively.
Technical capacity is your IT team's ability to perform the technical work that only IT can do.
This is the work your IT team is uniquely equipped to perform.
The challenge is that not every hour is spent this way.
At least some of your team’s time is consumed by the manual work surrounding support rather than the technical work required to resolve an issue. This Hidden Work quietly reduces the capacity available for the projects and initiatives that matter most.
Before deciding you need more staff, consider these five questions.
1. How many support requests arrive outside your standard process?
Think about the requests your IT team receives in a typical week.
How many arrive through email, Microsoft Teams, phone calls, hallway conversations, or someone stopping by the office?
When people need help, their natural inclination is to use whatever method is most convenient in the moment. But when requests arrive outside the district's standard support process, someone has to determine what to do next.
Should this become a ticket? Does it belong to another department? Is there enough information to begin working on the issue?
Each request may only take a few minutes to organize, but those minutes add up. Before anyone begins solving the technical problem, your team is already spending time capturing information, deciding where the request belongs, and ensuring it doesn't fall through the cracks.
2. How many requests land with IT that belong somewhere else?
In your district, how many of the requests that come to IT actually require IT support? How many should actually be managed by Facilities, Finance, HR, Curriculum, or another department?
Teachers and staff aren’t always clear where to go for help. When they're unsure, IT often becomes the default destination.
Every time this happens, someone on your team must diagnose the misrouted request, redirect it, explain who owns it, or connect the employee with the right department.
Each interaction may only take a few minutes, but that’s time taken away from solving technical issues.
If this happens frequently, your team could be spending more time being coordinators than technicians.
Read the blog to learn why misrouted requests are a symptom of a bigger support problem.
3. How often is IT answering the same questions?
Every district has questions that seem to come up over and over again.
“How do I connect to wifi?”
“How do I access this application?”
“Why can't I print?”
Answering these questions may feel like legitimate support work. But when your team gets hit with the same questions over and over, their technical capacity is spent providing the same answers instead of solving more complex problems or completing strategic work.
Any one of these questions is easy to answer. It's the cumulative effect of having to answer them hundreds of times throughout the year that quietly steals your team’s technical capacity.
4. How much time is spent gathering missing information?
If your IT team’s experience is like most, they regularly receive requests that lack all of the information needed to get started.
When requests arrive without all of the context, someone on your IT team has to ask follow-up questions.
“Which classroom?”
“Which device?”
“What error message are you seeing?”
“When did it first happen?”
Those missing details are necessary, and it takes time to gather them. The more time your team must spend collecting necessary information, the less time they have available to resolve the issue itself.
5. How often does IT coordinate issues that are shared responsibilities?
Some requests legitimately require IT involvement, but IT can’t resolve them alone.
A classroom move could require coordination from Facilities.
An application access issue could require Curriculum approval.
An onboarding issue could require HR assistance.
Even when another department owns part of the work, IT often becomes the coordinator because technology is a part of so many district processes.
Collaborating with other departments, gathering updates, and following up on status are necessary. But IT should not automatically own every coordination task simply because technology is involved. When it does, less technical capacity remains for the work only IT can perform.
What Do These Questions Have in Common?
These issues may seem unrelated, but they all point to the same underlying problem: a fragmented support experience.
When requests arrive through different channels, reach the wrong teams, lack critical information, or require manual coordination across departments, someone has to bridge the gaps. That additional effort often falls to IT.
We call this Hidden Work.
Hidden Work is the additional operational effort required to compensate for fragmented support experiences and disconnected systems.
Hidden Work isn't the same as unnecessary work. In many cases, it's an essential part of helping employees get the support they need. The problem is that most districts don't recognize how much of it exists, or how much technical capacity it quietly consumes over the course of a year.
Do You Have an IT Staffing Problem or a Hidden Work Problem?
School districts absolutely face IT staffing challenges. And hiring more staff may be the right decision.
But it's worth considering whether your district's biggest challenge is IT staffing…
Or whether Hidden Work is quietly consuming the capacity of the team you already have.
If a significant portion of your team's day is spent managing informal intake, rerouting requests, answering repetitive questions, gathering missing information, and coordinating work across departments, adding another technician may simply create more capacity for work that doesn't require technical expertise in the first place.
These are symptoms of a Hidden Work problem, not just a staffing problem.
Discover How a Better Support Experience Reduces Hidden Work
Before investing in additional staff, it's worth understanding how much Hidden Work exists in your district and how much technical capacity it's consuming.
Hiring may be part of the answer. But reducing the manual work and coordination surrounding support frees up your existing team to spend more time on the technical work they’re uniquely qualified to perform.
Want to see what a better support experience looks like?
Learn how schoolAgent makes it easier for teachers and staff to get help and for IT teams to reclaim their time.