IT Production Phase Drill Down

In previous posts, I covered the 3 main stages of virtualization adoption and the key elements driving the virtualization journey. Just a reminder that most of the material in these posts comes directly from our customers through a primary research project that we carried out last summer.

Let’s now double-click on the IT Production phase.

In this phase the IT department is the main driver for virtualization in a bottom up type of approach. They virtualize the assets that they own such as file and print servers, domain controllers, web servers, Citrix servers, and so on. Test and Dev servers are also a primary candidate for virtualization at this stage.

Key Drivers

Here is the typical status of the key virtualization drivers in IT production:


The confidence is reactive, meaning that the team has enough knowledge and experience to react to certain triggers (see blow for the list of typical triggers) but virtualization is not the predominant computing platform yet. The team knows how to install and operate ESX/ESXi but they are typically not familiar with more advanced features like SRM, DRS, HA and FT. There is a big inflection point in term of confidence when the team learns how to use vMotion as it allows them to perform system maintenance without downtime. It is not unusual to see customers organize internal demos around vMotion to show its power to other divisions and/or to the business.


The sponsorship at this stage is typically at the IT manager or IT director level, especially in bigger companies. In smaller companies the CIO has more visibility into most projects going on in his or her org. In many cases, we cannot even talk about sponsorship as much as ownership as IT tends to virtualize what they own first.  There are cases where the sponsorship is at the senior level but in many cases the virtualization first policy is not enforced aggressively yet.


The predominant value that drives virtualization in this stage is cost saving from servers consolidation. These saves are so significant that they overshadow some of the additional benefits the come from virtualization such as faster provisioning, better manageability, less downtime etc. More on business value further down in this post.


Our customers told us that at the beginning of their journeys, these where the three biggest obstacles  in the way of virtualization projects:

Team Communication

Or lack of thereof. Virtualization technology cuts across multiple teams and disciplines: servers, storage, network, and security. Virtualization is typically introduced into IT by the server team without necessarily involving the other teams that will be impacted by the transformation.

In many customers this has been the main obstacle to more efficient adoption and in turn value realization.

It is very important to:

  • Train all teams involved on virtualization technology
  • Keep communicating across teams as the transformation takes place over time.

We found customers who even re-organized their IT around virtualization to facilitate adoption and optimize their processes.

Virtualization FUD

This is somewhat related to the previous point. As much as virtualization has become mainstream in thousands of IT shops and it is running mission critical applications in some of the largest data centers the world over, there are still IT professionals that don’t fully understand how it works and what are its advantages. This is natural with any technology transformation but this FUD does get in the way of wider adoption of virtualization.

We learned some very interesting tactics that customers use to overcome this obstacle. Some examples:

vMotion Demo
This is a big hit amongst our customers. They use vMotion to show in a very effective way some of the things that virtualization can do for the business such as  disruption-less maintenance, lower risk from hardware failure, and so on. Later in the journey, the vMotion demo is replaced by demos of even more sophisticated features such as High Availability and Fault Tolerance.

Show and Tell
Virtualization champions within our customers often take the show on the road and they go around the company educating people about the technical and business advantages of virtualization. Sometimes they use a successful internal project that they did, some other times they just hold a virtualization workshop using material from our web site or other blogs.

Virtualize Under the Radar
At the beginning of the journey a lot of virtualization happens below the radar as IT virtualizes the assets that they own directly. Later in the journey FUD from application owners and the business side becomes more of a factor and slows down adoption. This is where we found that some of our most confident customers just go ahead and virtualize applications without really telling their business counterparts. I know, this is controversial but true. The attitude of  these customers is along these lines: “I don’t let the business tell me how to run my infrastructure. If I decide that virtualization is the right computing platform for a given application, I just do it”. If you think about it, the business does not really care what brand hard drive IT uses right? Overtime the same will be true for whether an application or a database runs physical or virtual. It is indeed true for some customers today where virtualization is the default computing platform. It is a factor of their confidence, credibility and experience.

Storage Architecture

Storage architecture is the third major obstacle we found in IT production. Many of our customers told us that if they could do it all over again they would spend more time figuring out the right storage architecture from the get-go that

  • works well with virtualization (and vMotion and all the advanced virtualization features)
  • supports future growth

I am not the right person to go deep on this issue. I will look for an expert at VMware and interview him or her about storage best practices in one of the future posts.

Triggers and Capabilities

As covered in this post, we developed a framework to model the relationship between business triggers, VMware product deployed, resulting capabilities and business value realized.

In the IT Production stage, these are the typical business triggers that ignite a virtualization project:

  • Major hardware refresh
  • Data center migration/ consolidation
  • Merger / acquisition
  • Standardization/Organizational Change
  • Outages (application, system)
  • Increased capability/ confidence
  • Cost cutting initiatives
  • Capacity constraints (power, cooling, CPU, space)

Customers respond to these triggers by deploying the basic virtualization platform around ESXi with related management tools (vCenter).

The capability that are achieved by deploying these products include:

  • Massive consolidation
  • Space, cooling, hardware, energy savings
  • Have a lot more floor space
  • Faster Provisioning
  • Do more with Less
  • Excess capacity for future growth

Faster provisioning in particular is a capability that fosters more adoption of virtualization and positively impacts the IT team credibility. It is not unusual for customers to cut down their provisioning cycle form weeks to days, sometimes hours.

These capabilities map pretty directly into the following business value categories

  • Capital Avoidance Saves
  • IT Operations Efficiency
  • Green Saves

Where the predominant value is Capital saves from consolidations as mentioned above.

Development-Related Triggers

There is also another set of triggers that prompts customer to deploy VMware’s development life-cycle management area such as Lab Manager. These triggers include:

  • Major application upgrade/Changes
  • Need to improve application life-cycle efficiency/ quality
  • Major OS refresh

From deploying this area of the VMware product line customers typically get these set of capabilities in return:

  • Reduce the cost of application development life-cycle
  • Faster set up of development seats
  • Reproduce bug/incident events for resolution
  • Replay events to identify incident root cause

This is probably the first area in most customers journeys where the value proposition from virtualization is not predominantly around cost saving from consolidation. There will be many more examples in the following stages (Business production and ITaaS, see this post of an overview).

In fact, when deploying products such as vCenter Lab Manager, customers typically realize lower cost for their testing infrastructure, increased application development efficiency and faster time to market for new applications.

What’s Next

In the next post, I will cover some of the IT Production best practices that we learned from our customers.


5 thoughts on “IT Production Phase Drill Down

  1. Pingback: Removing IT from the Boardroom Agenda « Virtualization journey

  2. Pingback: IT Production – Some Best Practices « Virtualization journey

  3. Pingback: IT Production – More Best Practices « Virtualization journey

  4. Pingback: Resistance is Futile – Your App will Be Virtualized « Virtualization journey

  5. Pingback: Business Production Drill Down – Part 2 – Key Elements « Virtualization Journey

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s