How to design a workload-centric IT infrastructure
By Andrew Reichman | Tuesday, October 02 2012
Today's approach to IT infrastructure is inefficient. Your business cares about outcomes and services, but it's built on technology-centric silos. For most firms, each silo is represented by an autonomous department that selects technologies in a vacuum - instead of realizing the value of integration with the other pieces of the firm.
In Forrester's IT Infrastructure Playbook, my colleagues and I maintain that in order to deliver better business results over the next decade, firms must adopt a "workload-centric" approach and design IT infrastructure on what matters most - the workloads - and not the other way around. But what exactly do we mean by workloads? We mean the major end-to-end application or data services that are the center of control and technology selection in your business environment. For example, server virtualization is a key workload because it aggregates many business applications into a common infrastructure.
Workload-centric infrastructure will remedy the ills of today's siloed approach - but getting there requires a different way of thinking about people, process and technology.
People: Align Teams With the Workloads and Applications That Matter Most
Typically, individuals are siloed around elements that they are experts on. With this inside-out approach, it's easy to miss the forest through the trees - technologists know a great deal about the category of gear that they buy and manage, but little about how it is used and what the customers really want. Because each silo functions independently, it's hard to move in a common direction.
In a workload-centric organization, staff members need alignment with the workloads they serve. To minimize disruptions but improve focus on key workloads that matter, Forrester suggests creating a multidisciplinary task force for each key workload. If each server, storage, and network team designates one or two members to attend planning and architecture sessions around workloads, the process of improving communication across departments can begin.
For a bolder approach, firms should eliminate the technology organization entirely. Instead of taking people and funds from each department, forward-looking firms are starting to consider aligning their infrastructure with workloads. For example, consider a VMware, an Oracle, and a mainframe team each reporting to a single leader. While this is clearly a departure from current practice, the improved communication, decision-making, and ability to track the true total cost of a workload is attractive.
Process: Measure the Effectiveness of the Entire Workload
Processes and metrics are rarely shared across server, storage, and network teams. For customers, this results in a confusing list of engineering specifications and finger-pointing at other departments. Customers simply don't care where the bottleneck or error lies, they just want to know when they will be back up and running or why they aren't going fast enough.
In order to help teams pool their information and deliver a customer-centric view, firms should focus on developing a comprehensive service catalog that enables customers to make good decisions. By keeping it simple with gold, silver, or bronze options for the entire workload experience, you can make the process clear for consumers, and avoid the all-too-common problem of having gold for one technology category that only gets bottlenecked by bronze in another.
Technology: Select Based on What's Best for Your Key Workloads
The biggest challenge associated with a workload-centric approach is architecture. Because infrastructure is designed around workloads, deploying a new approach can be done in many ways and will likely involve a combination of solutions. Forrester maintains that these options fit into three main categories: partitioned consolidated systems, converged systems that are factory and vendor optimized for key workloads, and finally, a public cloud model.
Don't Fear Change - Embrace It
Workload-centric models represent a major departure from the way that infrastructure has been deployed for years, so naturally, it can feel uncomfortable. But Forrester believes that it is the right thing for companies - large and small - from both an economics and effectiveness perspective. If you don't do it, the business will find a way around you. Get on this bandwagon now, and give your people the benefit of having internal experts participate in the process to reinvent the way that that you approach business technology.
Andrew Reichman is a Principal Analyst at Forrester Research serving Infrastructure & Operations Professionals.
In Forrester's IT Infrastructure Playbook, my colleagues and I maintain that in order to deliver better business results over the next decade, firms must adopt a "workload-centric" approach and design IT infrastructure on what matters most - the workloads - and not the other way around. But what exactly do we mean by workloads? We mean the major end-to-end application or data services that are the center of control and technology selection in your business environment. For example, server virtualization is a key workload because it aggregates many business applications into a common infrastructure.
Workload-centric infrastructure will remedy the ills of today's siloed approach - but getting there requires a different way of thinking about people, process and technology.
People: Align Teams With the Workloads and Applications That Matter Most
Typically, individuals are siloed around elements that they are experts on. With this inside-out approach, it's easy to miss the forest through the trees - technologists know a great deal about the category of gear that they buy and manage, but little about how it is used and what the customers really want. Because each silo functions independently, it's hard to move in a common direction.
In a workload-centric organization, staff members need alignment with the workloads they serve. To minimize disruptions but improve focus on key workloads that matter, Forrester suggests creating a multidisciplinary task force for each key workload. If each server, storage, and network team designates one or two members to attend planning and architecture sessions around workloads, the process of improving communication across departments can begin.
For a bolder approach, firms should eliminate the technology organization entirely. Instead of taking people and funds from each department, forward-looking firms are starting to consider aligning their infrastructure with workloads. For example, consider a VMware, an Oracle, and a mainframe team each reporting to a single leader. While this is clearly a departure from current practice, the improved communication, decision-making, and ability to track the true total cost of a workload is attractive.
Process: Measure the Effectiveness of the Entire Workload
Processes and metrics are rarely shared across server, storage, and network teams. For customers, this results in a confusing list of engineering specifications and finger-pointing at other departments. Customers simply don't care where the bottleneck or error lies, they just want to know when they will be back up and running or why they aren't going fast enough.
In order to help teams pool their information and deliver a customer-centric view, firms should focus on developing a comprehensive service catalog that enables customers to make good decisions. By keeping it simple with gold, silver, or bronze options for the entire workload experience, you can make the process clear for consumers, and avoid the all-too-common problem of having gold for one technology category that only gets bottlenecked by bronze in another.
Technology: Select Based on What's Best for Your Key Workloads
The biggest challenge associated with a workload-centric approach is architecture. Because infrastructure is designed around workloads, deploying a new approach can be done in many ways and will likely involve a combination of solutions. Forrester maintains that these options fit into three main categories: partitioned consolidated systems, converged systems that are factory and vendor optimized for key workloads, and finally, a public cloud model.
Don't Fear Change - Embrace It
Workload-centric models represent a major departure from the way that infrastructure has been deployed for years, so naturally, it can feel uncomfortable. But Forrester believes that it is the right thing for companies - large and small - from both an economics and effectiveness perspective. If you don't do it, the business will find a way around you. Get on this bandwagon now, and give your people the benefit of having internal experts participate in the process to reinvent the way that that you approach business technology.
Andrew Reichman is a Principal Analyst at Forrester Research serving Infrastructure & Operations Professionals.
Follow CIO on
Twitter @cio_nz
Facebook
LinkedIn
Download CIO for your tablet here.
Click here to subscribe to CIO.
Sign up to receive free CIO newsletters.
Send news tips to divina@cio.co.nz
 |
Tidal wave alert
Ready or not, mobility is here to stay, say three IT leaders who share their experiences on the road to BYOD.
IPv6: A new headache or huge opportunity?
IPv6 is here, it's real and it's growing, according to local industry bodies. Deploying IPv6 may not be high on your list of priorities at the moment, but if you start planning now you could avoid escalating costs.
MOST POPULAR
CONNECT WITH @ CIO NZ
CIO NZ has now reached LinkedIn! Join to expand your networks and meet others interested in business technology leadership and innovation.
SUBSCRIBE
CIO is bringing together the best of MIS NZ and CIO, the new look CIO is the only magazine that focuses on the unique management needs of senior IT professionals.
NEWSLETTERS
MIS 100 REPORT
MIS100 2012The definitive guide to New Zealand's largest and most significant ICT users.
READ NOW »
