Who Should the CIO Report To? Power, Structure, and the Ideal Leadership Model

Olivia Carter

Alright, Mark, let’s dive right in. So, today we’re talking about something that sounds a little dry at first glance—who the CIO actually reports to in a university—but if you’ve spent even a coffee break in higher ed, you know it’s, uh, supercharged. It sets the CIO’s tone: are you, like, the strategy architect, the quiet fixer, or just the budget enforcer?

Mark Putnam

Liv, it’s one of those topics where most folks see just the org chart, but beneath that lies a whole world of culture, trust, and, honestly, sometimes a fair bit of tension. I always find it useful to start with Weber’s “ideal type” concept—a way to clarify what the job really looks like at its best. It’s not perfectionism or some HR fantasy, just a clear-eyed framework.

Olivia Carter

Right, and Weber didn’t mean, you know, a checklist leader that fits everywhere perfectly. It's more like: here are the key dimensions you need to think about—then reality bends and adapts around them. So, let’s list those out: strategic stewardship, governance, digital strategy, institutional partnership, talent, and, last but not least, integrity. That’s a lot to juggle.

Mark Putnam

And each of those, Liv, is less about the technicalities and more about mindset. Strategic stewardship—are you aligning tech with the mission or just keeping the lights on? Governance and risk—who do you answer to and what happens when the stakes are high? Digital strategy—do you actually get to lead transformation or just smooth out the bumps? Partnership—are you at the table, or waiting by the door? Talent—do you build culture, or just keep up with HR? Integrity—it’s really the glue. If you fudge on that, it all unravels fast.

Olivia Carter

I mean, on paper it all sounds… neat? But in real life, you never get the full “ideal.” You’re always negotiating some trade-off: speed versus consensus, freedom versus oversight. Do you think, Mark, there’s really a single gold-standard model, or is adaptability what actually matters most?

Mark Putnam

No single model’s perfect, Liv. The “ideal type” sharpens the choices—shows what you’re giving up and what you’re gaining. In my experience, the real hallmark is adaptability: mastering the structure you’re in, rather than wishing for a better box on the chart.

Olivia Carter

We should get into how these reporting lines actually happen in the wild. It’s never just “let’s shake up the org chart” for fun, right? There’s always some kind of trigger. I remember a search I covered at, uh—can I say the name, Mark? No?—a flagship university, where the executive team basically split into factions arguing over whether the new CIO should report to the president, provost, or CFO. It got seriously political. Like, the faculty senate had a debate about IT governance—wild.

Mark Putnam

That’s a familiar pattern. When a president wants to restore authority and urgency, maybe after a leadership blow-up or a cyber incident, they’ll bump the CIO to a direct report. If faculty are worried about academic tech being “just” administrative, the provost becomes the answer. If expense control or admin efficiency is front and center—and maybe there's the sense that the CIO needs greater supervision—the CFO or COO takes the reins. Each choice sends a signal: what does the institution value most right now? And is it ready for change, or just trying to contain some risk?

Olivia Carter

It’s interesting how those decisions don’t just “happen”—they telegraph priorities. If they want bold strategy, they go top. If they’re anxious about the growing wedge between teaching and admin, they shift to the provost. If, honestly, they’re desperate for budget predictability and control over IT… it goes to finance. But, like, once that decision’s made, it’s not just the paper trail—it shapes every interaction for years.

Mark Putnam

Exactly, Liv. Reporting line signals how much trust they’re extending—and what kind of leader they really want, even if they don’t say it out loud. That sets the ground rules for everything that follows, from hiring to how quickly change really happens.

Olivia Carter

Mark, let's dive into how the CIO role is different based on who's their boss.

Mark Putnam

Let’s start at the top: reporting to the president. This model looks most powerful on the chart. It tells the community that tech is strategic, not just a service function. The CIO sits at the same table as other cabinet leaders, defining the digital direction for the whole university. I had this experience after a leadership turnover. The new president urgently wanted digital change, wanted IT front and center, and gave me license to act quickly—but expected results just as quickly. It’s both liberating and, frankly, it keeps you up at night.

