Deep Dive: The AI Officer Illusion

Olivia Carter

So, Mark, I gotta start with this: A good number of universities issuing a press release trumpeting a new Chief AI Officer coming on board. It’s like folks woke up one morning and collectively decided this was the ultimate tech flex. Does it actually mean anything? Or is it just, I dunno, a show?

Mark Putnam

It’s not just you noticing the barrage, Olivia. A Chief AI Officer—CAIO—seems to be the latest box to tick when executives and board members get nervous. It’s classic urgency theater. It’s not about driving real change; it’s about reassuring everyone in the room that, yes, “we’re responding!” It signals motion in a moment when uncertainty demands reassurance. The problem is, the appearance of motion is not motion.

Olivia Carter

That’s kinda bleak, but honestly—I get it. You’re saying institutions aren’t actually laying new tracks, just hamming it up so everyone can breathe easier?

Mark Putnam

Exactly. I’ve seen this cycle many times. Remember the Chief Digital Officers, the Chief Innovation Officers? Twenty years ago, those roles popped up everywhere, but their mandates were all concept and future talk—they rarely touched the real stuff like budgets or operations. It’s a rational defense mechanism for an institution under tech pressure, but it rarely delivers.

Olivia Carter

So we’re doing the same thing with AI now—history on repeat. Wow.

Mark Putnam

That seems to be the case in many places, Olivia.

Olivia Carter

You know, when I was digging through Chester’s piece, what jumped out was that whole Robert Gates story. Am I remembering right that he turned down a major intelligence job?

Mark Putnam

You’ve got it. Timothy Chester overlapped with Gates at Texas A&M when Gates was president. Gates was everything you want in a leader—rigorous, but open to new ideas from anyone, not just the higher-ups. But when he was offered Director of National Intelligence in 2005—the DNI—he saw it for what it was: a position with a big title, loads of responsibility, and almost no actual control. The agencies, the budgets, the staff—they all reported into others.

Olivia Carter

So Gates refused, basically saying, I won’t take a job where I’m set up to fail because I don’t have the levers—no command, no real muscle, right?

Mark Putnam

Exactly. Gates said it was like being a “powerful congressional committee chair” instead of a real executive. And that’s precisely the bind a CAIO faces. You get instant responsibility for maybe the most profound change in a generation—but no budget, no people, no real say over IT, faculty, or governance. It’s responsibility separated from authority. And there’s the risk.

Olivia Carter

It’s wild—just listening to that parallel, it’s all title, no traction.

Mark Putnam

Gates was Gates, he had strong opinions and he wasn't afraid to act on them.

Olivia Carter

So, let’s hit pause and really break this down, because I’ve heard you use this “horizontal versus vertical” phrase a few times now. I want to make sure I get it. In a standard corporation or university, you have vertical silos—Finance, HR, Facilities—and that works fine. Why can’t you just run AI like that? Why can’t we just slot a "Department of AI" right next to Human Resources and call it a day?

Mark Putnam

It’s a great question, but it fundamentally misunderstands what AI actually is. Think about it this way: HR has a distinct lane. They handle benefits, hiring, payroll. They generally stay out of the biology lab or the history curriculum. But AI isn't a lane; it's a layer. It’s not a traditional business unit; it’s a capability.

Olivia Carter

Give me an analogy.

Mark Putnam

Think of it like electricity or literacy. You don’t have a "Chief Electricity Officer" who has to sign off every time a professor plugs in a microscope or a staff member turns on the lights. If you did, the university would grind to a halt. Electricity is infrastructure—it’s horizontal. It powers everything, but it belongs to everyone. AI is exactly the same. It cuts across every role, every workflow, and every decision point.

Olivia Carter

But right now, schools are treating it like a vertical. They are hiring that Chief Electricity Officer.

Mark Putnam

Exactly. And that is where you start fighting the "physics" of the organization. When you try to force a horizontal force—something that needs to be everywhere—through a vertical funnel like a single office, you don't get focus. You get friction.

Olivia Carter

Walk me through that. What does that friction actually look like on a Tuesday morning?

Mark Putnam

Okay, imagine you’re a researcher in the medical school. You find an incredible new AI tool that helps fold proteins faster. In a healthy horizontal model, you just use it—governed by clear, pre-existing guardrails. But in this "Chief AI Officer" model, suddenly you have a new boss involved. You have to submit a request. The CAIO has to review it. But the CAIO doesn't own the network security, so they have to forward it to the CIO. They don't own the data privacy liability, so they forward it to General Counsel.

Olivia Carter

