How Technology Teams Become the Department of “No”, and How to Change That

Karla Burkholder said something during our conversation that every district technology leader should recognize: she didn’t want technology to be the department of “no.”

She wanted curriculum and instruction to make instructional decisions. She wanted technology to assess whether a tool could be supported and whether its security and data practices met the district’s expectations.

That sounds reasonable. It also explains how technology teams end up in an impossible position.

A teacher finds an application with real instructional promise. The review uncovers a problem. Technology delivers the answer, and suddenly the people protecting students are the people preventing teachers from helping them.

The teacher sees the lesson they could create. The technology director sees the information the application would receive. Both are thinking about students. They need a process that brings those concerns into the same conversation.

Explain what would make a yes possible

Karla, Deputy Executive Director of Texas Education Technology Leaders, gave a practical example: a teacher wants access to an online game, but the district cannot establish adequate protection for the student information involved.

The instructional value may be real. So is the concern.

Simply returning “not approved” leaves the teacher with very little to work with. Explaining the concern makes the decision more understandable. Explaining what would need to change gives the conversation a possible next step.

That might mean the vendor must provide information or commitments the district needs. It might mean examining whether the activity can be accomplished with an already approved tool.

The important thing is that the educational goal remains part of the discussion.

Technology leaders shouldn’t have to argue against a good lesson to explain a problem with an application. Instructional colleagues can help preserve the lesson’s purpose while the team works through the conditions for using a tool.

Curiosity needs a clear process

Karla was explicit that she wants teachers to search, explore, and find useful resources. She also emphasized that a free product still requires review.

The absence of an invoice tells us very little about what happens after students create accounts.

A useful process helps teachers understand when to ask, what information to provide, and who participates in the decision. It also makes clear that instructional value and data protection both matter.

If the only visible part of that process is the rejection email, we shouldn’t be surprised when people misunderstand it.

Show the reasoning. Give the decision an owner. Make the next step clear enough that a teacher doesn’t need to open another support ticket to understand the first one.

We can’t demand better decisions while removing support

Our conversation also turned to instructional technology support.

Karla described the loss of specialists, professional development time, and help embedded in teachers’ day-to-day work. At the same time, expectations about thoughtful technology use keep growing.

That combination deserves attention.

Teachers are being asked to evaluate whether a tool improves instruction, understand district rules, adapt to AI, and explain their choices to families. Training on where to click will only get them so far.

They need opportunities to plan with colleagues, see useful examples, and get help applying the tools to their content.

Technology and instructional leaders should examine that support together. A district can’t reasonably expect increasingly sophisticated decisions while treating the time needed to make them as optional.

Parents need to see how the decisions work

Karla connected these internal processes to a larger issue: trust.

Families want to understand what their children are using, how much time they spend on devices, and how the district protects them. Those questions deserve specific answers.

Districts can share usage information alongside examples of the work. They can explain the review process and the responsibilities of the teams involved. Students can show what they created or learned.

That gives parents something more useful than reassurance.

It also helps distinguish questions that often get bundled together. How long students use a device, what they do with it, and what information an application receives each deserve attention. One answer won’t cover all three.

Share the responsibility before sharing the answer

The idea I took from Karla is that technology teams need colleagues in the decision, not just recipients of it.

Curriculum should help establish the instructional purpose. Technology should explain the operational and data concerns. Leadership should support the process, and teachers should understand how to participate.

Some decisions will still be no. That is part of the responsibility.

But a teacher should leave that conversation understanding the reason, knowing what can happen next, and feeling that someone is still interested in the learning they wanted to make possible.

That’s how a technology team becomes a partner people approach early, while there is still time to find a solution.