Olivia Carter

So, huge freedom… and even bigger scrutiny. That double-edge, right? Because formal authority doesn’t magically get people onto your train if they weren’t already convinced. You must build trust fast, or that “freedom” just means you’re first in line if things don’t work out.

Mark Putnam

That’s precisely it. You have to be more than just “the IT person with the big title.” It’s about turning complexity into clarity, listening—and acting—fast enough to show progress, but not recklessly. You can’t rely on authority alone. In fact, you get very little credit for your box on the chart unless you translate it into value for everyone else. Build trust by showing you’re there to serve the institution, not just win internal battles.

Olivia Carter

Sounds like a role where candor and urgency are front and center, but also empathy. You have to walk the line—not lean on your title too much, but also, you know, not get lost trying to please everybody. You’re the strategist, but if you lose the room, you lose everything.

Mark Putnam

That's right, Olivia.

Olivia Carter

So let’s switch gears. Reporting to the provost—this one seems to put the CIO right in the middle of the academic heartbeat. There’s more partnership, more natural trust with faculty and deans. You’re a peer, not just a resource. But, Mark, I want to ask—how did those trusting faculty relationships actually shape the work you did? Did it really change the IT culture?

Mark Putnam

It changed everything, Liv. When I reported to the provost, it meant sitting at the same table as the deans, not just as a support function, but as a voice in core academic decisions. It built a culture of dialogue—faculty felt heard, and so did their concerns about teaching and research. But, the tough part—sometimes, the urge to “get buy-in,” to wait for consensus, could bog us down. Some projects just can’t afford endless dialogue or they never get out of committee.

Olivia Carter

Yeah, that’s such a classic higher ed thing—everyone wants consensus, but sometimes the window for action slams shut while folks are still wordsmithing the proposal. But the upside is real: alignment with mission, the sense that IT is an enabler of scholarship, not just overhead.

Mark Putnam

I agree. When the CIO builds those bridges, the academic side opens up to tech as a true partner. But you still have to be brave enough to nudge things forward, even when the crowd’s not quite ready.

Olivia Carter

So, let’s tackle the last one folks, uh, that some CIOs complain about: the CIO who reports to the CFO or COO. It’s kind of the “get things done” model, right? Prioritizes efficiency, admin alignment, risk—all the things presidents and provosts say they want, but maybe not at the expense of, well, academic influence and autonomy?

Mark Putnam

Exactly. You have strong operational influence—budgets, compliance, process—but often struggle to reach academic departments. It shifts you from being a strategist to becoming, in a sense, a persuader. I remember having to… well, translate everything—taking academic project asks and recasting them in finance language. In one case, I spent weeks reframing a proposal to show cost controls, compliance wins, operational impact—only then did it get traction. You need a coalition, and you win support through credibility, not just positional power.

Olivia Carter

It sounds exhausting but, honestly, super practical. You have to align with the administrative crowd, but quietly hustle for innovation with faculty and academic leaders. You’re, like, the operational diplomat. And everybody knows, if you get this right, the whole place runs smoother, even if it means fewer bold risks.

Mark Putnam

True, Liv. The upside is stability—discipline, reliable outcomes, structure. But it’s less about grand gestures, more about steady progress. That’s not glamorous, but it is essential.

Olivia Carter

Alright, Mark, before we close—if you had to give advice to a new CIO about reporting lines, what would you say?

Mark Putnam

Don’t focus on the lines. Focus on mastering the box you’re given—because trust and adaptability travel with you. The org chart might set your starting point, but leadership runs on respect and fit.

Olivia Carter

I love that. Okay, this was both nerdy and practical—my favorite mix. Thanks, Mark. And thanks to all of you for joining us again. If you got this far, you’re kind of a governance geek, too. We’ll be back soon with another episode of Dispatches from an Internet Pioneer.

Mark Putnam

Always a pleasure, Liv. Take care, everyone.

Olivia Carter

Bye, Mark. See you next time!