Managing Technical Debt in K–12: Governance, Modernization, and Responsible AI

Mario McHenry, Executive Director, Technology Services, Saint Paul Public Schools

Mario McHenry, Executive Director, Technology Services, Saint Paul Public Schools

Mario McHenry serves as Executive Director of Technology Services at Saint Paul Public Schools, where he leads enterprise IT strategy, infrastructure modernization, and cybersecurity initiatives. He brings extensive experience in K-12 technology operations, governance, and service delivery to support teaching, learning and district transformation.

This article is based on an interview between Education Technology Insights and Mario McHenry. It explores his perspectives on technical debt, infrastructure modernization, governance and responsible AI adoption in today’s evolving K-12 technology landscape.

Defining Technical Debt in a K-12 Technology Environment

I define technical debt as the result of strategic or reactionbased decisions by any stakeholder allowed to directly or indirectly influence IT-related systems and service lifecycle at the local and enterprise levels. It’s not something that can be truly eliminated, only managed. Even well-maintained vehicles require service; neglect simply accelerates failure.

Types of Technical Debt that Impact Instruction and Operations Manual SIS Reporting:

Manual or file-based rostering methods for academic software tools cause “rostering rot,” where applications fail to synchronize in real time. This creates operational friction that delays "day one" classroom readiness, adds additional work for educators, and jeopardizes the accuracy and security of critical student data.

Fragmented Endpoint Device Management (EDM):

Managing device fleets of any size without standardized "known good states" creates configuration drift. This drift leads to excessive support tickets and significant instructional downtime for students and staff.

Security Risks in Neglected Peripherals:

Peripheral services like printing and faxing that lack Identity Management (IAM) integration create major privacy vulnerabilities. Without authenticated "badgerelease" printing, sensitive student and personnel records are exposed to unauthorized access, resulting in both data breaches and significant operational waste.

Practical Steps That Have Helped Saint Paul Public Schools Reduce Technical Debt

Saint Paul Public Schools’ rapid implementation of AI tools for students and staff was the result of deliberate technical debt reduction and long-term strategic planning.

At the foundation was infrastructure modernization. A stable network, device ecosystem, and core architecture allowed AI tools to be introduced without emergency upgrades or disruptive reconfiguration.

“Sustainable succession planning directly limits the accumulation of technical debt.”

Strong identity and access architecture accelerated implementation. Pre-existing Google Organizational Unit (OU) structures made grade-banded and tiered AI restrictions possible immediately. Instead of retrofitting permissions, the district leveraged mature governance already in place. Complementing this were off-site content filtering controls that restricted specific AI websites for students, ensuring managed and developmentally appropriate exposure.

Investment in professional development and communication governance ensured staff readiness. Annual “Back to School” technology training, ongoing district professional development, and monthly newsletters created clarity and alignment. This proactive approach minimized confusion, reduced support burdens, and prevented userdriven technical debt.

Students received structured digital citizenship instruction through quarterly advisory lessons addressing responsible technology use, cyberbullying and AI ethics. Clear expectations for students reinforced responsible AI use and reduced remediation.

Policy modernization and academic integrity controls strengthened governance. An updated Technology Usage Policy incorporated AI concepts, and an AI plagiarism detection upgrade increased educator confidence, with over 85% of submissions not flagged as AI-generated.

Cross-department AI workgroups further ensured coordinated decision-making, reducing siloed initiatives and fragmented tool adoption.

Together, these efforts demonstrate proactive governance, positioning Saint Paul Public Schools as technically stable and responsibly AI-ready.

Lessons for Districts Beginning Infrastructure Modernization

Infrastructure modernization in K-12 should be approached as a long-term, succession-oriented strategy rather than a short-term technical project. View every decision through a succession planning lens—preparation, phased execution and funding alignment may span multiple years. Two guiding questions should include, “How can I ensure my successor has better experiences than I did?” and “What other stakeholder challenges can this change resolve?” Linking historical investments, current realities and projected roadmaps creates continuity and prevents cyclical reinvention. Sustainable succession planning directly limits the accumulation of technical debt.

Modernization should also shift from a componentbased mindset to a service-based architecture perspective. Rather than focusing on servers, wireless access points or firewalls in isolation, prioritize the services delivered— Internet connectivity, Student Information Systems (SIS), Learning Management Systems (LMS), Inventory Management Systems (IMS) and Unified Communications as a Service (UCaaS). Measure the health, resilience and user experience of each service. Strengthening service performance will naturally surface and resolve underlying infrastructure gaps.

This service lens also reduces the likelihood of overlooking stakeholders affected by planned or unplanned changes.

Align modernization efforts explicitly with the district’s mission and vision, and articulate that alignment within roadmaps and Board materials. This secures executive sponsorship and strategic clarity. Finally, engage vendors intentionally and consistently. Maintain recurring discussions around lifecycle planning, architectural design, runbook builds, managed services, mergers or acquisitions, and training. Invest in both vendor-neutral and proprietary certifications.