So instead of doing the research, I’m stuck in a reply-all chain.

Mark Putnam

Precisely. Innovation goes from being permission-less to permission-based. Every experiment acquires queue time. The institution doesn't become safer; it just becomes slower. And this leads to the second massive problem, which is what I call the "Negotiation Tax."

Olivia Carter

The Negotiation Tax. I love that term, but it sounds expensive. What is it?

Mark Putnam

It’s the hidden cost of doing business when you have a leader with responsibility but no authority. Remember, this new CAIO usually doesn't control the budget, the faculty tenure guidelines, or the IT infrastructure. So to get anything done, they have to beg. They spend 80% of their energy negotiating—negotiating with the Provost to change an assessment policy, negotiating with the CFO for budget, negotiating with the CIO to open a firewall port.

Olivia Carter

So they aren’t really a commander. They’re... what? A lobbyist?

Mark Putnam

That’s exactly right. They are an internal lobbyist. Every single initiative becomes a coalition that has to be built from scratch. All that time spent "aligning" and "treaty-making" is time not spent actually teaching students or improving operations. It’s bureaucracy by a new name, and it gives the illusion of progress while actually adding drag to the system.

Olivia Carter

I’ve definitely seen that in the wild. A lot of impressive-sounding meetings, a lot of strategy decks, but when you look at what’s actually changing in the classroom or the back office... it’s mostly just noise.

Mark Putnam

That's right, Olivia.

Olivia Carter

But it’s not just red tape, right? I mean—what’s the real hit here? Like, what actually happens once someone gets that shiny new CAIO badge?

Mark Putnam

What happens is disengagement. As soon as you hire that role, everyone else thinks they’re off the hook. The CIO goes back to focusing on networks and security, the Provost ignores the hard questions about pedagogy and assessment, General Counsel dodges the privacy debates. There’s this psychic relief: “That’s the AI office’s problem.” But AI is too fundamental—it cuts through everything. You can’t assign away the responsibility or the learning. Delegating sense-making is not efficiency. It’s abdication.

Olivia Carter

Honestly, I’ve seen it. There was this university I covered not long ago—a senior IT person literally told me, “Look, AI’s exciting, but now that we’ve got a Chief AI Officer, I can punt it over the fence.” And then the stuff people cared about—data quality, integrating with faculty—just hung there, unresolved. Nobody picked it up. And the real innovations? They fell right through those cracks.

Mark Putnam

Which is the structural deficit Chester’s talking about. True transformation can’t be delegated. The leaders with authority—the deans, the budget holders, the policy makers—they have to internalize this shift. If they disengage, adaptation fails.

Olivia Carter

So a CAIO might make things look safer on a board slide, but the real learning and problem-solving just gets bypassed.

Mark Putnam

Thats what I mean when I say "all appearances, no traction."

Olivia Carter

So where does that leave us? Because, I mean, you get why leaders want a clear answer—they want a fix, something that signals they’re on top of this. But what’s actually going to work? How do you build resilience instead of just…well, urgent theater?

Mark Putnam

Resilience isn’t in the shortcut, Olivia. Chester’s argument, and I think he’s absolutely right, is that the way forward is slower and harder. It means upskilling your existing leadership. You want every cabinet officer, every provost, your general counsel—everyone—to be fluent in AI, not just aware of it. Every department has to own their share. Hiring a specialist can’t substitute for institutional-wide learning. If your C-suite can’t do this work, the problem isn’t the absence of a Chief AI Officer. It’s that you need leaders ready to govern in the present reality, not the world-as-it-was. Institutions that build that mindset—they’re the ones that adapt and last.

Olivia Carter

Yeah, it’s not the fast answer. But it’s the only one that sticks. You’ve gotta build fluency at the top. There’s real comfort in just handing it off, but I mean, we know universities—you can’t deliver transformation by outsourcing responsibility for it. It just doesn’t work.

Mark Putnam

That’s the hard truth. But that’s real resilience. The temptation to find a proxy is strong, but foundational change is collective work. It’s leadership grown for the age of AI, not a workaround. And maybe this episode is our reminder: If you want durable results, get comfortable with the slow and steady path.

Olivia Carter

Alright, that feels like a good place to leave it for today. Mark, as always—thanks for your wisdom and candor. And for everyone listening, thanks for joining us on Dispatches from an Internet Pioneer. We’ll see you next time for more tough questions and honest answers. Take care, Mark.

Mark Putnam

Thanks, Olivia. Always a pleasure. Goodbye, everyone. Keep asking the real questions.