Cómo equilibrar las demandas de confiabilidad y agilidad en el departamento de IT

I was reading a book the other night that had a couple of pages devoted to change. After reflecting on the information, I started thinking more about the dual demands that are placed on IT by organizations.

Índice de Contenido
  1. The Demand for IT as a Reliable Utility
  2. The Need for Agile and Innovative IT
  3. Handling the Competing Demands
    1. Outsourcing
    2. Creating Different IT Organizations
    3. Decentralizing
  4. The Quest for Balance

The Demand for IT as a Reliable Utility

The first demand is to be a utility. By this I mean that the organization wants their IT to be as reliable as the electricity that flows into the building – No down time, always on, and as easy to use as plugging a power cord into a wall. Needless to say, this is no small feat and takes quite a bit of work to guarantee 24/7/365 with no mistakes.

The Need for Agile and Innovative IT

Then we have all the experts saying that in order for IT to be successful, it must be agile, able to change at a moment's notice, not only understanding business needs but also able to anticipate them and oh, by the way, help them work through the change that will need to take place in order to be successful.

Anyone hearing that Sesame Street song right about now about things not belonging together? Because if you look at the qualities that make one successful at being a utility, they don’t necessarily mesh 100% with being an agile, lean, mean, change machine. Yet many of us try to do both every day, with varying degrees of success.

Handling the Competing Demands

These demands become increasingly harder as budgets shrink and IT staffing gets smaller all the time. If you talk to many CIOs, they feel that they are lucky to keep the lights on and they and their employees are going above and beyond just trying to keep services from eroding, let alone floating like a butterfly and stinging like a bee.

So how does one handle these "competing" demands? Here are a few different approaches organizations have taken:

10 razones por las que el departamento de IT no te soporta

Outsourcing

The idea behind outsourcing is that if you can't do it well yourself, let someone else do it. To be honest with you, I think the jury is still out on outsourcing. For every success story I hear, I hear two horror stories. I think the model of outsourcing smaller pieces or select functions will end up being the ideal way to go rather than the let's throw out the baby with the bathwater approach.

Creating Different IT Organizations

Creating different IT organizations within a single organization can be another approach. I'm not talking about decentralizing IT here, although that is another approach, but creating one IT organization whose sole purpose in life is to operate the "utility," while the other focuses on innovation and bringing new products and projects online. To some degree, this can make sense. There are IT professionals who are well suited to and prefer the routine of keeping things running reliably, and those who thrive on change and new development. Splitting these roles apart can prove successful, provided both departments get the resources they need. In many organizations, being able to focus on just one or the other and not both is a dream that will never become a reality.

Decentralizing

Decentralizing IT operations can also be an option. Creating separate departmental IT operations that are closer to the customer can prove beneficial or detrimental and a duplication of effort depending on the culture of the organization.

In ideal circumstances, I think the best approach might be a combination of all the above. Outsourcing select functions, combined with two IT groups - one dedicated to service and the other focused on new development, with departmental IT acting as liaisons to both units.

As much as people might proclaim, there is no one right answer to the competing demands placed on IT and what works in one place may not work in another. Perhaps most important in this whole discussion is that IT management needs to make organization management realize that there is this conundrum of competing demands and that it is often an either-or situation if the budget cannot support both. I know that in many organizations, the "utility" portion of the business does not get any attention from customers and management if it is running correctly.

The Quest for Balance

Ultimately, it is up to IT to try and strike a balance between the two. How they do that is often how they are judged. Lean too far one way and you're deemed inflexible and customer unfriendly. Lean too far in the other direction and you're accused of being responsive but unreliable. Finding the right balance is key, even though it may mean not pleasing everyone. After all, you can't make everyone happy and everyone that carries an iPod or a BlackBerry seems to know how to do your job better than you do. But remember this: people get fired for leaning too far in either direction – but failing as the utility will hasten your exit far sooner than being unresponsive. In either case, we are often caught between a rock and a hard place.

La importancia de la formación del usuario final en el uso de la tecnología

En Newsmatic nos especializamos en tecnología de vanguardia, contamos con los artículos mas novedosos sobre CXO, allí encontraras muchos artículos similares a Cómo equilibrar las demandas de confiabilidad y agilidad en el departamento de IT , tenemos lo ultimo en tecnología 2023.

Artículos Relacionados

Subir

Utilizamos cookies para mejorar su experiencia de navegación, mostrarle anuncios o contenidos personalizados y analizar nuestro tráfico. Al hacer clic en “Aceptar todo” usted da su consentimiento a nuestro uso de las cookies.