Is Chaos the New Equilibrium?

August 3, 2009

 

“We’re waiting for things to return to normal.”  How many times in the past few months have we heard this?  But what if the situation we are in is now the new “normal?”  Many organizations are holding back, sitting on the sidelines, if you will, waiting for economic conditions to stabilize, to become more in control.  What if the control limits have greatly expanded?  Perhaps, now, we are “in control,” based on the new parameters? 

Listening to Wall Street analysts the other day on CNBC, several were referring to historical data on where they thought the market was heading, it was almost as if they were ignoring the events of the past 10 months.  A friend of mine sold some stock we both had bought because a friend of his, who is heavy into the technicals, told him he should sell.  The stock is up 15% since then.

The purpose of this is not to bash stock analysts or technicians, but to point out that using traditional methods and techniques without modifying them for the current situation may not be appropriate in today’s environment.  When a significant event, a Black Swan, like the financial meltdown in October of 2008 occurs, the rules of the game change.   To continue to apply old rules to a new situation will result in staggered growth at best.  It’s not just in the market where this is happening, it’s all around us.  Take IT organizations and Virtualization for example. 

Virtualization is a transformative technology.  Not only does it allow for an IT organization to cut hardware costs, but it allows for a dramatic change in the way IT does business.  But this does not happen on its own.  The IT organization must recognize the opportunity and change accordingly.  Too often, IT organizations deploy virtualization technology, continue to apply the old rules of server management, and then wonder why things don’t seem to be improving.  The rules of the game changed; they don’t get the full benefits because they’re still playing under the old rules.

Customers and markets, that were once thought to behave very rationally, have shown quite a bit of irrational behavior over the past year.  Whether this behavior continues remains to be seen, but one thing is fairly certain, the economic landscape has changed significantly – e.g. the Government owns two auto companies.

So, are you waiting for things to return to ‘normal?’  Or are you adapting to the new environment and positioning yourself and your organization for success?  What events have caused the rules of your game to change?  Have you adapted?

Let me know your thoughts.

Glenn Whitfield

Advertisements

What IT Can Learn From Manufacturing

May 26, 2009

 Background

A long time ago, or at least what seems like a long time ago, in the U.S., Manufacturing was King. For companies whose primary product was manufactured, manufacturing, along with finance, dominated discussions.  There was little concern for quality, cost, or customer service.  The customers would get what they got (and like it), and any additional costs incurred would simply be passed along in the price of the product.  Life was good!

Slowly, however, things started to change.  As other countries began to emerge from the post-WW II economies, they began to develop their own infrastructure, and were actively seeking techniques to improve quality and productivity.

Meanwhile, back in the U.S., it was business as usual, and many felt these pesky little countries were no match for the mighty U.S. industrial base.  Quality experts like Deming and Juran, seeing the error in this line of thinking, pleaded their ideas to senior management before it was too late.  They were cast aside.

So they went to Japan, whose leaders were hungry for ways to improve quality and increase productivity.  They were able to implement these techniques through diligent work with much success.  Eventually, they began to take a foothold in the U.S. and their products became very successful.

Savvy U.S. manufacturers looked at what was going on and began to change their thinking and their organizations.  The traditional organization’s operations, with its command and control structure, siloed departments, mass-production mentality with its associated lack of flexibility, had to change.  Some organizations made the transformation while others did not, and are no longer in business.

Because of the “sudden” insurgence of foreign competition (not really, but few were paying attention to notice), managers took drastic steps to remain competitive – like outsourcing either entire manufacturing operations, or parts of operations.  Sometimes this worked, sometimes due to supply chain and other issues, it was less than successful. 

Next, and for those whose products and structure precluded them from outsourcing, came implementation of Lean manufacturing / Toyota Production System (TPS) concepts, along with several reorganizing by product or service.  This transformation continues to this day.

IT Comparison

So, what does this have to do with IT?  Well, when you look at IT in enterprise organizations, a lot.

One of many ways to look at it is to ask, “In an enterprise, what is the purpose of IT?  What does IT really do?”  In its simplest form, IT processes data to become usable information so it can be utilized in decisions to help the business.  In this way, IT is much like a factory that processes data and turns it into information.

Of course, the way it processes data varies greatly.  Sometimes it functions simply as a conduit, as in email.  A supplier (user) types a note on an application and presses SEND.  At that point, IT takes the email and processes it to a customer (also a user) who opens the email and makes a business decision based on the information it contained (act on it, do nothing, delete, etc.).  Sometimes IT is a storage facility that stores and inventories products (files) for later use by customers.  A supplier (user) sends a product (file) to IT for storage (server).  When a customer (user) needs the file, they order it from IT (click to open), and IT delivers the product to the customer.  Other times, IT functions as a true manufacturer and creates product.  A supplier has a need to solve a business problem and there is an IT product (application) that can help.  The supplier presents the build specs and IT produces the application either by building it with its own resources (development) or by outsourcing production to a specialist (purchase software).  IT then delivers it to the customer for use, and provides customer service (help desk) as well.

