Higher education leaders often blame AI for the disruption their institutions are experiencing, but the technology is only revealing problems that were already there. The real issue, according to a new analysis from the Alliance for Innovation & Transformation (AFIT), is what it calls the "inherited architecture" - the unexamined assumptions about how academic work should be organized that most colleges have never revisited.
That architecture includes assumptions like "one position equals one job equals one person," "expertise and credential mean the same thing," and "a course is a container 15 weeks long." None of these are laws. All of them were decisions made under conditions that no longer exist. In stable times, inherited architecture is invisible and mostly harmless. It becomes visible - and expensive - the moment a change arrives that the architecture can't absorb.
The analysis draws on a concept from software engineering that has a second half most people outside the field haven't heard of. Technical debt, coined by programmer Ward Cunningham in 1993, describes the accumulated cost of shipping a not-quite-right solution now and postponing the right one. In 2015, researchers led by Damian Tamburri extended this to "social debt" - the accumulated cost of organizational and social decisions rather than technical ones. Studying a large European aviation software company, they found that decisions using technical means to solve social problems generated both kinds of debt simultaneously, in a pattern that couldn't be trivially paid back.
The "community smells" of higher education
Tamburri's team created a catalog of "community smells" - recurring organizational patterns that look normal but signal accumulating debt. The analysis notes that the catalog reads "like an ethnography of higher education written by researchers who had never visited one."
One pattern is the "architecture hood effect," where decisions are so dispersed that nobody can be identified as the owner of any particular decision. This produces a "nobody's fault" dynamic in which accountability dissolves. Another is "radio silence" - an increasingly formal structure where changes are delayed while people who don't know each other are notified and certified. The researchers measured the delay at half a day to two days per decision, compounding across the organization. In higher education, that's a curriculum committee.
The most troubling finding: of the mitigations the researchers observed institutions deploying against these patterns, roughly 40% failed to produce the intended effect, and some made the situation worse. "Institutions patching without first diagnosing were flipping a coin and paying for the privilege," the analysis states.
Why AI is different from previous technologies
Higher education has developed a mechanism for making technical debt disappear from leadership conversations. The debt gets logged on a risk register, assigned to a CIO, and becomes a line item in an IT governance report. Nothing is solved. The debt is still accruing - it's just no longer visible at the layer where anyone has the authority to address it.
AI doesn't sit on top of inherited architecture the way previous technologies did. A learning management system could be bolted onto a 15-week course container without anyone examining whether the container still makes sense. A CRM could be layered over an admissions process built on assumptions from 1985. Those tools automated existing steps. AI doesn't automate steps - it redistributes what work is.
Consider a system that can do 60% of the coordination labor in an advising role but none of the relational labor. The inherited assumption that the term "advisor" represents a coherent unit of work performed by one person is no longer true. Most institutions will buy an AI advising tool and bolt it onto the existing role. Almost nobody will ask what the role actually consists of, because that question doesn't have a vendor.
The distinction between patching and rebuilding matters, and the debt literature offers diagnostic signatures rather than instincts. Patch when the mismatch is local and the assumption still holds elsewhere. Suspect architecture when the same class of problem keeps recurring under different names - for example, if enrollment decline persists despite new marketing, then new programs, then new partnerships, then new tuition discounting, the problem is shallower than the fixes. Suspect architecture when the workaround has become the process: the shadow spreadsheet, the staff member everyone calls because the official channel doesn't work. And suspect architecture when the fix requires a new prohibition - a rule forbidding a symptom rather than addressing the underlying structure. The frontier AI labs are doing exactly that, responding to emergent model behaviors by adding hard-coded prohibitions to system prompts rather than examining the training processes that produced them.
Rebuild when the assumption itself has been invalidated, not merely stressed. That's the AI case. The assumption that a position is the atomic unit of institutional work has been invalidated because AI redistributes work across position boundaries. No amount of patching at the position level will resolve a mismatch that exists at the level of what a position is.
What leadership needs to do
Before an institution can decide how AI changes its workforce, it has to identify what it currently assumes. Most have never done this analysis, because inherited architecture is invisible precisely to the people who have operated inside it the longest. The assumptions don't appear in the strategic plan. They appear in the org chart, the position control system, the workflow that everyone works around, and the committee that exists because of a decision made in 1994 that nobody remembers making.
That surfacing work isn't an HR exercise, though HR is where its absence becomes most expensive. It's architectural work that belongs to leadership, because leadership is the only layer with authority over the assumptions themselves. The question isn't "what AI tools should we buy?" The questions are: What is this institution built on, does it still hold, and if it doesn't, should we patch or should we rebuild?
For administrators in education, the practical takeaway is that the diagnostic work comes before the technology decision. Institutions that skip the diagnosis and go straight to tool selection will discover 18 months into an implementation that it's failing for reasons nobody can name. Those that surface their inherited assumptions - and distinguish between a process problem and an architecture problem - can make deliberate choices about where patching is sufficient and where a rebuild is unavoidable. The institutions that treat AI as a reason to examine how work actually gets done will be the ones that avoid the tailspin. For practical guidance on adapting teaching roles and institutional workflows, the AI Learning Path for Teachers offers a starting point, and broader resources for AI for Education can help leadership teams frame these conversations.
Why this matters for education professionals
The cost of skipping this analysis is concrete. Every year an institution spends servicing debt on a system that no longer matches its work is a year it isn't building the capacity to respond to the next change. The analysis frames it simply: the wiring in an old house is not a small project, and pretending otherwise doesn't make the lights stay on. For anyone working in higher education - faculty, administrators, staff - the question to ask isn't whether AI will change your role. It's whether your institution is willing to examine what that role was built on before the change arrives.
Your membership also unlocks:
