Tag Archives: ITaaS

What I Learned from VMware’s Internal Private Cloud Deployment

By Kurt Milne

kurtmilne-cropFor seven years as an industry analyst, I studied top-performing IT organizations to figure out what made them best-in-class. And after studying 30 private cloud early adopters in 2011, I co-authored a book about how to deploy private cloud.

But after joining VMware last year, I’ve had the opportunity to spend six months working closely with VMware’s IT team to get an in-depth understanding of our internal private vCloud Suite deployment.

In this multi-part blog series, I’ll write about what I’ve learned.

Lesson learned – The most important thing I learned, and what really reframed much of my thinking about IT spending, is that VMware IT invested in our private cloud strategy to increase business agility.  And that effort drastically lowered our costs.

Breaking it down:

1. We made a strategic decision to try something different.

Over the years, I’ve studied companies that use every form of squeezing IT budgets there is. But what happens with a “cut till it hurts” or a “cut until something important breaks” approach is that the primary objective of lowering IT budgets is often achieved. But it also leaves IT hamstrung and unable to meet the needs of the business. An unbalanced focus on cost cutting reduces IT’s ability to deliver. That in turn lowers business perception of IT value, which further focuses efforts on cost cutting. Define “death spiral.”

VMware didn’t follow that path when we decided to invest in private cloud. We justified our “Project OneCloud” based on belief that that the traditional way of growing IT capabilities wouldn’t scale to meet our growth objectives. We have doubled revenue and headcount many times over the last 10 years. The IT executive team had the insight to realize that a linear approach of increasing capacity by buying more boxes and adding more headcount would not support business needs as we double in size yet again. We are no longer a startup. We have grown up as a company. We had to try a different approach.

Apparently VMware IT is not alone with this thinking. IT Under Pressure: McKinsey Global Survey results shows a marked shift in 2013 as IT organizations are using IT to improve business effectiveness and efficiency, not just manage costs.

2. Effective service design drove adoption.

What really enabled our private cloud success was broad adoption. There is a commitment and investment in private cloud that requires broad adoption to justify the cost and effort. The promise of delivering IT services the same old way at lower cost didn’t drive adoption. What drove adoption was a new operating model focused on delivering and consuming IT as a service. Specifically, abstracting infrastructure delivered as basic compute, network, and storage as a service. Then designing IT services for specific groups of consumers that allowed them to get what they need, when they needed it. That included application stacks, dev/test environments, and any other business function that depends on IT infrastructure (almost all do in the mobile-cloud era). We strove to eliminate the need to call IT, and also eliminated tickets between functional groups within IT.

Ten different business functions — from sales, marketing, and product delivery, to support and training — have moved their workloads to the cloud. Many have their own service catalog with a focused set of services as front end on the private cloud. Many have their own operations team who monitor and support automation and process that are built on top of infrastructure services.

Carefully designing IT services, then giving people access to get what they need when they need it without having to call IT — is key to success.

3. Broad adoption drove down costs via scale economies.

We started with one business group deploying sales demos and put their work in a service catalog front end on the private cloud. Then we expanded onboarding other functional groups to the cloud. One trick – and that is to develop a relationship with procurement. Any time someone orders hardware within the company, get in front of the order and see if they will deploy on private cloud instead.

Make IT customers’ jobs easier. Accelerate their time to desired results. Build trust by setting realistic expectations, then delivering per expectation.

Three primary milestones:

  1. Once we onboarded a few key tenants and got to ~10,000 VMs in our cloud, we lowered cost per general purpose VM by roughly 50 percent. With a new infrastructure as a service model that allowed consumers to “outsource infrastructure” to our central cloud team — and at a much lower cost per VM — word got out, and multiple other business groups wanted to move to the cloud.
  2. Once we onboarded another handful of tenants and got to ~50,000 VMs in our private cloud, we lowered cost per general purpose VM by another 50 percent. We were surprised by how fast demand grew and how fast we scaled from 10,000 to 50,000 VMs.
  3. We are “all in” and now on track to meet our goal of having around 95 percent of all our corporate workloads in private or hybrid cloud (vCloud Hybrid Service) – for a total of around 80,000 to 90,000 VMs. We expect cost per VM to drop another 50 percent.

So we set out to increase agility and better meet the needs of the business, delivered services that made IT consumers’ jobs easier, and as a result we dropped our cost per VM by ~85 percent.

