When a university replaces core systems, the conversation usually centers on technology choices and project plans. In higher education, the software is rarely the hardest part. Big implementations succeed or fail on change management — how people are prepared, involved, and supported along the way.
Code is the easy part
Recent EDUCAUSE research on ERP implementations found that institutional culture and readiness for change are the biggest obstacles to transformation, not the tools themselves. Sixty percent of institutions cited culture and readiness as their top challenge, and over half pointed to leadership or staff resistance. A well-chosen system can still stall if people aren't ready to move with it.
This shows up most clearly when a project touches everyday work. Timetabling, room booking, maintenance, space management, field services, energy reporting — these are tied to long-standing habits and local processes. Change the software behind them and you're changing how the university runs. Treat that as a purely technical upgrade, and the project struggles.
Governance, calendars, and trust
Higher education's governance model makes change slower and more complex, especially when that change is an entirely new campus management system. Shared governance and committee processes mean decisions that a company might make in one meeting can take a semester. Your timeline has to work around academic calendars and exam periods, not the other way around.
Resistance is often about trust, not technology. Many faculty and staff have lived through unfunded mandates, tool sprawl, and projects that promised transformation but delivered “yet another login screen.” They push back when decisions feel top-down, even when the current systems are weak.
Decentralized authority adds another layer. Colleges, departments, and campuses often run their own workflows and reporting. A single system has to work across all of them, which turns rollout into negotiation. Integrated campus platforms help here — bringing space, maintenance, and energy management into one environment while still supporting how each department already works.
Why change management isn't optional
Treating change management as a “nice to have” is risky. Experience and research in higher education show that training, communication and dedicated change teams often make the difference between broad adoption and a stalled rollout.
A few patterns stand out across projects:
- Engaging stakeholders early — faculty, departmental leaders, professional services staff — leads to higher adoption and less resistance later.
- Projects that set aside budget and time for training, coaching, and local champions build more confidence in the new way of working.
- Universities that explain the why behind a change, not just the what, connect the project to goals like student experience, research support, or resilience — which earns more buy-in than a features list ever will.
The platform is only part of the story. Implementation support, process design, training, and ongoing application management all help turn a higher education software into something people actually use. But that only works if the university invests in the change management around it.
Five steps to set yourself up for success
These draw on change frameworks like Prosci's ADKAR model and lessons from universities that have been through large ERP and digital transformation projects.
Resistance is often about trust, not technology. Many faculty and staff have lived through unfunded mandates, tool sprawl, and projects that promised transformation but delivered “yet another login screen.” They push back when decisions feel top-down, even when the current systems are weak.
- Start with culture and readiness. Before you finalize requirements, check how ready different parts of the institution are for change. Look at where past projects succeeded or failed, and sequence your rollout around academic cycles so major milestones don't clash with teaching and exams.
- Involve end users early. Faculty and facilities teams know how the work actually gets done. Bringing them into selection and design improves fit and builds trust. Not every decision needs a vote, but people need to know their input mattered.
- Plan for ongoing training and communication. Don't stop training at go-live. Short sessions, recordings, peer support, and targeted training for power users help different groups adapt at their own pace. Focus your messaging on concrete benefits: fewer manual steps, better data, clearer insight into space use and maintenance.
- Use local champions and cross-functional teams. Champions in faculties, departments, and service units bridge the gap between the project team and daily work. They catch issues early and translate project messages into terms their colleagues understand. Cross-functional teams — IT, facilities, academic representatives, leadership — keep decisions realistic while maintaining an institution-wide view.
- Look beyond go-live. Successful universities treat go-live as a starting point, not the finish line. They use the implementation to strengthen data foundations, break down siloed workflows, and support priorities like hybrid learning, sustainability, or student experience. Tie the new system to goals like reducing carbon footprint or improving space use, and it becomes a lever for long-term resilience instead of just another tool.
Bringing it together
In higher education, shared governance, decentralized authority, and long-standing ways of working mean major campus management software projects are as much about people as they are about platforms. Change management isn't a side stream on the project plan — it's the work that determines whether a new system, whether an IWMS, a campus management solution, or something else, can actually support the institution it's meant to serve.
Take culture and readiness seriously. Involve end users in decisions. Invest in training and communication. Link the project to long-term goals. Do this, and you improve your odds that a major change in day-to-day procedures leads to real improvement, not another difficult chapter.