Senior Education Value Director, PowerSchool

October 16, 2026

Do you know all the technology used in your district?

I know I could answer this question when I was in charge of my district’s technology program. I had a spreadsheet on my desktop that could tell me the product, who owned it, the budget it was paid for with, and the renewal date.

The same is true for many of the districts I talk to. It might be a database or some other way they are tracking it.

That information matters for sure.

However, if we ask a different question of that information, the answer gets a little less clear. For example, if I ask: “What system do you have in place to reduce chronic absenteeism?” the answer may be harder to explain because the system is not a product. It’s everything that has to happen from the first missed days to the moment a student is reconnected to school.

“We have gotten very good at cataloging technology, but the work of a district has never fit neatly into the apps and programs we log into every day.”

That pause in trying to answer is useful because it exposes something we rarely stop to question. We have gotten very good at cataloging technology, but the work of a district has never fit neatly into the apps and programs we log into every day.

A system is more than technology

We use the word “system” all the time when what we really mean is an app or program. I think that distinction matters more than we give it credit for. In this case, a system includes the:

People doing the work
Workflows they follow
Data they need
Decisions made along the way
Apps and programs that supports all of it

Technology matters, but it’s only one part of the larger story.

Reducing chronic absenteeism, for example, makes this visible quickly. Attendance does not improve because a dashboard turns red. Someone has to be monitoring that dashboard, understand what it all means, know what processes to follow, attempt to connect with the family, coordinate support, and implement and manage the interventions. Every app involved can be working exactly as designed while the larger system still creates delays, confusion, or missed opportunities.

In the last post in this series on edtech value, I wrote about the friction that lives between systems. This is the next question: Are we looking at the whole system in the first place?

If reducing chronic absenteeism is an area of focus, could the superintendent or other leadership describe the full system behind it? Could they explain who sees the first indication of a problem and what happens next? Can they describe where the family enters the picture and how everyone knows whether the intervention worked?

If the answers are fuzzy, that’s not a technology problem. It’s a visibility problem.

(Try it now. Think of an initiative currently in place where you are. Can you name all the people, processes, and technology that drive its success?)

Start with the outcome, then build the system

Districts already have a place to begin: the strategic plan. If that plan says reducing chronic absenteeism matters, start with what success looks like and work backwards instead of starting with an inventory of apps and programs you have and what you might need to spend money on. Put the outcome in the center and ask what has to work around it.

What does success look like?
Who is involved?
What information and data do we need move and act upon?
What processes have to happen consistently?
Where does ownership change hands?

And then and only then, what technology makes that work easier?

This is what I call organizing by a center of impact. The phrase is less important than the idea, and I would argue that the district should define what this work actually looks like for itself. It’s not another department, a new technology category, or a box for sorting products. It’s a strategic outcome important enough to organize the work around. For one district, that might be 3 grade reading. For another, it might be teacher retention, graduation readiness, or family engagement.

Your district’s priorities should determine what the organization is and how it looks.

Strategic priorities cut across systems

Once you look at the work this way, the neat categories of how we typically organize technology may not seem to fit. Reducing chronic absenteeism can involve teachers, principals, attendance staff, counselors, student services, communications, technology, transportation, and families. Different teams may own individual pieces, but no single department owns the entire outcome.

The district owns the outcome together.

The same is true of the technology. A communication platform may support attendance, enrollment, and family engagement. Analytics may support early literacy, MTSS, and graduation readiness. The overlap between systems is not (or may not be) a problem to solve. Rather, it’s something leaders need to see. Strategic priorities rarely stay inside singular departments, so the systems supporting them can’t be understood only through that lens either.

Mapping priorities this way also changes who belongs in the conversation. Technology leaders see the applications and integrations. Academic and operational leaders understand the work inside them. School staff know where the workarounds live. And families experience the results. Together, those perspectives create a picture no single department can see alone.

A different kind of clarity: Follow the work to see what matters

A technology inventory is useful because it tells you what you have, how much it costs and when you will have to pay the next bill. What it can’t always tell you is how the work actually happens, where it slows down, where data stops moving, or where people have quietly become the connectors between disconnected processes. You really can only see those things when you follow the work from beginning to end.

This is not about creating another framework or launching another initiative (we all know there are already enough of these.). It’s about getting a clearer view of whether the people, processes, data, and technology already in place are helping the district accomplish what it says matters most or holding it back. When you start with the outcome, gaps become easier to see, duplication becomes easier to question, and the parts that are working well become easier to protect.

Don’t organize the conversation around the systems. Organize the systems around the work.