Key takeaways:

  • Our private cloud goal was to reshape IT to better meet revenue growth objectives.
  • We transformed IT to deliver IT services in a way that abstracted the infrastructure layer and allowed various business team to “outsource infrastructure.”
  • Ten different internal business groups have moved workloads to private cloud.
  • Less focus on infrastructure and easy access to personalized services made it easier for IT service consumers to do their jobs and focus more on their customers.
  • A new operating model for IT and effective service design drove adoption.
  • Broad adoption drove down costs. By ~85 percent.

Below are links to two short videos of VMware IT executives sharing their lessons learned related to cost and agility. In my next post, I’ll talk about what I learned about a new operating model for IT.

Follow @VMwareCloudOps and @kurtmilne on Twitter for future updates, and join the conversation by using the #CloudOps and #SDDC hashtags on Twitter.









Aligned Incentives – and Cool, Meaningful New Jobs! – In the Cloud Era

By: Paul Chapman, VMware Vice President Global Infrastructure and Cloud Operations

Transforming IT service delivery in the cloud era means getting all your technical ducks in a row. But those ducks won’t ever fly if your employees do not have aligned incentives.

Incentives to transform have to be aligned from top to bottom – including service delivery strategy, operating model, organizational construct, and individual job functions. Otherwise, you’ll have people in your organization wanting to work against changes that are vital for success, and in some cases almost willing for them to fail.

This can be a significant issue with what I call ‘human middleware.’ It’s that realm of work currently done by skilled employees that is both standard and repeatable at the same time: install a database; install an operating system; configure the database; upgrade the operating system; tune the operating system, etc..

These roles are prime for automation and/or digitization – allowing the same functions to be performed more efficiently, more predictably, game-changingly faster, and giving the IT organization the flexibility it needs to deliver IT as a Service.

Of course, automation also offers people in these roles the chance to move to more meaningful and interesting roles – but therein lies the aligned incentive problem. People who have built their expertise in a particular technology area over an extended period of time are less likely to be incentivized to give that up and transition to doing something ‘different.’

Shifting Roles – A VMware Example

Here’s one example from VMware IT – where building out a complete enterprise SDLC instance for a complex application environment once took 20 people 3-6 weeks.

We saw the opportunity to automate the build process in our private cloud and, indeed, with blueprints, scripting, and automation, what took 20 people 3-6 weeks, now takes 3 people less than 36 hours.

But shifting roles and aligning incentives was also very critical to making this happen.

Here was our perspective: the work of building these environments over and over again was not hugely engaging. Much of it involved coordinating efforts and requesting task work via ticketing systems, but people were also entrenched in their area of expertise and years of gained experience, so they were less inclined to automate their own role in the process. The irony was that in leveraging automation to significantly reduce the human effort and speed up service delivery, we could actually free people up to do more meaningful work – work that in turn would be much more challenging and rewarding for them.

In this case, employees went from doing standard repeatable tasks to high order blueprinting, scripting, and managing and tuning the automation process. In many cases, though, these new roles required new but extensible skills. So in order to help them be successful, we made a key decision: we would actively help (in a step-wise, non-threatening, change-management-focused way) the relevant employees grow their skills. And we’d free them up from their current roles to focus on the “future” skills that were going to be required.

Three New Roles

So there’s the bottom line incentive that can shift employees from undermining a transformation to supporting it: you can say, “yes, your role is changing, but we can help you grow into an even more meaningful role.”

And as automation frees people up and a number of formerly central tasks fall away, interesting new roles do emerge – here, for example, are three new jobs that we now have at VMware:

  •  Blueprint Designer – responsible for designing and architecting blueprints for building the next generation of automated or digitized services.
  •  Automation Engineer – responsible for engineering scripts that will automate or digitize business process and or IT services.
  •  Services Operations Manager – responsible for applications and tenant operation services in the new cloud-operating model.

The Cloud Era of Opportunity

The reality is that being an IT professional has always been highly dynamic. Of the dozen or so different IT positions that I’ve held in my career, the majority don’t exist anymore. Constant change is the steady state in IT.

Change can be uncomfortable, of course. But given its inevitability, we shouldn’t – and can’t – fight it. We should get in front of the change and engineer the transformation for success. And yet too frequently we don’t – often because we’re incented to want to keep things as they are. Indeed, misaligned incentives remain one the biggest impediments to accelerating change in IT.

