When an organization changes how it attacks a business problem, it’s quite common for these changes to be met with resistance. Information Technology is no exception. Switching from traditional servers, storage, and other on premises IT equipment to cloud versions of these services often triggers resistance from leadership, finance, IT, and end users. Here’s a look at departments and types of resistance IT often hears when making the change to cloud:
- Leadership and Finance – It’s so expensive. Can’t you make do with what we have? It seems way more complex than what you’ve been doing. Isn’t it riskier?
- Information Technology – But we’ve always done it that way. You’re trying to get rid of me and reduce staff headcount. I won’t have anything interesting to work on anymore.
- End users – What’s wrong with the way we’re doing it now? I don’t want anything to change. It’s hard enough now. Why do we want to make it harder?
How do you preemptively address this resistance?
By building a business case for the change involved in moving to the cloud. The business case is critical to your success. This document should directly address challenges in your business and tie the functional IT changes and its outcomes to address the challenges. Examples include:
- Managing risk by reducing downtime, improving application performance, and meeting compliance regulations
- Reducing IT project backlogs and time-to-service by reducing the keep-the-lights-on IT maintenance work
- Helping the leadership and finance teams by accurately quantifying the incremental costs of specific projects
- Addressing the ongoing difficulty in hiring and retaining IT infrastructure staff
- Filling skills gaps with existing staff to improve service levels
Some of these may seem simplistic or obvious. But you must connect the dots from business requirements to IT projects so all departments can clearly see the benefit. If you don’t connect the dots, leadership, finance, IT, and your end users will default to the simplest, least meaningful comparison of old versus new – price.
And, some cloud services just don’t address your organization’s specific business requirements. Choosing the right cloud for the job is the best foundation to building a winning business case.
Do you need help with your business case? My colleagues and I routinely help companies develop justification documents that tie business requirements to changes in IT. Check out this whitepaper, Shift CAPEX to OPEX, or contact me if you’d like to discuss your specific situation.