How UCSD Transformed the Entire University into a Cultural DNA with Change Management

The most difficult thing to change at a university is often not the systems, processes, or organizational structure, but the long-held ways people work.

The University of California, San Diego (UCSD) faced this very challenge. This wasn't a partial improvement in a small institution but a campus-wide transformation of a large research university. The campus has over 12,000 faculty and staff distributed across academic, administrative, research, and healthcare systems. Each unit had its own rhythm, language, priorities, and work culture.

When the new chancellor pushed for a campus-wide strategic transformation, problems quickly emerged. UCSD did not lack talent or ambition. What truly hindered the transformation was the absence of a common methodology for change.

Every team was working hard, but every team was working in its own way. The result wasn't increased speed, but increased chaos.

The transformation of a large campus begins with seeing its complexity.

The Core Challenge for UCSD's Change Management: An Abundance of Change

When many organizations talk about transformation, the first question is how to initiate change. UCSD's problem was the opposite. A large number of changes were already happening on campus.

New systems going live, new processes being introduced, new collaboration models being pushed, and cross-departmental projects being launched. While each of these changes was necessary on its own, they became a heavy burden when they fell on the same group of people simultaneously.

Typical problems UCSD faced at the time included:

• Inconsistent communication messages, with different units having different understandings of the same transformation.

• Resistance appearing in various places but difficult to see systematically.

• Leadership finding it hard to grasp the true progress of the campus-wide transformation.

• Frontline staff feeling fatigued from facing multiple changes at once.

• Project teams focusing on delivering results but underestimating the difficulty of user adoption.

These situations are not uncommon in large organizations. The root of the problem is usually not that the wrong system was chosen or that a certain team was uncooperative, but that there was no common language for change.

When one unit said "we're ready," it might only mean that technical testing was complete. When someone said "everyone knows," it might just mean a notice had been sent out. When someone said "resistance is low," it might just be that employees hadn't expressed their concerns publicly yet.

Without a common methodology, transformation is difficult to manage. It becomes a collection of projects rather than a directed organizational change.

Strategic Pivot: Building Change Capability at UCSD

When UCSD approached Prosci, its goal was not to have an external consultant complete a single project. What the university truly wanted to build was a capability that could remain within the organization.

This is the most noteworthy aspect of the UCSD case.

When faced with a stalled transformation, many organizations demand faster project delivery, quicker system launches, and stronger pushes from management. But UCSD took a different path. It first asked a more fundamental question:

If the entire university needs to change, have we taught everyone how to face change?

Prosci's recommendation focused on capability building. That is, before pushing for more changes, let the people on campus understand how change happens, how resistance is formed, how adoption is supported, and how results are sustained.

This shifted change management from "a tool needed for some projects" to "a method that all managers and project teams can use."

Disparate paths need a common direction, and so does transformation.

Driving Change at UCSD: Aligning Leadership with a Common Language

In a large-scale transformation, training only the grassroots level without training leadership usually has limited effect. This is because employees observe not only the content of the change but also whether their supervisors are genuinely committed, whether they talk about it consistently, and whether they are willing to address resistance.

UCSD's first step was to have 50 senior leaders participate in Prosci's change management program. This was crucial.

When leadership begins to use the same language, the quality of conversation throughout the organization changes. In the past, they might only have asked:

• When does the system go live?

• Are we over budget?

• Is the schedule delayed?

• What is the training completion rate?

After learning change management, leaders began to ask questions closer to the success or failure of adoption:

• Do the affected people know why we need to change? (Awareness)

• Are they willing to participate in this change? (Desire)

• Do they know how to work in the new way? (Knowledge)

• Do they have the ability to actually do it? (Ability)

• Will the new behaviors be continuously reinforced? (Reinforcement)

These questions correspond to the five elements of Prosci's ADKAR model: Awareness, Desire, Knowledge, Ability, and Reinforcement.

The value of ADKAR is not just that it provides a set of terms, but that it allows people at different levels to talk about the same thing. When a project falls behind schedule, the team doesn't have to just say "people are resisting." They can more accurately determine if there is a lack of Awareness, insufficient Desire, or if Knowledge and Ability have not yet been established.

This precision turns change from a matter of feeling into a manageable issue that can be diagnosed, discussed, and improved.

Large-Scale Training Brought ADKAR into Daily Work

After aligning the leadership, UCSD then rolled out change management to a wider audience.

The university held large, forum-style training sessions with over 500 participants per session. Participants included not only managers but also administrative staff and frontline employees. This shows that UCSD did not view change management as a specialty for a few senior executives, but as a shared capability for the entire campus.

The training helped campus personnel understand:

• How to build awareness of the reasons for change.

• How to increase personal desire to participate in change.

• How to provide enough knowledge for people to know how to do things the new way.

• How to build actual ability, not just complete training.

• How to make new behaviors stick through subsequent support.

These points may seem basic, but they are precisely where many transformations fail.

Many organizations think that sending out an announcement equals building Awareness. They think holding a training session equals having Knowledge. They think that once the process is written down, employees will naturally have the Ability. They think that once the system is live, the change is complete.

UCSD's approach, however, reminds everyone that adoption does not happen automatically. It needs to be designed, supported, and tracked.

A common language is not a slogan, but an understanding in daily interactions.

Learning Didn't Stop When the Course Ended

What makes the UCSD case truly valuable is not just how many people it trained, but that it didn't treat training as the end point.

Many organizations hold grand change management courses, only to revert to their old ways afterward. UCSD adopted a continuous capability-building approach. It established an online learning community, scheduled regular workshops, and provided coaching support.

This transformed change management from a one-time event into a continuous cycle of capability.

