Cost Reduction Starts with Anticipating Cost Increases
The first step in reducing costs requires doing the opposite: You must ascertain where costs will increase when you move to the cloud. This might sound counterintuitive, but I’ve seen cost reduction efforts fall flat in organizations when this isn’t done up front. Here’s how it happens.
An organization wants to move IT to the cloud to save money. Then, it finds out that it can’t begin to think about a cloud move without increasing network and internet bandwidth and without procuring additional security services for the cloud, such as secure access service edge.
The best practice for addressing this is for the CIO to present these transitional costs up front to budget decision-makers and bake these new costs into the total cloud budget. This new cloud budget number then becomes the baseline against which cost reductions are measured.
Once you have a total cloud cost picture, you can pursue opportunities for cost reductions. There are a few key areas where you will be able to find them.
READ MORE: Ask yourself these three questions before modernizing your infrastructure.
Look into user subscriptions. As more clinicians and support staff use cloud-based resources, they will independently budget for these without IT’s knowledge. This is especially true for Software as a Service offerings that were previously delivered to end users via download but are now delivered from the cloud. Often, there are more cloud services in use than IT planned for. In some cases, these resources are underused or redundant. This is an area that IT should audit so service duplications or dormancy can be eliminated.
Similar auditing and tracking should be done for cloud storage and processing that goes unused. This usually happens when resources are provisioned and then left in an active state because someone forgets to deprovision them after use. As a result, the healthcare organization keeps paying for them, even though they sit idle.
Finally, you might have cloud providers that provide the same service, or there might be excess, obsolete data stored and paid for in the cloud when it should be purged.
These are all areas where IT can tighten up use, with a goal of paying only for cloud services that are actively being used.