We can, as IT leaders, shift those incentives, and with them an organization’s cultural comfort with regular change. And given the positives that transformation can bring both the organization and its employees, it’s clear that we should do all we can to make that shift happen.

Major Takeaways:

  • Aligning incentives is a key part of any ITaaS transformation
  • Automation will eliminate some roles, but also create more meaningful roles and opportunities for IT professionals
  • Support, coaching, and communication about new opportunities will help accelerate change
  • Defining a change-management strategy for employee freedom and support for their transition are critical for success

Follow @VMwareCloudOps and @PaulChapmanVM on Twitter for future updates, and join the conversation by using the #CloudOps and #SDDC hashtags on Twitter.

A VMware Perspective on IT as a Service, Part 3: Agility, How to Measure it, and Keep Improving it Over Time

By: Paul Chapman, VMware Vice President Global Infrastructure and Cloud Operations

In this series of posts, I’m offering a VMware Corporate IT perspective on the journey to IT as a Service, looking at how we made the change ourselves, sharing some of the many benefits that ITaaS is bringing us, and offering some insights on how – if you’re considering taking the plunge – you might successfully make the transition yourself.

I started out by offering my take on the journey to IT as a Service. Then I shared the story of how our applications operations group transformed its operations by shifting to the Software Defined Data Center. This time, I’ll explain how we think of agility at VMware.

If I had to pick just two reasons why we decided to transition to IT as a Service (ITaaS) at VMware, it was that:

a) It would let IT deliver at the speed of business,


b) It would make IT a game changer – by providing business transformation through IT transformation, we’d be helping the business scale and grow.

But, if our vision embraced getting IT to run at the speed of business, delighting our users every day, and turning IT into an innovation center and not a roadblock, agility, efficiency, and an ITaaS mindset were the engines that would get us there.

Importantly, though, we put agility first. Many IT businesses think of IT as a cost center and put efficiency and cost first. While the “cut ‘till it hurts” approach can drive down costs and make efficiency metrics looks better, it can also leave IT hamstrung and unable to innovate and support changing business needs. Our big insight was that investments that significantly improved agility ALSO resulted in higher efficiency and service quality gains. By leading with agility, we could achieve both.

How We Think of Agility

When we think about agility, it’s on three levels. We’re aiming for:

  1. Zero demand. Every time anyone has to make an IT request, that’s a potential point of friction. They’ve had to stop what they’re doing and ask for something to be done, and then wait even longer for a response before they can move on. So our goal has been to completely remove their need to ask in the first place. You’d be surprised how much low hanging fruit there is here. There are lots of diamonds in the backend data, as long as IT studies it with the mindset of elimination vs. just resolution speed and SLA improvements.
  2. More self-service. Self-service is another key component to agility and ITaaS. The alternative is that our customers have to go to a help desk, the last place they should go, and wait for someone to get back to them through some kind of queued ticketing system. Taking IT out of the equation and giving users the ability to self-serve significantly increases speed-to-solution and user satisfaction.
  3. The ability to serve complex requests. If you have made progress on the first two, the calls and tickets you do get will by default feature more complex or lower volume requests. So what’s the best way to respond to them? Here’s how we do it: We’ll see, for example, that on average it’s taking n days to deliver or solve service request x. Then we ask (if we cannot eliminate or provide self-service) how can we slice up these requests, automate workflow and individual tasks, and reduce handoffs as much as possible? It’s not a one-time deal, it’s a process and an incrementally ongoing quest to reduce the time-to-deliver on the demand that comes to IT. Hiring or moving people to focus on this vs. volume-based hiring to solve requests is far more likely to have a transformative impact on IT and its agility in serving customer needs.

Measuring Agility

The shorter we can make the delivery time for any service, even the most complex, the better off our customers are in terms of being able to get what they need to do their job. So how do we measure our responsiveness?

Our goals here are very aggressive. We’re looking to reduce the time it takes to deliver a particular service from months, days, and weeks, to hours, minutes, and seconds, and in some cases eliminate the need altogether.

Specific examples of metrics I like to use to gauge my organizing’s agility include:

  • The number of service requests that have been completely eliminated either through resolving at root the need in the first-place and or through fully automating solutions
  • The number of service requests that are self-served
  • If no automation or elimination is possible, then the cost- and speed-to-deliver of the solution from time of user creation
  • The services offered through the ‘outside-in’ IT Service Catalogue

