The Student-Centered Approach

Leaders discuss operational strategy

Higher education is under increasing pressure to modernize operations, integrate emerging technologies, strengthen cybersecurity, and meet rising student expectations—all while navigating financial constraints and organizational complexity. But the institutions making the greatest progress are not simply investing in technology. They are rethinking the role of partnership, operational strategy, and leadership itself.

Former Dartmouth CIO, Mitch Davis and former MIT CIO, Mark Silis share their perspectives on what it takes to build institutions that are both operationally resilient and student-centered. Drawing from decades of experience leading large-scale digital transformation efforts at some of the nation’s most prestigious universities, both leaders emphasize a common theme: technology should never exist for its own sake. It should serve people, remove friction, and create environments where students, faculty, and staff can thrive.

“Problems arise when partners, leadership, and operations lose focus on why they exist.”

— Mitch Davis, Former Dartmouth CIO

Why is it so important for campus IT to operate as a strategic partner across the institution rather than simply a service provider, and how does that ultimately shape the student experience?

Davis:  Organizational leadership that has limited knowledge of technology usually wants to quantify it as a service. This makes technology seem more relatable and understandable like finance, facilities, and HR. But, it is unlike any other service because IT is pervasive, expansive, rapidly growing and disrupting the status quo individually, organizationally, and globally. Technologies within robotics, quantum computing, and Artificial Intelligence are all remapping our future. In turn, the IT staff are some of the most knowledgeable, well paid and educated people on campus. If you choose not to utilize them as a catalyst for ideas and building your future, you are limiting your institution’s ability to compete.

Silis:  Technology today is integral to everything that happens under the university roof. The traditional model—where each part of the institution owns its own digital strategy for its own systems, whether teaching and learning, HR, finance, research management, or the student information system—no longer works. These systems have to operate as one digital ecosystem across the campus. That demands a fundamentally different role for campus IT than 20 years ago, when the work was largely about offering recommendations and guidance. Today, the work is building and orchestrating an ecosystem in which every system serves the community seamlessly.

“Campus IT is not a service provider. Technology is a strategic capability—essential, not complementary—and the pandemic proved it.”

— Mark Silis, former MIT CIO

The same principle shapes the student experience. Students born in the 2000s expect to navigate institutional complexity the way they navigate everything else: on their phones, in a couple of clicks. It shouldn’t take five phone calls, 10 tickets, and 12 different people to land a class schedule, plan a degree, or pick a meal plan. That’s the world they grew up in, and it’s the world higher education has to operate in.

Campus IT is not a service provider. Technology is a strategic capability—essential, not complementary—and the pandemic proved it.

How should institutions think differently about operational excellence so that efficiency improvements actually enhance engagement, access, and student success?

Davis:  The student experience is best done with them in mind. Maintaining successful relationships with student government and IT related students is incredibly important. With the students involved, you have advocates on campus that can provide valuable information when you are making changes to operations or systems. Delivering desired operationing solutions is only possible if you engage students in the process of change. By working with them to deliver meaningful change, you can build a relationship where they wait in anticipation for change rather than resistance.

Silis:  The right question about operational efficiency is: efficiency for whom? Too often, “efficiency” is just another word for cost savings, measured purely from the back-office perspective. And in my experience, even on those narrow terms, very few systems projects actually deliver. When I’ve asked colleagues what a project will save, or what capabilities it will provide, and whether we can hold those to measurable metrics, the honest answer is usually some version of “we just want to make it better.”

Real operational efficiency has to be measured holistically from the perspective of the people running the institution, and from the perspective of the people it serves. That second perspective is the one universities most often miss. Take something as simple as a facilities repair form. The more detail the back office can capture up front, the more efficient its workflow. But that efficiency is purchased by asking the person reporting the problem to fill out 50 fields across 20 categories. Multiply that pattern across registration, room booking, financial aid, and every other touchpoint, and you have an institution whose internal efficiency is paid for by the friction it imposes on its community.

Here’s what’s actually at stake. You have some of the brightest minds in the world on your campus. You want them spending their time on the work that furthers their education and produces research breakthroughs, not navigating internal systems or administrative bureaucracy. Done well, operational excellence makes that possible. Everyone wins. But it requires thinking about efficiency from every side of the equation, not just the back office.

