Saturday, September 3, 2011

Framework Sceptics

Once in a very great while one comes across a project or company so embroiled in paperwork that you come to suspect their managers of a fetish for red tape. However, most projects want to succeed and most companies want to make money, so it does not occur too often, and when it does the consequences for success and profit are easy to predict.

Amongst IT Service Management consultants its a bit of a sport to speak disparagingly of commonly used process frameworks like ITIL and BiSL, and project consultants in general like to make light a of full-blown PRINCE2 approach to projects. It would be very amusing for a physicist to essay the shortcomings of relativity, a composer to mock music theory or an accountant to say that the GAAP standard takes itself too seriously, but they don't tend to do that. These people realize that you don't have to involve Einstein's entire work every time you conduct an experiment with time and space, not all notes need be in a composition, and not all rules apply to all ledgers at all times. They go quietly about the business of being good at whatever they're good at.

Not the IT consultant. You're not a man to be reckoned with until you've stated that this or that framework is far too complex, never mind that you've never worked for an organization large or complex enough to utilize it. Project leaders are even worse. Depending on whom you ask, well over half or, according to some, more that three quarters of projects end in failure. Failure. Not on time, not within budget, and certainly not delivering the desired result. In my (albeit limited) experience, most projects suffer from a lack of preparation and an excess of unstructured work. I've yet to encounter the truly pointless progress report, the completely useless review meeting or the irrelevant risk register. Neither have I seen an IT department run so well that it cannot benefit from a little process optimization and a smidgeon more compliance to standards.

The criticism that a framework is too complex is irrelevant as long as it is not the stated purpose of that framework to be implemented down to the last detail. Scalability is at the heart of all frameworks I mentioned. The criticism that compliance comes at the price of agility and efficiency is a non-sequitur. It's true, but compliance is still worth the warranty it gives.

BP can tell you, they were not broken by over-compliance to a set of rules and regulations. One or two executives might even admit that a few more inspections and reviews would not have gone amiss. Similarly, I doubt a CIO was ever berated by his CFO for wasting money on process compliance. Rather a lot of them have had complaints about budget overruns on their projects, poor knowledge and asset management and opaque departments, I daresay. A little bit of common wisdom, also known as a best-practice based framework would not hurt to make sure the same comments don't come up during the next review.

Rather than proving the mastery of your trade by critiquing the work of others (which is used to great effect by many on a daily basis), contribute to the improvement of your tools and help to make the frameworks as slim and efficient as they can be. It's not like ITSM is an academic discipline (as opposed to, say, aerospace engineering).

Tuesday, August 30, 2011

ITSM-fu, beware the acquisitions!

IT service management is all about ensuring the warranty and utility of IT assets and services. Simply put, the IT has to support the company's main process well. Incident management, change management and so on are fairly standardized processes that help companies manage their IT environment.
Some changes to the environment are wholly out of scope of these regular, 'busines-as-usual' processes, because they do not originate from within the processes themselves. IT Service Management is a bit introspective.

A favorite activity of growing companies is acquisition: gobbling up big competitors, promising start-ups and maybe something more outré for diversification. These companies are bought for their valuable people and assets, and nowadays a lot of the value of a company is its data. IP, content, patents, customer data, research databases, what have you.

A lot of this virtual gold is in formats and systems which are different from, sometimes fundamentally incompatible with, the buyers own data and systems.

The positive impact of new purchases is therefore determined in part by the ability to absorb new data, and bring it in line with ones own databases, systems and procedures for access.

IT Service Management frameworks need to expand their focus beyond running business-as-usual IT services. Robust procedures and best practices for integrating new IT systems and large, diverse data sets need to be developed as part and parcel of IT service management in general. Running a series of technical projects every time an acquisition is made is less effective for bypassing the regular IT service management organization, because that is where, ultimately, all new systems and data end up being managed anyway.

Currently, a lot of knowledge resides within large companies. Some of them have very strict policies for this sort of thing, and have absorbed a new buy in six months. Others take forever as ponderous projects with lots of external expertise are sent up to digest acquired data. The technical know-how can always be found, however, all the management and governance level experience is currently not distilled into frameworks and best practices, and companies are poorer for it.

As long as an integration process is not properly managed from the perspective of the regular IT-organization, it will have a large and detrimental impact on regular ITSM processes because they are calibrated towards preserving the business-as-usual IT organization, not towards merging IT organizations while preserving the current warranty and utility of IT services. This is a hard thing to do.

The next iteration of frameworks like ITIL need to address the needs of large companies when it comes to adopting acquisitions to maintain their status as comprehensive IT Service Management frameworks.

The current set of processes needs to be expanded. Currently, change management and release management are originators of change in the environment, presuming that IT service management instigates change, rather than reacts to it. New processes have to be defined and integrated with the rest, which deal with imposed change and seek to absorb and integrate new data and systems. The knowledge is definitely out there, and it is up to platforms like the IT Service Management Forum to distill it into the current frameworks. I mentioned ITIL a lot, but certainly BiSL and ASL are up for the same improvement.

The bottom line is that the biggest changes in an IT environment often come from the outside, and the success of the company can hinge on how well these changes are dealt with. IT service management frameworks need to adjust from introspection to adaptivity: ITSM-fu.

Steve's Job

When I started studying computer science it was my avowed purpose to one day have Steve's Job: to be Chief Executive Officer of my very own technology company. Now Steve is no longer CEO of Apple and it feels very strange. I feel a bit like Bill Turner would feel if one day Jack Sparrow gave up on being captain of the Black Pearl. The goal is still there, but it's daunting to see that a brilliant and driven man has worked himself into what seems to be an early grave. I hope for his recovery, and I hope he will be chairman of the board for a long time to come. Meanwhile I'll soldier on, collecting experience that I hope to put to good use some day. Who knows? Steve certainly put a ding in our (digital) universe.