Now, there are a lot of things going on behind the scenes in the IT Factory to deliver these products and services, and the way IT Factories go about delivering these vary by organization.  As was the case in manufacturing during the mass-production hey-days, where factories were aligned by departments (Stamping, Machining, Finishing, Assembly, Shipping, etc.), many IT Factories are aligned by function (Hardware, Software, Network, Storage, Server, Support, etc.).  In the traditional IT Factory, every application has its own server, storage, and support group all within and aligned by each of the functional areas.  Changes and new requests must pass through each of the functional areas before moving to the next, with the occasional concurrent processes.  Since the organization was probably already structured in a hierarchical way, it only made sense for IT to follow this structure.

But things are changing, and changing quickly.  If the rate of change in manufacturing was linear, in IT it is exponential (see figure 1).

Mfg IT Change Rate

However, in a slight difference from manufacturing, the change IT enterprises are experiencing is not necessarily driven by outside competition, but by the technology itself.

Applications have gone from being developed in-house (highly specialized ones still will need this), to being purchased off the shelf and installed on the companies servers, to being available as a service (SaaS).  Storage and Networks (along with Applications) that used to require separate physical machines have gone from 1:1 to 1:many with the implementation of virtualization technologies and the advent of the cloud.  Mini-factories (desktops) that are supported by maintenance personnel (desktop support) who had to be dispatched remotely to solve customer (user) problems or make changes can now be fixed remotely with desktop virtualization technologies.

In essence, IT as we have known it in the enterprise is slowly becoming obsolete unless it develops new approaches and skills to support the business.  It’s not a question of whether the current work that is being performed will still be needed, it’s a matter of scope and scale.  There will still be a need for networking, hardware, storage, etc. personnel, just not as many (in the enterprise).

This leaves two choices for IT leaders.  They can either support these new technologies, figuring out how to best utilize them in their organization, or resist them and continue to maintain the status quo.  The problem with resisting them is they will eventually catch you and your organization.

IT Reaction

IT needs to use these transformative technologies to fundamentally change the way it does business, much in the same way that manufacturing embraces Lean and cellular manufacturing concepts and techniques.  IT needs to transform from a provider of technology to a provider of service that utilizes technology.  It needs to become the de facto expert at applying technology to improve the business and business processes, ensuring all the while its actions are aligned with the overall corporate strategy.

Time is of the essence.  Organizations need to review the technology available and determine not only how that technology will enable them to improve operating costs, but also how it will help them improve the service they provide to the business.  The opportunity is ripe for IT to take a true leadership role in helping change and improve the business.  History has shown us where the consequences for inaction lead.

 Mfg IT Then and Now

 

Let me know your thoughts!

Glenn Whitfield


Preparing for Virtualization

March 25, 2009

 

In the last couple of weeks, I have been asked to participate in several meetings with our virtualization specialists to help a client with a few issues.  Now, I know very little about the technical aspects of virtualization, but I do know a few things about processes and organizations.  So, when they asked me my thoughts on one of the issues (application deployment), my first thought was to find out how they performed that function with a physical server.  We then mapped out their process.  Next we mapped how it should be done in a virtual environment.  And lastly, we mapped how they were actually doing it in the virtual environment.

Comparing the way they did it with a physical server to the way they were doing it with a virtual machine, we quickly discovered nothing had changed.  They were trying to do things the same way.

IT organizations constantly complain that when they put in new technology, the business users never achieve the full benefit of the technology because they refuse to change the way they do things (and IT then gets blamed for the technology underachieving expectations).  But who to blame when the ‘business’ user is IT?  It will either be the consultant who helped them put it in, or the technology itself.  Excuses like, “we tried virtualization and it just didn’t work here” or “virtualization is just not for us” start to be voiced, and, viola, the technology once again failed to meet expectations.

Why did the virtualization project fail? Because we focused on the wrong things; we focused on the technology and ignored the process and people. 

We must learn to focus on the process, engaging the people, while preparing for the technology. (see more here and here)

Virtualization is a tool.  It is a technology that, to get the full benefit, requires the IT organization to change the way they do certain things.  If you don’t change the way you do things, you won’t ever get the benefit of the tool.  Intuitively, everyone knows this.  But how many are doing something about it?

If you are heading into a virtualization project or expanding on work you’ve already started, it is imperative you review your processes for how you do things currently in the ‘physical’ world, and how you’ll do things in the future in the ‘virtual’ world.  Not doing so will limit your potential.

Let me know your thoughts!

 

Glenn Whitfield