I am not a fan of time-based SLAs because I think it promotes the wrong behavior – customer satisfaction, elimination, automation, and self service are far more meaningful than time-based SLAs.

More fundamentally, IT should always be trying for an outside-in view and not an inside-out view. All too often, Service Catalogues are based on IT defining its services and how a customer can “order them” vs. offering the services the “customer needs and wants.”

Predicting Demand in a Ticketless World

Done right, agility means offering services on-demand before the customer even makes a request. It’s a nice idea, but how does IT predict what issues might come up so that it can preemptively have solutions ready before they’re needed?

At VMware, one approach has been to significantly increase focus and investment on having the right forensics in place. This lets us go from reactive, to proactive, to predictive, and to be very aware of everything that is going on in the environment.

In addition, we monitor internal social communications for sentiment and issues that might be brewing. Today we see a lot of activity on our internal Socialcast collaboration site, which is helping us get ahead of issues as well as have a more intimate relationship with our users.

Then we add transparency. Internally, we have a portal that shares the quality of service delivery at any given point. So if we’re seeing degradation in a network connection, for example, or a quality of service issue with a particular application, anybody in the company can see what we know, what we’re looking at, and what we’re communicating about the issue.

Key Takeaways:

  • Agility, efficiency, and organizational mindset are at the heart of solving the movement to ITaaS.
  • Agility inevitably drives increased efficiency, but efficiency alone won’t lead to meaningful agility gains.
  • At VMware, we think of agility in terms of customer-centric, zero demand, automation, and self-service.
  • We measure agility in terms of speed and cost.
  • Forensics and transparency are key to predicting demand, and identifying and communicating issues.
  • Without true agility, it is very painful and costly for organizations to scale and to remain nimble at the same time.
  • The power of automation plus the power of a self-service mindset lets IT organizations help scale the business in a customer centric, cost-effective way.

You can find parts 1 and 2 of this series here and here. Next time, I’ll explain what it took to stand up and run our own internal private cloud with ~50k VM’s.

Follow @VMwareCloudOps and @PaulChapmanVM on Twitter for future updates, and join the conversation by using the #CloudOps and #SDDC hashtags on Twitter.

A VMware Perspective on IT as a Service, Part 2: An In-house Example of IT Transformation

By: Paul Chapman, VMware Vice President Global Infrastructure and Cloud Operations

In this series of posts, I’m offering a VMware Corporate IT perspective on the journey to IT as a Service (ITaaS), looking at how we adopted the movement ourselves, sharing some of the many benefits that ITaaS is bringing us, and offering some insights on how – if you’re considering taking the plunge – you might successfully make the transition yourself.

Last time, I outlined the context for the movement to IT as a Service – one that suggests we’re now at a point where IT can no longer hide behind the complexity of IT environments, and where IT organizations need to deliver on new consumer expectations of service delivery if they are to have the agility and efficiency to deliver at the speed of business.

Today, I’m going to share the story of one of the functional IT groups at VMware – our Applications Operations group – that has transformed by shifting to a focus on agility and automation, with game changing results. If you’re curious to learn more, check out the full case study, or a short summary video here.

A Problem with Process

Here’s what happened: The Cloud Operations group within VMware corporate IT oversees the support of a portfolio of ~200+ business applications. The application operations team (AppOps) provisions and manages very complex SDLC development and test environments for a team of ~600+ global developers and quality assurance engineers who work on the VMware program portfolio.

By the middle of 2012, the AppOps team realized that it faced a serious issue with provisioning these environments.

As things stood, their processes were:

  • Slow – Manually provisioning a dev/test SDLC instance for a full enterprise applications ecosystem was taking in the range of 4-6 weeks per instance,
  • Disruptive – Hundreds of developers had to wait for a reliable new instance for extended periods of time, multiple times during the lifecycle,
  • Risk – Cascading delays created risk, keeping other portfolio projects from being able to start and/or complete on time, potentially costing millions of dollars in delays,
  • Inconsistent – Quality and lead times were unpredictable, varying with schedule complexity, different outcomes from manually repeated processes, and the capacity and availability of team members distributed around the globe.

The knock-on impact of a delay was very costly. Every time a new environment experienced delays, developers were idle and millions of dollars were at stake. This made portfolio planning inordinately difficult. We could have shrunk the portfolio and slowed the delivery of business critical programs in response, but that was unacceptable given our overall corporate growth objectives.

Then, not surprisingly, IT was therefore under considerable pressure to increase its agility, speed, and throughput.

Not the Easy Fix

Clearly, AppOps needed to reduce provisioning times and increase schedule predictability and service quality.

One way to do that would have been to try and improve the efficiency of the large “human middleware” they already had in place, applying lean methodologies and trying to be as “efficient” as possible when executing standard repeatable tasks.

However, a thorough process review made it clear that more than a continuous efficiency program was required. The primary issue was that they were scheduling and managing a large number of people who were performing, in the most part, skilled but repeatable tasks. Even with an improved provisioning process, the human-middleware problem would never fully go away, as speed and predictably could never reach the desired goals.

Instead, the AppOps group chose to completely replace and automate its provisioning process using a VMware on-premises private cloud, based on the software-defined data center. This would completely automate SDLC instance provisioning, using blueprints, policies, and automation and management capabilities using the VMware vCloud® Suite and other adjacent tools.

If they were to succeed, two factors would be critical:

  • Ambitious, long term objectives. To be successful, any solution needed to be game changing – instead of making incremental improvements to the existing process, AppOps was looking to turn a process that traditionally took 4-6 weeks to into one taking just a matter of hours. Solving this problem required a radically different approach that was built from the ground up.
  • An available private cloud. VMware had already deployed, at scale, its private cloud (called ‘Project OneCloud’), delivering infrastructure-as-a-service (IaaS) capabilities for internal use. With vCloud Suite’s automation and management capabilities, the private cloud could host all non-production SDLC instances – eliminating the need for lengthy hardware provisioning cycles.

By late 2012, the AppOps team was ready to start building the new, automated and streamlined provisioning platform, setting itself the goal of deploying all Dev/Test SDLC instances within 24 hours of a request.

Doing this meant driving transformation in three areas:

  • Architecture – Shifting from a traditional virtualized data center environment to a SDDC private cloud and deploying cloud management with automation capabilities to provision complex SDLC environments. Each instance contains over 30 applications, including the company’s full ERP, custom applications, portals, middleware, IDM, BI, webservers, app servers, integrations, databases, and more.
  • Operations – Converting manual, time consuming processes to an end-to-end, automated scripted process with blueprint-based provisioning. Key employee transitions would include investments in change-management and supporting employees through training and education, moving them to more value-added and meaningful roles in the new cloud operating model.
  • Financial – Moving from a project-capex based infrastructure funding model to a service-opex consumption and chargeback model. Instead of incurring costs for building and maintaining infrastructure to support the virtual machines, IT could pass the cost of workloads to individual project requestors. In turn, because of the ability to provision quickly and provide transparent opex service costs, there has been a higher increase in de-provisioning instances which has in turn increased infrastructure utilization and reduced spend on net-new infrastructure.

The Payoff and Business Benefit

Phase one of the project – deploying basic automated provisioning and management capabilities – has now been completed. 2,800 virtual machines that support dev/test instances have been transitioned to the new OneCloud environment, resulting in game-changing benefits:

  • Reduced provisioning time from 4-6 weeks to 36 hours: on track to achieve goal of <24 hours,
  • Increased productivity of 600 developers by as much as 20 percent,
  • Improved service quality so that AppOpps can now consistently say “Yes” to all project requests in the time required,
  • Saved the business $6M per year in infrastructure and operating costs,
  • Moved people to higher-order, more meaningful IT roles, e.g. blueprinting and automation design.

Phase two will focus on further enhancing automation and management capabilities and transitioning more pre-production environments to the private cloud.

Lessons Learned

  • Agility investments are self-sustaining. Investing in increased agility yields significant additional benefits, such as substantially reduced operating and infrastructure costs, and increasing service quality.
  • vCloud Suite is a full solution. The AppOps team implemented vCloud Suite to automate provisioning and management of SDLC instances. Out-of-box functionality let them automate and manage a wide range of core tasks. The availability of SDKs and APIs let them deliver additional automation and management functionality through adjacent tools.
  • On-demand capabilities change IT service consumption. SDLC instances are no longer viewed with the same risk outlook as before. Where developers and applications owners formerly felt the need to keep an instance open for multiple and/or on-going projects, AppOps can now release those instances back into the provisioning pool in a “disposable infrastructure” service consumption model.
  • APIs replace ticketing and late-night meetings. A service catalog and API calls help IT clarify and simplify communication about the services AppOps delivers and what its customers can expect in return. Efficiency has replaced the time-consuming, difficult, and highly-variable task of scheduling and coordinating work between multiple, globally distributed teams.

