AI has added a new expectation to an old problem. District technology teams have been asked to do more with less for years. Now the thinking goes something like this: You have AI. You know how to use it. Surely that makes doing more with less easier.
I see why that sounds reasonable. I also think it skips over the question I’d ask if I were still sitting in the district CIO chair today: Where could AI take some work off people’s plates and give them more time for the work that needs their expertise? I’d start by making it easier for people across the district to get the help they need.
From a Single Pane of Glass to a Single Front Door
When I was CIO at Fulton County Schools, we had finance data in one place, student information in another, and plenty of other systems in between. We were a large district and had the staff to bring that data together securely. Our team built more than 400 visualizations. For the first time, we could look at information from across the district through what I like to call a single pane of glass. That gave us a better view of what was happening and helped us make decisions.
I’ve been thinking about what it would mean to give people across a district that same kind of simplicity when they need help. And I think a door is better for that. Glass is something you look through. A door is something you walk through.
Say you’re a teacher and the air conditioner in your classroom has stopped working. You’ve got a room full of students. How much time do you want to spend figuring out whom to call or which form to fill out? I’d like you to be able to say, “My classroom air conditioner is broken,” and get the request moving. If you need a device repaired tomorrow, you ought to be able to start in that same place.
Sometimes all you need is an answer. Sometimes somebody needs to take the next step. That’s where AI gets especially interesting to me. It could pull together the details and tee up the request so it can reach the right team with enough information to act. Think about how much easier that would make the teacher’s day. Now think about all the people across a district who spend a little of their day getting a question or a request to the right place.
People Should Make the Judgment Calls
When I say I’d like AI to tee up the next step, I mean I’d like to see what it’s prepared before it takes an action that calls for judgment. I’d want to know how well it works in my district before I trust it to do more. What information does it need? Is there student data involved? Who’s responsible for what happens next? Those are questions I’d want answered while we still have choices about how to set it up.
Take a budget conversation. Say we need to look at what a 20 percent reduction could mean for the district. AI could compare a proposed budget with our strategic plan and show us which priorities could be affected. That would help us get to the part of the conversation where we need to sit down together and ask if the juice is worth the squeeze.
What would we be giving up? How would our schools and community feel it? Are we protecting what matters most for teaching and learning? I’d be glad to have help putting the information together. I’d want the people who know those schools and answer to that community making the decision.
Build Only If You Can Support It at Scale
The question of who’s responsible matters just as much when you’re deciding whether to build an AI application yourself or buy one. I was talking with a group of CIOs recently, and that choice came up in a very practical way. One colleague from a small district was building an AI tool to take care of some of the routine tickets his team sees over and over. He wanted more time for the work that needed his attention. I understood the appeal. We built plenty of things ourselves at Fulton because we had the people and the budget to support them.
Then his peers started asking the kinds of questions you want your colleagues to ask while you’re still trying something out. What data can the tool access, and how will you protect it? Who’s going to keep it working? Can you still support it if more schools and teams start using it?
I like seeing districts try things for themselves. If you have the people and a plan to keep the tool secure, maintain it, and support it as more people use it, building can make sense. If you can’t see how your team would take that on, I’d look at what’s already available. A partner who understands K-12 may be able to adapt an existing tool to your district’s needs and help you support it over time. One thing I always want to know about a partner is whether they’ll sit down with us and work through the problem when something goes wrong.
What Would We Do With the Time We Get Back?
I’ve been CIO in districts of very different sizes. The scale changes, and so does what you can take on. What I’ve found in both settings is that people go into this work because they want to serve schools. They take it to heart when what they’re being asked to deliver and what they have to work with don’t line up.
That’s why I’d start with the work people already wish they had more time to do. Think back to that teacher with a room full of students and a broken air conditioner. If getting help takes one request instead of a search for the right person or form, that’s a little more of the day the teacher gets to spend with students. The same goes for the district team. Every request they don’t have to chase down gives them a little more room for the work that needs their attention.
I think of myself first as an educator and second as an IT professional. When I weigh what AI can do for a district, I come back to what we’re here for. If it gives teachers more time to teach and district teams more time to support them, that’s where I see its value.



.png)
