Home > ITIL the Elephant in the room > Forbes: Cloud is Out of the Box And IT Needs To Face Up To It

Forbes: Cloud is Out of the Box And IT Needs To Face Up To It

We’ve just added further debate over at ITSkeptic which will of course cause further steam to be expelled (http://www.itskeptic.org/organisations-have-failed-their-it-bad-parents#comment-9213)

But this article over at Forbes rather brings home to roost our point of view:

http://www.forbes.com/sites/joemckendrick/2012/03/22/cios-love-hate-relationship-with-the-cloud-revealed/

With specific reference to this paragraph in the article:

“Part of that new mission means figuring out what it means to be an IT department at a time of DIY technology, when everyone and anyone can purchase and use their own devices or online services.”

We have made this comment over at the ITSkeptic:

There is no point moaning or taking a shot at the business for making use of readily available technology. Afterall, we in IT within the firewall are simply a provider of service which sustains our business, just like outsourcers and providers of cloud facilities.

The fact that Cloud is unmanaged or outsourcers charge for every change or that we appear to lack cost efficiency to our customers in the business is our problem.

We in IT Service Management and IT Operations need to grow up. We should be offering fit for purpose solutions to our customers, then we would not risk being outsourced or, compete with the Cloud.

If the business needs a new service rapidly, and are prepared to do without end-to-end management security, then we should be capable of offering that to them instead of them going to the Cloud.

We should not bemoan the fact that our customer is always asking for more, we should recognise that this is the nature of business today. Remain competitive or die. Die means eithe the company fails or the company goes around us. Either way we lose our jobs.

It is we in IT who need to grow up.

Our business should not be expected go govern IT. If we employ someone to do a job, we do not then expect to have to micro-manage them over their shoulders to make sure they are doing their job properly. We have employed them because they are capable of doing that job.

We do however have a responsibility to inform the employee that we have changed our strategy for which they “may” need to change what they do.

Conversely, the employee we have hired has a responsibility to make sure that they are in tune with what we’re doing.

Simple example: We employ a gardener to mow the lawn and tend my existing flower garden. We then decide that we want to transform a section of the lawn into a vegetable patch.

We would approach our gardener and present our plan. We would expect our gardener to tell us that they could do the work and let us know if there is any additional cost (investment) and resources required (from additional FTE hours to seeds). If they were incapable of performing the work themselves (lack of expertise) we would also expect them to tell us that they needed to hire specialist FTEs to delivery the work to plan.

We see IT as no different to the above. You say “Failure to govern IT. It is like a wayward unsupervised teenager.”

IT is not run by junior people. IT needs to take responsibility as a service provider and effectively maintain its provisions to the business requirements, especially when they require rapid change.

You say: Failure to take responsibility for activities that aren’t IT’s job.

We say, we do not know about Gardening. We employ the gardener to know about gardening. If we want certain quantities of vegetables, we are not equipped to write the design, change, release and project plan for how to garden to that requirement.

We give the gardener our requirement and the gardener should design his plan. Clearly if we do not tell the gardener that we need the Potatoes in the Northern Hemisphere in January, then producing potatoes under Glass with Heaters will not be in his plan. So that is our bad. However collaborative discussion with an expert in their field (a gardener would know that some people like veg throughout the year) should elicit that information.

One doesn’t simply dump a requirement over the fence and then expect it to be delivered. We’re all mature folk, surely we should receive a requirement and then brainstorm that we have understood the requirements correctly (Oh, you want it by Friday and you have colorblind users, need double-byte , and need multiple timezone support!).

Get a grip. We bring you back to our original point: IT is/are not children. IT is a professional service provider. IT should act like a professional service provider.

When you talk about a “Failure to Respect IT”, listen to yourself a moment…do you respect anyone who doesn’t listen to you or argues against you and your requirements when you are the person with the money?

Think of a car salesman – you are going to buy a car and you want the car tomorrow. You agree a spec with the salesman but the salesman then tells you that you can’t have the new car today because the car takes 3 months to deliver. Now, you want the car tomorrow because your old car has died, but the salesman has not asked you why you want the car tomorrow. Whether he asked you why you want the car tomorrow or not, if you say you want the car tomorrow, he should be saying “3 months to order to your specific spec or I can give you this similar car off the Lot today. It doesn’t have the spec you want or the warranty or whatever…but you can have it today, your choice”

And that is the point with delivering IT services. The customer asks for a service. They will have a reason for needing that service. It is our role to do what we can to facilitate that service, not be a problem.

We lose the respect of our business quite rightly when we do not react to their requests or, worse, put up roadblocks as to why we cannot do what they want, when they can walk into any consumer store and get for their own personal use exactly what we tell them we cannot deliver.

You say “Non-IT people can never expect to understand the complexities of enterprise IT”. YES!!! That’s why they employ us. To know how to garden for them so they don’t have to. We are “the Fixers”.

To our original perspective on IT and ITIL, ITIL assumes that people do not know what they are doing. People, we in IT should know what we are doing.

When one is employed, one is employed because (a) one is allegedly capable of executing the role we have been employed for and (b) one will be a responsible corporate citizen, acting on the best interests of and additive to the business.

We are not employed as controlled drones, we are employed as human expertise. ITIL creates and demands drones. Drones cannot react to change, they need controllers who program them for the change.

Layers of mediocre management in IT hiding behind their ITIL maturity is the problem, and has led to the lack of value from our management tools and the outsourcing of our resources and the move of the business to adopt the relative freedom of cloud to support the continued innovation of the business.

The Business is not the problem, We in IT are the problem. We are our worst enemy, not because we are teenagers but because we act like teenagers.

We hope this engages debate with you. Tell us how ITIL and Governance and the over Procification of IT helps businesses? Tell us how it encourages entrepreneurialism and creativity in IT people to go that extra mile for the business that feeds them and their families?

Tell us how ITIL is part of the solution and not part of the problem.

ITILosaurus

Advertisements
  1. No comments yet.
  1. No trackbacks yet.

Feel motivated to reply?

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

WordPress.com Logo

You are commenting using your WordPress.com 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 )

Google+ photo

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

Connecting to %s

%d bloggers like this: