Objectives of Handling Resistance towards the Cloud Standard
BriscoBikes management have decided on a cloud software solution, which implies that they are aiming for standardization. The impacted users must adapt to a new IT interface and new best-practice business processes. Sometimes, they must also adapt to new roles, responsibilities, and organizational structures. They must build new skills and learn new ways of working. There is likely to be resistance during the transition from the current to the future state.
In general, there are diverse reasons for resistance. Typical drivers for people’s reluctance to change are uncertainty and fear of the unknown, lost established routines and habits, and the anticipation of negative implications (for example, higher workload or job insecurity). Resistance can lead to significant issues, such as project delays, loss in productivity, or poor user adoption. As a result, it is important to actively manage resistance throughout the 4S project.
Situation at BriscoBikes
The project lead IT, Ron Williams, is increasingly concerned about Bart’s negative attitude towards the 4S project. He schedules a call with Sandra and Paul for an exchange on possible interventions.
It's Your Turn: Time to Practice!
Resistance can manifest itself in a broad range of different behaviors. Recognizing these signs at an early stage and trying to understand the underlying reasons is key for addressing and managing resistance effectively.
How much do you already know about resistance in the cloud context?
Take 10 minutes to complete exercise 22 in your workbook.

Approaches for Handling Resistance
In preparation for their meeting, Sandra sends Paul and Ron an overview of typical examples for resistant behavior in cloud projects.

In addition, she shares a slide summarizing potential causes for resistance in the cloud context.

In the following video, Sandra, Paul, and Ron talk about resistance in cloud projects and develop ideas how to change Bart’s attitude towards the 4S project.