Tech IT Easy

May 8, 2007

How should an IT department be organized ?

         “Message from Jeremy: To all Tech IT Easy readers, who could obviously not necessarily remember the initial announcement, I have invited my friend Steve to help me try to provide you, dear readership, with everyday better technology insights. Steve’s mission statement is that there’s no mission statement: what matters most here is to raise the right issues on underlying market trends, bringing to light new software, Internet services and consumer electronic devices. Steve, the floor is yours…”

     Along as my working paper (The various business models for websites based on connecting users), for which I would still welcome any kind of help (just mail to steve.danino@mailhec.net), I am also conducting a project for a large industrial company to reorganize its (large) IT department. The problems should sound familiar: costs are through the roof, quality of service is desperately poor, and many valuable projects proposed by other divisions of this group are just scrapped off because the IT Manager just doesn’t have any budget left…

 I felt it could be interesting to provide Tech IT Easy’s readers with some of our current findings. We’d be glad to know, by the way, whether the organization for which you work or have worked for has experienced already the same problems and implemented the same type of solutions.

 Here we go then :

- First of all, it appeared that the IT department was a discretionary cost center, ie the headquarter would simply pay for all its expenses. Costs were not allocated, and certainly not allocated by customers (the other firms divisions), which considered this internal service as “free”. Instead of having a P&L for the IT department, or even a line estimating IT expenses within the P&L of the divisions, all the costs would be grossly included in the overhead costs. Problems: 1) It’s difficult to identify and punish the black sheeps who are responsible for overconsumption 2) Free ? this of course is an illusion. Nothing is free. At the end of the year, the overall budget for IT will be systematically reconducted – if not capped by the HQ.

- And here comes the problem of misallocation. Since the IT department is under pressure by the HQ to reduce its costs, it might refuse to engage in some of the projects the other divisions would ask for. But then, one might say that this department did indeed accept to work earlier for least valuable projects … first come, first-served ! This is not a serious way to deal with a 1 billion dollar large IT budget. And what about trade-offs when it comes to suppressing maintenace fees, which are piling up little by little, until they become unmanageable ? Just bear in mind that an organization like the one we consider uses hundreds of systems and thousands of different applications….

 So, there are some very serious issues here. It has been estimated that this company could save up to 30% ot its IT costs – a mere 300 million dollars per year ! And here’s how:

1) The first possibility would be outsourcing the IT department to an external provider, such as IBM Global Services, Cap Gemini, Accenture, EDS, etc… Empirical data shows that very significant savings can be performed this way – up to 40%.

Problem: this very company already tried this a couple of years ago. And the quality of service was an absolute disaster. Besides, contract management was tough and supplementary expenses were billed on and on by the provider, (the name of which I will not disclose – or only by email). The result: within less than 3 years, the services were internalized once again.

2)  Another possibility would be transforming the IT department in a profit center, very much like Siemens did with its new subsidiary Siemens Business Services. The big picture: you tell your IT guys that instead of being “civil servants” of their company, they should endorse the market principles, and try actually to make profit…which is far from obvious since all the other divisions are now allowed to purchase their IT services on the external market.

Problem: the IT department is absolutely non-competitive. So let’s forget about this one.

3) Last possibility: keep the current structure, but make the IT department bill its services to each division (ie allocating the costs) and make sure that a market reference is taken into account when negotiating transfer prices. If the head of any division complains to the HQ that the IT service is billing twice as much as an external provider would, then a “positive” pressure would be built upon this division. Problem: this solution sounds slightly awkward, since very few companies, to my knowledge, have chosen this organization.

So, have you ever heard of similar cases ? What would be the best choice according to you ?

7 Comments »

  1. Thanks for sharing your findings with us Steve. Your post seems long at first sight, but it’s well organized and very clear – on top of being extremely interesting.

    Depending on the culture of the company, I would go for 2) or 3) + having a cross-department investment committee to select the most value-creating IT Projects + bringing in functional managers (from operational departments) on top of developers to make sure IT projects fit the actual needs of their stakeholders.

    This of course, if a quick answer, and I’m sure there are ways to spend a year in the company to precisely define the one best way to proceed.

    Comment by Jeremy Fain — May 8, 2007 @ 13:38

  2. Four letters, ITIL.

    I don’t see this as a problem of organization but as a problem of accounting. There’s no need to any organizational change, but the internal IT service unit needs to have internal costs for all services it offers. There are many benefits to this, even though it means that there needs to be controllers in the IT unit.

    I seriously advise to take a look at ITIL. It’s a library on information how to successfully run an IT service unit today.

    Comment by kari — May 8, 2007 @ 19:17

  3. Good idea Kari, very complementary with my comment.

    Steve, Kari is too modest to remind you about it, but he had written an excellent post about ITIL you may find some inspiration in: http://jeremyfain.wordpress.com/2007/02/14/creating-itil-compliant-service-catalogue/

    Comment by Jeremy Fain — May 8, 2007 @ 19:32

  4. Thanks Jeremy, but that post was mostly about Service Catalogue, which is part of Service Support part of ITIL. What Steve is interested is probably the “Financial Management for IT Services” part of ITIL Service Delivery. It’s goal is “to provide cost effective stewardship of the IT assets and the financial resources used in providing IT services”. There’s a chapter or two on how IT services should be priced and charged.

    Comment by kari — May 9, 2007 @ 07:49

  5. Well guys, it is not only a matter of accounting.

    Allowing your divisions to purchase IT services externally is really a strategic choice; besides, keeping your IT departments as a discretionary cost center might also imply that productivity could be much improved.

    Comment by Steve — May 9, 2007 @ 17:17

  6. I’d say that BUs buying their own IT services is rather insane, at least support-wise. OK, it’s an idea and might work in operational, every-day IT, but I’d foresee a lot of challenges with IT infrastructure and such.
    If you want centrally organized IT, ITIL is the way to go.

    I’d say option 3 is what any sane organization does. The only three ways I’ve heard this done are
    1. IT costs are aggregated to corporate center – which I believe is the situation now?
    2. IT costs are shared by BUs by some predefined way.
    3. All IT services are priced and BUs are charged.

    Option 2 makes rarely sense, especially if the BUs are diverse as their needs are probably different too and some BUs might feel they pay too much. I think many organizations begin from option 1 and probably already have or are planning to go to option 3.

    The reasons and benefits and challenges and what not are best explained in ITIL. I strongly advise taking a look at it, as it combines time-tested best practices of many IT organizations.

    Comment by kari — May 11, 2007 @ 08:58

  7. Thanks Kari.

    You’d be glad to know that our client will more or less reach the same conclusions as the ones you have just sketched out.

    Option 3. is definitely the best way to go, at least on paper. But there are some drawbacks indeed: time consumption primarily…and, more anecdotically, preventing the IT department to practice creative accounting and charging could lead to a few serious issues (splitting projects into service units, political pressure built upon IT department, etc…)

    Comment by Steve — May 11, 2007 @ 12:14


RSS feed for comments on this post. TrackBack URI

Leave a comment

Blog at WordPress.com.