Create business alignment in cloud management
In on-premises environments, IT assets (applications, virtual machines, VM hosts, disk, servers, devices, and data sources) are managed by IT to support workload operations. In IT terms, a workload is a collection of IT assets that support a specific business operation. To help support business operations, IT management delivers processes that are designed to minimize disruptions to those assets. When an organization moves to the cloud, management and operations shift a bit, creating an opportunity to develop tighter business alignment.
The first step in creating business alignment is to ensure term alignment. IT management, like most engineering professions, has amassed a collection of jargon, or highly technical terms. Such terms can lead to confusion for business stakeholders and make it difficult to map management services to business value.
Fortunately, the process of developing a cloud adoption strategy and cloud adoption plan creates an ideal opportunity to remap these terms. The process also creates opportunities to rethink commitments to operational management, in partnership with the business. The following article series walks you through this new approach across three specific terms that can help improve conversations among business stakeholders:
- Criticality: Mapping workloads to business processes. Ranking criticality to focus investments.
- Impact: Understanding the impact of potential outages to aid in evaluating return on investment for cloud management.
- Commitment: Developing true partnerships, by creating and documenting agreements with the business.
Underlying these terms are classic IT terms such as SLA, RTO, and RPO. For more information on mapping specific business and IT terms, see Business commitment in cloud management.
Operations management workbook
To help capture decisions that result from this conversation about term alignment, an operations management workbook is available on our GitHub site. This workbook does not perform SLA or cost calculations. It serves only to help capture such measures and forecast return on loss-avoidance efforts.
Alternatively, these same workloads and associated assets could be tagged directly in Azure, if the solutions are already deployed to the cloud.
Start creating business alignment by defining workload criticality.