When project teams encountered resistance, they could go back to ADKAR to diagnose the problem. When managers needed to support their teams, they could use the common framework for dialogue. When new changes were initiated, teams more naturally incorporated people-side adoption into their plans, rather than trying to fix it at the last minute.

This continuity is crucial. Culture doesn't change because of one course. Culture is formed after repeatedly using the same method, repeatedly asking the same types of questions, and repeatedly reinforcing the same kind of behavior.

UCSD's change management became DNA not through a single, brilliant implementation, but through long-term, repetitive management habits.

Results Began to Appear at Three Levels: Capability, Projects, and Culture

According to the public case study by Prosci, UCSD's results were not limited to "everyone thought the course was good." They gradually reflected in capability improvement, project success, and cultural transformation.

Employees Saw the Practicality of the Training

The case study mentions that 90% of participants felt the training content was immediately applicable. This figure is significant because if change management remains only at the conceptual level, it is difficult to integrate into daily work.

For a large university, faculty and staff deal with processes, policies, systems, and cross-departmental collaboration every day. If they can directly apply the course content to their work situations, it means the language of the methodology is clear enough and close enough to the ground.

UCSD also received a relevant ATD (Association for Talent Development) award for this talent development effort. This shows that it didn't just complete the training, but achieved recognizable results in organizational capability building.

IT Consolidation Projects Became Better at Handling Resistance

In an IT consolidation project, the team used ADKAR to diagnose resistance. This allowed them to see more clearly where the problem lay.

If employees didn't understand the reason for the change, Awareness needed to be reinforced. If employees knew the reason but were unwilling to cooperate, Desire needed to be addressed. If they were willing to change but didn't know how, Knowledge needed to be provided. If they knew how but couldn't do it, Ability needed to be supported.

The case study mentioned a significant improvement in Awareness and Desire. Even more noteworthy, employees began to proactively ask questions related to adoption.

This is a sign of cultural shift. When people are no longer passive recipients of change but start asking how to adopt, how to use, and how to do things the new way, it means they have shifted from being spectators to participants.

Project Teams Began to Proactively Include Change Plans

Another important outcome at UCSD was that change management gradually became part of project work.

In the past, project teams might first plan the technology, process, timeline, and resources, and only think about communication and training when it was about to go live. This approach often turned adoption into a last-minute pressure point.

At UCSD, project teams began to think about the people side earlier. Leaders would proactively ask for change metrics. Teams would include change management plans in their projects. A common question gradually formed on campus:

How do we get people to truly adopt this?

This question may seem simple, but it is a crucial watershed for transformation maturity.

UCSD's Impact Spread to the Broader Higher Education Community

UCSD's story did not stop on campus. It also became one of the founding members of the National Consortium for Change & Innovation in Higher Education (NCCI) and spurred other UC campuses to pay attention to and adopt the Prosci methodology.

This illustrates that higher education institutions are facing a common challenge. Universities are no longer just teaching and research units, but also highly complex systems of service, administration, healthcare, technology, and community. As the external environment, student needs, research models, and resource pressures continue to change, universities need not just more projects, but a more mature capability for change.

UCSD's experience provides an example. Large academic institutions can maintain a diverse culture while also establishing a common methodology. Different units do not need to become identical, but they need to use a common language on key transformations.

This is precisely the difference between a campus-wide transformation moving from chaos to coherence.

Once change becomes culture, it remains in the daily rhythm of the campus.

Change Management Lessons from the UCSD Transformation

Although UCSD's case took place in higher education, its lessons are applicable to many large organizations, especially those undergoing multiple transformations simultaneously, with complex cross-departmental collaboration and diverse employee groups.

1. Establish a Common Language Before Demanding Coordinated Action

If each unit describes change in its own way, it's difficult for leadership to judge the real progress. A common language allows problems to be seen earlier and support to be more precise. The role of ADKAR at UCSD was to break down the abstract concept of "resistance" into manageable states. This allowed teams to solve problems together instead of blaming each other.

2. Leaders Must First Change the Questions They Ask

Transformation doesn't succeed just because a leader announces it and others follow. What leaders ask, the organization will value. When leaders only ask about timelines and budgets, teams naturally focus on delivery. When leaders also ask about adoption, desire, ability, and reinforcement, teams will incorporate the people side of change into their core work.

3. Training is Just the Beginning; Continuous Support Forms Culture

A single training session can establish a concept, but culture comes from repeated use. UCSD ensured the methodology was continuously practiced through learning communities, workshops, and coaching support. This is why change management could evolve from a tool into DNA. It no longer relies on a single project or a few experts but gradually enters the daily judgment of managers and teams.

4. Measure Adoption, Not Just Go-Live

A system launch, a process release, or a policy announcement does not equal successful change. The real result is whether people understand, are willing, know how, are able, and continue to work in the new way. UCSD's story reminds all large organizations that the completion point of a transformation is not on launch day, but on the day new behaviors become stable and stick.

UCSD's Real Change Was Putting People Back at the Core of Transformation

UCSD's success was not just because it adopted a certain methodology, nor just because it held large-scale training. The deeper reason is that it made a clear choice.

It elevated change management from an ancillary project task to an organizational capability. It enabled leaders, managers, project teams, and frontline staff to use a common language. It also acknowledged that the core of large-scale transformation is not technology delivery, but human adoption.

This is what makes UCSD's story worth remembering.

A research university full of complexity did not solve chaos with more commands, but built coherence with a common method. It moved from being fragmented to collaborative, from reactive to proactive, and from one project after another, it accumulated new cultural habits.

When change management becomes cultural DNA, transformation is no longer just an annual plan. It becomes the organization's fundamental capability to face the future.