6. Are you ready for change?
When working through any major technology or system transformation, a consideration of the organisation’s readiness for change is as important to the success of the implementation as any consideration of the technical aspects of that transformation.
The term 'change readiness' refers to the will or desire for change within the organisation.
Change usually involves three aspects: culture, people and processes (JISC INFOKIT – Change Management). The process aspect will be dealt with in the Process Map section. In this section we will look at the way in which the culture and the people within an organization can impact on an organisation’s readiness for change.

As shown by the diagram, the three factors have an interconnected relationship.
In the past there has been a tendency to concentrate on the processes part of the diagram.
But even when the processes are right, cultural forces and people’s behavior can be such that they hinder the implementation of change and jeopardize its success.
The Culture of the Organisation
Before looking at the influence of culture on an organisation’s readiness for change, let us first of all consider the actual culture that might be found within HEIs and FECs.
The JISC infoKit ‘Creating a Managed Learning Environment’ identifies three types of culture that can exist within HEIs and FECs within the UK. It describes the characteristics of each culture in the following way.
Collegiate culture – commonly found in the older universities – particularly those with a research focus.
-
Unclear reporting lines and poor coordination, strong local cultures, agendas and identifiers
-
Academic status is perceived as higher than support or administrative functions
-
Strong subject−specific allegiances with academics often feeling a stronger alliance to their subject area and external networks than the institutional mission
Bureaucratic culture – commonly found in FECs and new universities
-
Characterised by strong central management and top−down decision making
-
The hierarchy of control and decision making is clearly established in the administrative and management structures of the institutions
Innovative culture – found in some new universities and colleges and in externally funded research or enterprise centres of older universities
-
Flexible structures geared to respond and adapt quickly to external factors and influences
-
Strong culture of change and innovation
-
Typically activities focused around particular projects and their associated project teams
-
Often characterized by matrix structure of responsibilities by both subject area and functional activity - which itself may be structured around identified strategic priorities.
Working with the culture of the organization
Of the three cultures identified as being present in HEIs and FECs, the one that may present the greatest barrier to change and innovation is the collegiate culture. The innovative culture, by definition, has a built-in readiness for change. Change initiatives within a bureaucratic culture may experience some resistance but its pattern of strong strategic management is likely to be sufficient to drive the initiative forward. In contrast, the collegiate culture, with its many subcultures and its history of autonomy and consensual agreements, can be stubbornly resistant to change.
Working with the collegiate culture
In general, professionals and technical staff will resist changes which they perceive as threatening their core values and practices and which have a negative impact on individuals and which diminish group autonomy (Pennington, 2003). Those seeking to implement change in HEIs, he suggests, should take account of some of the following cultural features:
-
Fuzzy lines of accountability, particularly for academic staff
-
A general lack of extrinsic rewards to shape behaviour plus the tendency to measure academics in terms of their individual performance thus promoting academic independence and individual ownership of knowledge
-
Well developed subject sub-cultures and allegiances that may be stronger than those held with the institution as a whole
-
Organizational divisions between academic departments, administrative and technical support units, different pay awards, physical separation plus the lack of a common culture and language
Top tip!
 |
One very positive thing that occurred during the training was that when we delivered the training we delivered it to mixed groups so the cleaner sat next to the principal. We actively broke down barriers between departments and different levels of the hierarchy. If people from the same department arrived together we separated them. |
-
Rotating management/leadership responsibilities (in some contexts) may make it more difficult for staff to exercise strong leadership and management
Top tip!
 |
If users request information to be hidden (from others), make sure they are aware of the larger impact this would have. A lot of the time they don’t look at the bigger picture, but do appreciate it once it has happened. |
Read more about the experiences of this HEI and their advice with respect to handling particular staff issues.
 |