Key Takeaway:

The VMware corporate IT organization decided to invest in improving agility, and, as a byproduct, not only increased service speed and quality, but also dramatically lowered IT infrastructure and operating costs.

Next time, I’ll look at agility: how we measure it and how we keep continuously improving. In Part 4, I’ll explain what it took to stand up and run our own internal private cloud that so far include  ~50k VMs.

For more information in the meantime, please see:

Follow @VMwareCloudOps & @PaulChapmanVM on Twitter for future updates, and join the conversation by using the #CloudOps and #SDDC hashtags on Twitter.

A VMware Perspective on IT as a Service, Part 1: The Journey

By: Paul Chapman, VMware Vice President Global Infrastructure and Cloud Operations

At VMware, we now live and breathe IT as a Service (ITaaS). It’s a relatively new phenomenon, but many companies are beginning to make the shift.

In this short series of posts, I’m going to offer a VMware Corporate IT perspective on the journey to IT as a Service, looking at how we ourselves made the change, sharing some of the many benefits that ITaaS is bringing us, and offering some insights on how – if you’re considering taking the plunge – you might successfully make the transition yourself.

A Long Time Coming

First up, it’s worth remembering that the concept of IT as a Service is not that new. As a community of IT professionals, we’ve been talking about it for at least a decade. But for a long time, the obvious and daunting challenge of managing very complex IT infrastructures gave us an excuse not to act.

Fast forward to today: We now have Software as a Service, Infrastructure as a Service, Platform as a Service and so on – which creates a whole new consumption model for IT. These innovations make it very hard for IT organizations to keep hiding behind complexity as an excuse not to act.

Meanwhile, though, the pace of technological change has all but outstripped and outpaced internal IT’s ability to keep up with consumer-like demand, and that’s spurred the rise of successful innovation silos such as the Workdays, the Salesforce.coms, and the Amazons of the world – that have been happy to do the work instead.

You could say this is revenge of the business, with lines of business and developers now happy to bypass the IT infrastructure organization entirely, turning to external providers offering on-demand services and innovative business models.

In the face of this, most IT organizations struggle to keep up with demand for new services. Quite frankly, I think that even if they were funded to fully support the demand, most IT organizations still wouldn’t be able to keep up using traditional service delivery models. I think the inefficiencies and the lack of agility rooted in a heavy-human and “process-bound” way of doing things would just get in the way.  Even simply maintaining the status quo these days is enough to overwhelm and exhaust personnel.

Not Whether, But How Fast

That’s certainly how we saw things here at VMware. It wasn’t so much a question of whether to go on the journey to IT as a Service, but a question of how fast we could get there. In 2010, 99% of our servers were virtualized, and 20% of business applications were delivered by SaaS vendors. We saw the power of the shift to more agile service delivery. We established an executive mandate to further transform our IT services as soon as possible, and we also started to take an outside-in look vs. an inside-out look.

Our plan included four basic principles:

  • To get IT up to business speed;
  • To become much more efficient and agile in our operations;
  • To delight our users every day;
  • And to turn IT into an innovation center, not a roadblock.

These four principles still encapsulate what we expect ITaaS to deliver.

We knew that traditional service delivery models imposed numerous friction points between the business and IT. We also knew we had to significantly increase our levels of automation and self-service. We knew that our consumers were looking for us to act like an internal SaaS provider, and we knew that the solution was to move to a zero-touch, customer-centric model. With that, we committed to further increasing our SaaS portfolio, and we started our 1st private cloud initiative.

In 2012, 30% of our applications were delivered via SaaS providers, and we launched our 2nd private cloud effort. “OneCloud” is our internal IaaS private cloud based on a software-defined datacenter architecture. Within a year of launch, we now have 9 different large SDLC tenants groups internally and have approximately ~40,000 virtual machines in our private cloud.

Two Insights: Automation and Change Management

I’ll write another post about building a private cloud in the near future, but I want to share what I think is different today, that allows IT orgs to finally – and successfully – make the change to this new way of doing business. Here are two quick insights:

First: The move to third party cloud services offers IT a route back to relevance and value.

