The Provost's Real Job Isn't Digital Transformation. It's Making It Add Up to One Institution

Ask most provosts to describe their job, and you'll hear a version of the same three priorities: grow enrollment, improve curriculum, keep the institution getting better year over year. Look at how academic affairs offices actually publish their own goals today, and a fourth commitment shows up almost every time, one that's easy to miss: strengthen accountability and evidence-based decision-making.

That fourth priority is the one digital transformation projects were supposed to deliver. Instead, most provosts got several separate answers to "what is our evidence," one from the SIS, one from the assessment tool, one from whichever spreadsheet Institutional Research maintains between official reports. Each answer is accurate. None of them is the institution speaking with one voice.

Here's where that shows up in practice.

A program is underperforming on enrollment. The provost needs to decide whether to redesign it, consolidate it, or let it run another cycle. That single decision touches five separate records: current enrollment trends from the SIS, assessment and learning outcome data from wherever OBE tracking happens, faculty workload implications from a scheduling tool, budget exposure from finance, and how a change would ripple into related programs sharing courses or faculty.

Each of those systems is modern. Each was implemented as its own transformation win. None of them was built knowing the other four exist.

So the provost's office does what every provost's office ends up doing: someone pulls a report from each system, reconciles the numbers by hand, and builds a briefing document that will be out of date the moment anything changes. The decision gets made. It just takes longer, involves more people checking each other's numbers, and produces an answer that's already aging by the time it reaches the meeting.

Multiply that by every program review, every curriculum change, every accreditation cycle running in parallel, and the pattern becomes the job. Not leading transformation. Managing reconciliation.

The instinct, when this keeps happening, is to look for one more system, a better dashboard, a data warehouse, an analytics layer that finally pulls everything together. That instinct isn't wrong. It's aimed at the wrong altitude.

A dashboard can display five disconnected data sources side by side. It can't tell you they mean the same thing, because the underlying systems were never governed by one institutional model in the first place. The gap isn't visibility. It's ownership: who decides what "current enrollment" means across every system that reports it, and who's accountable when two of them disagree.

EDUCAUSE's Top 10 for 2026 names building a data-centric culture as one of higher education's leading priorities this year, and not a systems upgrade, but rather a culture shift. That distinction matters. A data-centric culture is a governance decision before it's a technology purchase: which academic facts are owned centrally, which decisions require which evidence, and how a change made in one place is guaranteed to show up correctly everywhere else.

Some institutions have started describing this connected layer as an academic operating system, a single governed model that curriculum, workload, assessment, and outcomes all run through, so a provost isn't reconciling five versions of the truth before every decision. 

That's less a product category than a description of what "leading digital transformation" should have meant from the start: not owning more systems, but owning the model that makes all of them agree.

That's also where connected institutional strategy starts to matter more than any individual tool. Strategic planning that spans enrollment, curriculum, and faculty capacity only works if the numbers feeding it come from one governed source, not five reconciled ones.