1

Module 2 SLP

Damarcus Tutt

Trident University International

BUS503

September 15, 2024

 2

Individual Resistance to Change

Resistance to change is a phenomenon that occurs both in personal and organizational

contexts, where individuals exhibit reluctance to adopt new behaviors, technologies, or

processes. In the IT field, where rapid technological advancement often necessitates frequent

change, resistance can manifest in various forms, from hesitation to learn new systems to

outright refusal to abandon established methods. In this paper, I will describe my experience of

resisting a workplace change, analyze the reasons behind my resistance, and reflect on the

insights gained from studying change management theory.

During my time working as a software developer, our team was informed of a significant

shift in the development framework we had been using for years. That was when the company's

management agreed to move from the old operation and adopt a new and more advanced

software environment with better performance and optimization. This change meant we had to

leave behind the ordinary tools and workflow that we were used to and replace them with new,

tougher models that needed a lot of training. At first, I wouldn't say I liked this transition because

I wanted to get used to the old method and remain there for a long time. My experience had

equipped me with years of practice in mastering the already set paradigm of working; thus, I was

at ease and could easily maneuver within the system. The concept of moving from one system,

which I was used to, to another system, which I was not familiar with, seemed very challenging,

and I was calm that in the process of adapting to the new tools, my efficiency would reduce.

Moreover, I also thought that my skills, which used to be regarded as necessary, might become

useless, threatening my job security (Iverson, 2010).

Several factors contributed to my resistance to this change. The fear of the unknown was

a significant reason for my reluctance to accept the new framework. The unfamiliarity with the
 3

new system, coupled with concerns about how long it would take to learn, heightened my

anxiety. This fear was exacerbated by a lack of clear information on how the transition would be

managed and whether sufficient training would be provided (Iverson, 2010). Another major

reason was the loss of competence. I had developed a strong skill set in the legacy system, which

was highly valued in the organization. The new framework made me feel like a novice again, as I

had to relearn many basic tasks. This potential loss of competence was unsettling (Campbell,

2014). Job security concerns were also prevalent. In the rapidly changing IT landscape, I hoped

that if I adapted quickly, I might be left behind, potentially jeopardizing my position within the

company. This concern was extreme given the competitive nature of the tech industry.

Additionally, the comfort with established routines played a role. Having worked with the same

framework for several years, I had developed efficient workflows, and the new framework

disrupted these routines, forcing me to step outside my comfort zone.

The organization and I took several actions to decrease resistance to the change.

Leadership eventually provided more detailed communication about the reasons for the change

and how the transition would occur. They highlighted the new system's benefits and provided

case studies from other organizations that had successfully adopted it (Campbell, 2014). The

company also offered extensive training sessions, workshops, and ongoing technical support to

help employees adjust to the new framework. This helped alleviate some of my concerns about

learning the new system. Additionally, my colleagues, many of whom were also resistant at first,

formed study groups to help each other learn the new framework. This sense of camaraderie

made the transition less daunting.

Over time, the change was successfully implemented across the organization. Although

there were initial productivity slowdowns, these were mitigated by the company's training and
 4

support. I regained my confidence and competence as I became more familiar with the new

framework. My concerns about job security and loss of skill value were addressed as I realized

that mastering the new system made me more valuable in the long term. Of the key concerns I

have voiced, which included uncertainly, perceived lack of competence or skill, and job

insecurity, all of them were easily solved by regular enculturation and training apart from

leadership and subordinate support. The top management of the company knew that there was

going to be some resistance and was able to counter this, which did not make the transition to use

the new technology difficult.

One key insight I have gained from this experience is the importance of open

communication in managing resistance to change. Had the leadership been more forthcoming

with information from the outset, my initial resistance might have been less severe. Uncertainty

breeds fear, and by clearly communicating the reasons for the change, the benefits it would

bring, and the support available to ease the transition, leadership can mitigate much of the

resistance that arises from fear of the unknown (Coleman & Thomas, 2017). Additionally, I now

understand that resistance often stems from a fear of losing one's sense of competence or value.

When people are used to being experts in their field, the prospect of returning to a "beginner"

status can be unsettling. Acknowledging this fear and providing training and support can go a

long way toward reducing resistance.

Having reflected on this experience, I now see how I can apply the lessons learned to

future situations where I may be responsible for leading change. First, I would prioritize early

and transparent communication to ensure all stakeholders understand the rationale behind the

change and the support they will receive. Establishing trust is critical, and engaging employees in

the process makes them more likely to feel ownership over the change rather than seeing it as
 5

something being imposed on them (Franklin, 2014). Furthermore, I would emphasize the

importance of providing adequate training and resources. As the experience with the new

software framework showed, employees are more willing to embrace change if they feel they are

given the tools they need to succeed. I would also encourage peer collaboration, as the sense of

community that developed among my colleagues made the transition less intimidating.

Moving forward, I will approach change with a more open mind. I recognize now that

resistance often stems from a place of fear, and by confronting that fear and seeking out support,

the process can be much smoother. I have also learned that change is an opportunity for personal

and professional growth. Rather than viewing it as a threat, I will strive to see change as a chance

to expand my skill set and enhance my value within the organization.

In conclusion, resistance to change is a natural human response, particularly in fields like

IT, where rapid technological advancement is the norm. My experience of resisting the adoption

of a new software framework highlighted several key factors contributing to resistance, including

fear of the unknown, loss of competence, and concerns about job security. However, these fears

can be addressed with clear communication, training, and support, leading to successful change

implementation. The insights gained from this experience will guide my future approach to

change, both as an individual and a leader, ensuring that I am better equipped to navigate and

manage resistance.
 6

References

Campbell, H. (2014). Managing organizational change: A practical toolkit for leaders (3.1).

[Books24x7 version]. Available in the Trident Online Library.

Coleman, S., & Thomas, B. (2017). Organizational change explained: Case studies on

transformational change in organizations (Chapter 6). [Books24x7 version]. Available in

the Trident Online Library.

Franklin, M. (2014). Agile change management: A practical framework for successful change

planning and implementation (Chapter 5). Kogan Page Ltd.

Iverson, L. (2010). The science of change management: The 7 phases of change & breaking

through resistance to change. [Books24x7 version]. Available in the Trident Online

Library.