The sharing of data wasn’t a problem at the time of implementation because the system was only being used by the Student Service Centre (SSC) to record interactions, no sensitive data was being held and no-one else could access the system. However in around 2004 we started to roll the system out to different areas of the university. At this point questions were asked about security. Most areas were happy that personal data should be seen / shared by the system but certain areas wanted tasks and notes created to be private. Privacy of tasks and notes within the Oracle CRM system is something that is provided out of the box, however it only works at an individual level, whereas the data being recorded needed to be shared amongst teams. To resolve this we had to implement some VPD (virtual private database) coding but there were still only a small number of areas requesting this.
Our main issues with security arose recently whilst working on implementing the system into our business school, some areas of which are extremely protective over their contacts, and don’t want people in other areas of the business school seeing them, never mind other faculties. This caused issues because in the first instance they wanted these contacts hidden from everyone, however it is not advisable to do this because if someone can’t see a contact is in the database they will just create it again leading to duplication. Senior members of the business school were also concerned that data was being kept private that should be shared, and a business decision was made that only ‘High Value Customers’ should be secure. A new policy was implemented so if the contact is a ‘High value customer’ a request can be made to senior management who approve or reject the request. If data is secured it was agreed that the contacts name will still be displayed, but any contact details (address, phone numbers, email addresses) will be hidden from view. If the data is secure a message is displayed so that other users know it is a high value customer and if they wish to contact the person they need to obtain the details from the relevant relationship manager. Again this security has been set up using VPD.
From a technical perspective setting up security to the level required was worrying because we did not want to ‘upset’ other members of staff such as the SSC, however if they do stick to their policy and only set up ‘high value customers’ this should not happen as students, alumni, staff and organisation information should still be readily available.
I would advise anyone setting up a new system to ensure they plan security at the start of the project and put a policy in place outlining what information can be ‘hidden’, or whether it should be ‘read only’ but still available. I would advise that minimum personal data can be seen to ensure you are looking at the correct contacts along with any relationships they have. This will avoid duplicate entries which could in turn lead to the customer being contacted by numerous parties having an adverse effect on the customer satisfaction. If users do request information to be hidden, make sure they are aware of the large impact this would have, as a lot of time they don’t look at the bigger picture, but do appreciate it once it has been explained. |
HEI moving from tactical to strategic |
Strategy, leadership, culture and change
The following diagram (adapted from the Manager’s Toolbox, 2008) illustrates quite clearly the relationship between strategy and leadership, culture and change.

|
Strategy
Direction and Focus
Business Portfolio
Resource Management |
 |
 |
Leadership
|
 |
Structure
Roles and Responsibilities
Processes
Management System |
 |
Culture
Values
Mindset
Unspoken Rules |
While it is unlikely that the culture can be changed in the short term, being aware of the barriers can be a useful tool when trying to drive forward any new technology or system.
Ensuring that senior management is aware of the link between their own strategic goals and the changes you want to implement will help gain their full commitment and support of the project. When that commitment is translated into a clear signal across the institution that the change is going to occur then it is much more likely to happen.
Working with the people of the organization
Aside from the culture, you also need to consider the effect of individual people when assessing the institution’s readiness for change and its acceptance of the CRM implementation. Not all staff will greet the proposal for change with enthusiasm. In general, younger staff are likely to feel more positive about the change as they will have invested less time and energy in the old systems.
The JISC infoKit on Change Management comes up with the following list of factors that affect our willingness/reluctance to accept change. Knowing these can help you plan the implementation.
Change is generally met with enthusiasm when:
-
we propose the change
-
we are involved in the design of the change
-
we feel that our opinion/views are heard, and contribute to the new reality
-
we benefit from the change
-
the organisation benefits from the change
-
students and the wider community benefit from the change
-
we dislike the present status quo
-
we are confident about our competence in the new context
-
we trust/respect/like the person/group, proposing the change
-
we can see the big picture and how the change contributes to it
-
we are given support and time to adjust to the changes
-
we are not expected to change too many things at the same time
-
we understand the reasons for the change
-
we believe the change is important
-
we believe the change is necessary
Change in education is met with confrontation when:
-
we are not involved in the change design
-
we feel that our opinion/views are not considered
-
we do not see benefits for ourselves, arising from the change
-
we do not feel the University would benefit from the change
-
we do not feel the students would benefit from the change
-
we do not feel the wider community would benefit from the change
-
we like the present status quo
Top tip!
 |
