The AI Readiness Problem Is Not a Tool Problem

Welcome to the first issue of The Higher Ed AI Field Guide.

Once a week, this is where we work through what AI is actually doing to colleges and universities, one piece at a time, from inside the operating reality rather than the conference keynote. No hype, no vendor theater, no panic.

We start with the question every campus leader asks first, and why it may be the wrong place to begin.

---

The question comes up in almost every conversation I have with campus leaders, usually within the first ten minutes. Sometimes it is a president, sometimes a provost, sometimes a CIO who has been handed AI on top of everything else they already own. The wording barely changes.

Which AI tool should we be using?

It is a fair question, and I understand why it gets asked first. A tool is concrete. You can buy it, name it in a board update, point to it as evidence the institution is doing something. The pressure to be seen doing something about AI is real, and right now it arrives from every direction at once. Trustees who read an article on the plane. Faculty who are alarmed. Other faculty who are thrilled. Students who are already three steps ahead of the syllabus. Employers asking whether graduates can work alongside these systems. The institution down the road that just announced an AI initiative with a logo and a hashtag.

So the instinct to start with the tool makes sense. I just think it is the wrong place to start, and I have watched enough institutions learn that the slow way to want to say so plainly.

The question underneath the question

The tool is the easy part. There are good ones, the prices are coming down, and most of them will do roughly what the demo promised.

The harder question, the one sitting underneath, is whether the institution is ready to use any of them well. Not ready in the sense of having a signed license. Ready in the sense of knowing who is allowed to decide, what data is permitted to go where, what it means for teaching and assessment when the tool is no longer separate from the work, what it does to the people whose jobs it quietly reshapes, and what the institution is actually for in a world where some of what it has always sold is getting cheaper to reproduce.

None of that is a technology question. It is an institutional readiness question, and it does not get solved at procurement.

This is the thesis of this whole series, so I will state it once, cleanly, and then spend the next several months making the case:

AI readiness in higher education is not a technology project. It is an institutional readiness problem.

A college that buys the best tool on the market and drops it into an institution that has not done the readiness work does not become an AI-ready institution. It becomes an institution with a very good tool and the same unanswered questions, now moving faster.

What this actually looks like on a campus

If you want to see whether an institution is ready, do not look at its tool list. Look at three other things.

Look at where AI is already being used without anyone’s permission. I have not visited a campus yet where the honest answer is “nowhere.” Staff are pasting institutional data into free chatbots to get through the work. Faculty are generating feedback and quiz banks on personal accounts. Students are well past the point of asking. This is not a discipline problem. It is people trying to survive their workloads with the tools in front of them, and it is already your operating model whether or not anyone has named it. The only real question is whether the institution turns that improvisation into something governed and supported, or keeps pretending it is not happening.

Look at how many disconnected pilots are underway. A chatbot in enrollment, a writing tool in one department, an analytics product in student success, a copilot license that finance bought for itself. Each one is defensible. Together they are not a strategy. They are twenty small bets nobody is holding as a portfolio, with no shared rules and no way to learn across them.

And look at who is allowed to say yes, and who is allowed to say no. On a lot of campuses the answer is a committee. Committees are not the problem. A committee without authority, without decision rights, without an escalation path, and without an operating rhythm that matches the pace of the technology is the problem. It becomes a place where AI gets observed rather than led, and people who need an answer this month route around it, which brings us right back to the shadow use.

For resource-constrained institutions, this is sharper, not softer. When you have fewer people, tighter budgets, and older systems, you cannot afford twenty pilots that go nowhere, and you cannot afford to buy capacity you are not organized to use. The schools with the most to gain from AI are often the ones with the least room to waste motion on it. Readiness is how you avoid wasting the motion.

A map for the conversation

Saying AI readiness is an institutional problem is easy. The harder part is that “institutional” can mean almost anything, which is how these conversations end up everywhere and nowhere at the same time.

So at eleved we organize the work around five pillars. Think of them as the executive doorway: five questions a cabinet can actually hold in one meeting, before drilling into the operational detail underneath.

The first is Governance, Risk and Compliance. How does the institution make responsible AI decisions, and who is accountable when one goes wrong? The second is Academic Mission and Learning. How does AI change teaching, learning, assessment, and research, which is to say the actual reason the institution exists? The third is Student Lifecycle and Success. How does AI support students from the first inquiry all the way through to alumni engagement, without turning support into surveillance? The fourth is Operations and Infrastructure. How does AI change the work of running the place, and where can it create real capacity instead of new chaos? The fifth is Strategy, Culture and Positioning. How does AI shape institutional identity and long-term sustainability, including the uncomfortable question of what you offer that a cheaper, faster alternative cannot easily copy?

Underneath those five pillars sit twenty-three operational domains, from data governance to academic integrity to financial sustainability. The pillars are the doorway. The domains are the map. Most institutions try to have the doorway conversation and the map conversation at the same time, in the same meeting, with the same people, and it does not go well. Part of readiness is simply knowing which conversation you are in.

I am not going to spend this series selling that framework. I am going to use it as a way to keep us honest, because the recurring failure I see is not that institutions pick the wrong tool. It is that they answer one of these five questions, usually governance, declare themselves underway, and leave the other four sitting in the dark.

Questions worth putting on a cabinet agenda

If this lands, the most useful thing you can do is not buy anything this week. It is to ask a few questions out loud, with the right people in the room, and notice how confidently they get answered.

• Where is AI already being used across the institution without formal approval, and what does that tell us about the gaps people are trying to fill?
• Who currently has the authority to approve an AI use case, and how long does a yes or a no actually take?
• Of the AI efforts already underway here, which ones are we managing as a portfolio, and which ones did we simply not know about until now?
• Which of the five readiness questions have we genuinely worked through, and which have we only assumed someone else is handling?
• If a competitor adopted AI faster than we did, what exactly would we lose, and what would still be ours no matter what they did?

If those questions produce crisp answers, the institution is further along than most. If they produce a long pause and a glance around the table, that pause is the actual starting point. It is more useful than any tool decision you could make this month.

Where this is going

Over the next several months this Field Guide will walk all five pillars and all twenty-three domains, one at a time, in roughly the order a leadership team would want to take them. Some issues will be about governance and risk. Some will be about what teaching becomes when AI is ambient in the room. Some will be about students, operations, money, and identity. The point is not to cover AI as news. It is to help you think about readiness as the actual work, in the actual operating reality of a college or university.

The institutions that handle this well over the next few years probably will not be the ones with the most tools. They will be the ones with the clearest sense of who decides, what they are for, and which questions they have actually answered.

That is a readiness problem. It always was.