Work backwards from the person.
Not “What can AI do?”
“What is this person trying to accomplish, and what’s in their way?”
The tool serves the vision. The vision serves the human.
Every piece is built backwards from the people who’ll play it and the room they’ll play it in.
Distributing licenses is a starting point.
Calling it an AI strategy is a category error.
Solving an organizational design problem as a procurement problem.
The people who want to do this work are already at your institution.
The infrastructure you need is probably already there.
The question is permission and alignment, not acquisition.
Five moves, in order.
- Start with a real, specific problem.
- Use infrastructure you already have or can procure cleanly.
- Find the staff who want to do this. They exist.
- Build tight scope.
- Evaluate against the original problem, not the platform.
By Design
A course-specific interactive study guide. One course. One instructor.
Not a generic chatbot. A tool shaped by specific course content, pedagogical intent, and instructor judgment.
9,000+ messages before the first exam.
The infrastructure is replicable. The judgment that shaped it was human.
Untitled PDF Tool
Accessibility remediation.
One accessibility burden. Hours of repetitive lift.
Upload. Review & edit. Download.
One person freed to make decisions that require judgment.
AI proposes. Humans decide.
The tool removes the tedium; the expertise stays in the room.
Policy, made queryable.
CBA. ASPT. Workload Policy.
Documents that govern everything. Navigated by everyone, understood by almost no one at speed.
AI doesn’t read policy for you.
It gives the right people faster access to what they already needed.
Who got that time back? What did they do instead?
That’s the question.
Same model. Three domains.
What’s replicable is the method, not the artifact.
In each case: what was the actual problem, and who owned solving it?
- By Design. Generic AI doesn’t know the course. Build a tool that does.
- PDF Tool. Accessibility labor is a human sink. Remove the repetitive; keep the expertise.
- Policy Querying. Policy governs everything. Few can navigate it at speed.
A question before a solution.
Risk appetite. Leadership that can say “we’ll try something that might not work.” That permission doesn’t need to be large. It just needs to be real.
People.
Staff who want to do this are already at your institution, doing adjacent work informally. You don’t need to hire. You need to point.
Infrastructure.
If you have an AWS, Microsoft, or Google relationship, start there. You probably don’t need to buy the repackaged version.
Let’s talk.
What’s one process at your institution that everyone knows is broken, and why hasn’t AI touched it?
Has your institution purchased an AI tool in the last 18 months that repackaged capabilities you already had through an existing contract?
Where does resistance to AI implementation actually live at your institution, and is it really about the technology?
Roy Magnuson, Director · rdmagnu@ilstu.edu · adaptiveedge.illinoisstate.edu