That may sound strange coming from a vendor that sells virtualization solutions, but the workloads we shifted to third party providers are the easily-siloed and more mature business processes – sending HR processes to Workday, say, or ITSM to ServiceNow, or SFA out to Salesforce. They are important, but they are not the mission-critical processes that differentiate us in the marketplace.

We found that by dismantling the “soviet era” systems that were running those paper-based processes and moving them to the cloud, we freed up a significant amount of internal resources from having to focus on the things that really did not differentiate us in the marketplace.

What remained, and what we’ve been aggressively moving to a private cloud SDDC environment, are the systems that are often more complex than what we moved to SaaS provider – systems like our license management system myvmware.com, or our online training hands-on labs (hol.com), or provisioning dev and test environments for hundreds of developers who use these applications every day. But the agility and efficiency we gain by maintaining them in house, in a private cloud, directly impacts our customers and supports our revenue growth objectives.

If you look at what many IT organizations spend on the services they don’t silo off elsewhere, 60-80% of it is spent in just keeping the lights on. And when you break it down even further, a lot of that goes to what I call “human middleware” – people doing standard repeatable work: install another database, install an operating system, maintain that database, maintain that operating system. We are actively and aggressively replacing our human middleware with end-to-end automation with impressive results that are a win-win for our customers, our business, and for IT.  Many of the traditional roles that are shrinking are shifting to more meaningful roles, and we are finding our IT professionals are learning new and more relevant skills.

The Promise of Change

That leads to my second insight: The shift to ITaaS is daunting to IT employees, but it offers them a great opportunity.

It’s not hard to make the case that an IT as a Service strategy unlocks levels of agility and efficiency we’ve never seen before. But we also need to consider how it impacts the people we’re asking to make it work. Fears, uncertainties, and doubts about the change are understandable, and it’s important to recognize that both personal and cultural challenges exist.

Change in our industry is inevitable and constant.  Who is still doing the IT job they did 10 years ago? But leading a transformation to ITaaS means that you need to paint a picture of a future state for your employees that highlights roles and opportunities that are much more meaningful than they’re used to under the traditional model. Who wouldn’t want to be relieved of rote and repetitive jobs and asked instead to be part of a forward-thinking and innovative sea change that can make a positive difference? This is important to keep in mind as you look to align employee incentives with the changes that you want to make.

In Summary:

  • ITaaS isn’t a new concept, but with new technologies, its time has come.
  • Even with better funding, most IT orgs wouldn’t be able to keep up with the demand they face today using traditional process-bound methods.
  • Shifting some applications to SaaS providers frees up IT resources and costs to automate and innovate where it really counts.
  • Shifting core differentiating business processes to a private cloud significantly improves agility, and creates new opportunities for innovation that weren’t possible in a traditional data center environment.
  • Finally, own the problem. Actively lead the cultural shift required to transform the architecture and operating model that enables IT as a Service.

In part 2 of this series, I’ll share specific details about just one of the IT groups that has transformed what it does based on a shift to private cloud. In part 3, I’ll look at agility: how we measure it and how we keep continuously improving. In Part 4, I’ll explain what it took to stand up and run our own internal private cloud with ~40k VMs.

Follow @VMwareCloudOps & @PaulChapmanVM on Twitter for future updates, and join the conversation by using the #CloudOps and #SDDC hashtags on Twitter.

Industry Veterans Share Key Lessons on Delivering IT as a Service

Ian Clayton, an ITSM industry veteran, and Paul Chapman, VMware’s Vice President of Global Infrastructure & Cloud Operations, know a lot about IT service delivery. Join Ian and Paul next Tuesday, July 23rd at 9am PT, as they share real lessons learned about delivering IT as a Service.

You will get more out of this brief webcast than most of the sessions presented at expensive conferences!

The webinar will cover:

  • VMware’s own IT service delivery transformation based on cloud
  • Business justification of an ITaaS delivery model
  • Key success factors for driving technology and operational transformation

Outside-in thinking is needed to give IT a winning strategy. But inside-out leadership is required to make the changes that enable a successful execution. Don’t miss this opportunity to hear from IT experts as they share real advice in successfully delivering IT as a Service in the cloud era – register now!

We’ll also be live-tweeting during the event via @VMwareCloudOps – follow us for updates! Also join the conversation by using the #CloudOps and #SDDC hashtags.