K–12 Technology Leaders Are Doing Too Much: 3 Ways to Reclaim Strategic Focus

• By Matt Holley, M. Ed., Dr. Chantell Manahan, Dr. Matthew X. Joseph
• 08/12/26

In K-12 education, the phrase "other duties as assigned" is often met with a knowing smile and a heavy sigh. For district technology leaders, that line in the contract might mean troubleshooting a network issue, advising on curriculum tools, supporting cybersecurity planning, attending a cabinet meeting, or helping record a fifth-grade musical. The reality is that technology directors touch nearly everything that happens in a school system. Not consulted on half of it. Still accountable for all of it.

There is hidden power in wearing multiple hats. When you sit at the intersection of instruction, operations, and security, you aren't just a "tech person", you are a lifelong learner with a front-row seat to everything happening in the district. Technology leaders are not only supporting schools, they're helping shape how they function, and in the process have become true educators, trusted because they too help shape student success.

However, when every hat stays on your head all the time, the role becomes unsustainable. Everything breaks and everyone blames IT. Everything works and nobody notices. If systems depend too heavily on one person, progress stalls the moment that person steps away. The challenge, then, isn't eliminating responsibilities; it's managing them in a way that builds capacity instead of dependency. 

The challenge isn't eliminating responsibilities; it's managing them in a way that builds capacity instead of dependency.

Here are three strategies K–12 technology leaders can use to navigate their many duties without losing strategic focus, influence, or sustainability:

1) Assign Clear Ownership Across District Technology Work

In many districts, technology leaders inherit responsibilities simply because no one else claims them. Over time, this creates a familiar pattern: Everything becomes shared, and nothing is truly owned. Because when a task is everyone's job, it's no one's job. Six departments buy six platforms. Nobody calls IT. Then IT owns all six integrations.

Clear ownership is one of the most effective ways to reduce overload. Whether it's data reporting, device management, or digital curriculum, every initiative needs a named owner with clearly defined responsibility and authority.

This doesn't mean stepping away entirely. Technology leaders will always play a supporting role across departments, but support is not the same as ownership. Strong leaders build others up to carry that ownership, and as a leader, that job shifts from doing the work to coaching the person who does. The goal isn't to do less work. It's about distributing the right work to the right people and empowering them to lead it.

2) Define the Role of the K–12 Technology Leader

In technology, silence is often the only feedback given. If everything is running smoothly, people assume the job is easy. When something breaks, they assume we aren't working. 

To navigate the "other duties" trap, we must clearly communicate what we do, and what we don't. If no one understands our role, they can't respect its boundaries.

Technology leaders need to be clear not just internally, but across their school communities about what they do, what they prioritize, and how work flows through their team. If the community doesn't understand the complexity of data privacy agreements or that the FERPA audit documentation can't just live in four different spreadsheets, or the urgency of cybersecurity reboots, they will continue to ask for "just one quick thing" that pulls us away from mission-critical work. Sharing our "impact vs. effort" reality helps the district understand that every hour spent on a low-impact "extra" is an hour taken away from instructional innovation. 

Every hour spent on a low-impact "extra" is an hour taken away from instructional innovation.

This might look like publishing a simple service map, outlining points of contact, or regularly sharing updates about team efforts. It might mean celebrating team wins or highlighting the behind-the-scenes work that keeps classrooms running.

When people understand the scope of our role, they make better requests. And when requests are clearer, priorities become more manageable. That's how a technology leader stops being under the table keeping the WiFi running and starts getting a seat at it.

3) Build a Legacy, Not a Kingdom

Perhaps the hardest lesson for any K-12 technology leader is realizing that if the system collapses the moment you leave, you haven't actually succeeded. Many tech directors fall into the trap of the "technical moat," keeping processes close to the vest because it feels like job security or because they want to ensure it's done "right."

Real leadership is about offboarding. Putting systems into place that will outlast your tenure. This requires cross-training, documenting processes, creating knowledge bases, automating workflows, or leveraging tools that reduce manual effort. When we refuse to offboard duties, we create a single point of failure. By empowering others and documenting our "secret sauce," we ensure that the district's technological health isn't tied to a single person's business card. We want to be the leaders who leave a legacy of stability, not a void of confusion.

We want to be the leaders who leave a legacy of stability, not a void of confusion.

The goal is simple: When you step away, the work should continue.

Technology leadership will always require wearing multiple hats, but it should never require wearing them all at once. By naming ownership, communicating clearly, and building systems that outlast us, we move from being the "etcetera" in every initiative to becoming essential leaders who create clarity, capacity, and sustainability. When IT is invisible, schools are running.

In the end, the true measure of success isn't how much we personally carry, but how well the system continues to thrive because we were there.