I recently got a great perspective from Nate B. Jones (@nate.b.jones) on the current “hype” surrounding AI—specifically the launch of tools like Claude Design. Like almost every shift in AI, computer professionals often feel like they are under siege, wondering if their jobs are being automated out from under them.
While concern is understandable, Nate made a point that really stuck with me: Good designers can use this technology to truly innovate by removing themselves from the implementation parts of their job.
Design was never about just “making the thing.” It was about situating a product within a context for a user. In the world of Higher Education, we don’t just build “products”; we build environments for knowledge. For the talented UX designers here at Duke, AI isn’t a replacement—it’s a release from the manual labor of production, allowing us to focus on the high-level architecture that our unique academic environment requires.
The Higher Ed Distinction: Mission Over Marketing
In the corporate world, UX is often a tool for “conversion”—getting someone to click, buy, or subscribe. But in a university setting, our goals aren’t transactional. We are designing for comprehension, retention, and institutional support. This requires a split in how we approach our trade.
1. Pedagogical UX: Designing for the Learner
When we develop content for instruction, our “user” is a student trying to master a complex concept. Standard marketing UX tries to remove all friction. However, in education, we often need desirable difficulty.
We use UX to “scaffold” information—revealing complexity in layers so we don’t overwhelm the student. Our requirements for accessibility (WCAG 2.1 AA) and universal design aren’t just checkboxes; they are the foundation of an equitable education. AI can generate the code for a slider, but it can’t determine the pedagogical timing of when that slider should appear to best aid a student’s “Aha!” moment.
2. Operational UX: Designing for the Staff
On the other side of the house, we have our faculty and staff. For them, the UX should be invisible. Whether they are managing an LMS, filing research grants, or navigating administrative portals, they need tools that get out of the way.
The “implementation” side of this work is often tedious—aligning tables, consistent button placement, and form logic. By letting AI handle the “production” of these artifacts, our designers can focus on the Institutional Intelligence:
-
How do we reduce the administrative burden on a PI (Principal Investigator)?
-
How can we streamline workflows so faculty spend more time teaching and less time “fighting the system”?
The Shift to Design Management
Nate’s take is that we are moving from being “vibe coders” or “artifact makers” to being managers of the process.
For us at Duke, that means our UX designers become the ultimate bridge. We translate academic intent into digital reality. If AI takes away two-thirds of the time we used to spend on the “implementation,” we can give that time back to the students and faculty through better research, deeper empathy, and more thoughtful architecture.
Maybe we’re aren’t under siege; we’re being promoted.