[One FEC reported that] the CRM development team found that it was important to ‘sell’ the benefits internally during implementation and also to make sure that the system looked as ‘familiar ‘to the people using the system as possible. |
Read how one FEC addressed the concerns of staff about the implementation
 |
Potential users of the CRM have been behind the project from the start, although as with any new system there have been some concerns about how roles might change / adapt, will there be an increased workload, will it produce the reports / information that is currently produced etc. This has been overcome by showing staff during consultancy sessions parts of the CRM that they would be using day-to-day and getting their input.
Senior management has also recognised that the college, except in more customer facing departments, has poor mechanisms for winning and keeping customers and that if more commercial income is to be generated we need to work smarter not harder. CRM has been sold as being part of the solution. |
FEC with strategic approach |
download a self-analysis tool to measure how well you have addressed factors shown to affect staff’s willingness for change
Assessing readiness for change
Implementing a CRM system in your institution will probably involve introducing several changes to current working practices.
One way of assessing an organization/institution’s readiness for change is by examining the three factors – culture, people and processes

This can be done by running focus groups with different categories of staff – eg management, administrators, academics, researchers, technical staff - or through surveys or workshops. The method you choose will depend upon the time and resources available. But the aim is always the same – to obtain as honest assessment as possible of things within the organization/institution.
It may be useful to remember this key point made in the HEFCE Report Effecting Change in Higher Education (2004)
Academics are challenging individuals - it is the nature of academia to debate, discuss and criticise. Engaging in debate is essential if there is to be buy-in from the academic community and criticism should not necessarily be seen as a lack of support.
Assessing culture, people and process
To assess the culture for change we might look at both the leadership and structure of the institution. We might ask questions that allow us to provide an overall rating of the following:
Leadership
-
Management’s willingness to support risk associated with change, encourage new ideas and commit resources to the change effort
-
Clear linkage between vision and the need for change and good communication of ideas
-
Steps taken to gain commitment of people for change - addressing resistance directly and effectively
-
Ensuring that mistakes are used as opportunities for learning
Structure
-
Clarity of roles assigned to people plus freedom to fulfil that role
-
Perception of link between personal growth and achievement of goals tied to assigned job responsibility
-
The degree to which current structure supports and encourages effective performance
To assess the people aspect we might rate the following characteristics.
People
-
The degree of trust and co-operation among employees
-
The perceived fairness of management through a period of change
-
The capability of individuals to understand change and perform skills at the required level
-
Personal identification with the institution, its purpose and values
-
The likelihood of staff remaining with the institution
To assess the degree to which work processes support change we might rate:
Processes
-
The degree to which work processes are flexible and meet customer needs in an efficient manner
-
Those processes used by management to guide and sustain performance
-
Planning, resource allocation, information exchange
-
Training, communication, rewards, performance management and information technology
Based on the ratings of answers to the questions above it is possible to identify where barriers and risks may exist and impact negatively on the change. Taking steps to address any negative issues before the implementation is likely to impact favourably on the change.
Top tip!
“Before you go out to the masses you have to have people lined up to manage it. Just like leadership development you have to start at the top. Once you’ve started the grass roots stuff you must make sure you have the architecture in place to continue with it – otherwise it just fizzles out.
Nicely designed training events will never change a culture. The message has to be embedded in the way you work. There has to be a reward and recognition programme – performance Management Programme and appraisal systems, supervisory management areas - you need to think where are they driving this forward' (The College Way Project)
Download a self-analysis tool for change readiness
Download a very useful change management toolkit for service managers provided by Northumberland County Council.
Alternatively you can access the document directly by going to the ProductShare website
Key factors affecting readiness for change
 |
leadership commitment and empowerment |
 |
good communication throughout the organization |
 |
employees trust management |
 |
management respect the input of the employees |
 |
reward and recognition – people are willing to change if that change is beneficial to them |
Jump to another section
require 'jump.inc'?>
|