How critical is collaboration between IT, operations, procurement, academic leadership, and external partners when trying to create a more seamless and supportive campus experience for students?

Davis:  Problems arise when partners, leadership, and operations lose focus on why they exist. Collaboration isn’t as essential if everyone agrees on outcomes up front.  I have seen collaborations fall apart when partners become more concerned about who is getting credit than doing the right thing. What is essential is embedding IT staff into departments. It is the best way to build a solid partnership and cultural alignment. But, the person must be invited to participate and it will take lots of time and effort.

Silis:  Collaboration is absolutely essential, and it starts from a simple fact: Digital is part of everything now. Every function on campus—academic leadership, operations, procurement, teaching and learning, external partners—touches the digital ecosystem in some way. You cannot build a seamless campus experience by treating that ecosystem as campus IT’s problem alone. Everyone has to be part of the journey.

When I look back at the projects that genuinely worked—the ones that produced experiences worthy of the institution—what stands out isn’t the technology. It’s the working relationships of the teams that built them. The openness, the transparency, the willingness to ask hard questions in front of each other, and the shared posture of trying to solve problems together rather than defending turf. That’s what produces the best and most satisfying solutions.

The alternative is regression. If campus IT designs in isolation, or any single function does, you end up with seams, the disconnected systems and disjointed experiences that students, faculty, and staff feel every day. The work of creating a truly supportive campus experience requires every part of the institution to come to the table, stay at the table, and own the outcome together.

What advice would you give institutional leaders about building partnerships and operational strategies that remain focused on people first—not just technology first?

Davis:  People always come first when thinking about outcomes. In addition, you need an operational and access state for Information Technology to ensure everything is in place for all the strategic vision to be realized. You simply cannot hobble IT by ignoring proper training, equipment, and funding and then blame them for unmet goals. Trusting IT leadership to deliver requires a seat at the table helping to define and determine what success means for all stakeholders.

Silis:  We’re at a moment in history that feels a lot like the early days of the internet but on a completely different scale. In the nineties, when I arrived at MIT, the institution had to build Project Athena to put computing workstations in students’ hands because access to technology was so uneven. Today, the technology is already in everyone’s hands. That’s why the AI revolution will evolve far more quickly, and reach far deeper into how we live and work than the internet revolution did.

The fundamental tension is this: Human capacity for change is linear, while technology’s capacity for change is exponential. Managing the gap between those two curves is much of what campus IT does day to day, and the gap is widening.

My advice to institutional leaders is: lean in. Don’t turn away from these changes because we don’t yet understand them or know how to use them, both of which may be true. Lean in anyway. Take responsible risks. Engage the debate on what we teach and how. The graphing calculator was resisted in the nineties for many of the same reasons AI is resisted in the classroom now, and it turned out to be a net benefit. It freed students to develop more intuition and tackle higher-order problems. We’ve always abstracted away yesterday’s foundations so people can solve tomorrow’s problems. AI is the next step in that pattern.

“Trusting IT leadership to deliver requires a seat at the table helping to define and determine what success means for all stakeholders.”

— Mitch Davis, former Dartmouth CIO

The most important shift, though, is who gets to build and what gets built. AI is putting technical capabilities into the hands of every individual on campus. People who never wrote a line of code are now building working software, and increasingly they’re building agentic systems—AI that doesn’t just respond to a prompt, but acts on their behalf, navigates processes for them, and gets work done. That’s a tectonic change for how an institution operates, because the community we serve is no longer just consuming what campus IT provides. They’re active participants —designing their own experiences, their own interfaces, and their own agents to engage the institution on their behalf. That changes expectations. It changes the loop of accountability.

For most of its history, campus IT delivered one solution and asked everyone to live with it—80% good enough for the average user. We’re moving into a world where each person can shape their own experience and, increasingly, deploy their own agents to act on it. People-first strategy, in this moment, means accepting that shift and building an environment that enables it—partnerships that pull faculty, staff, students, and external partners into co-creation, and infrastructure that’s built to be navigated by agents, not just clicked through by humans. Lead with that, and the technology choices will follow.

“The fundamental tension is this: Human capacity for change is linear, while technology’s capacity for change is exponential.”

— Mark Silis, former MIT CIO