Information Technology Service Management

 Information Technology Service Management

 

Over the last few years I have facilitated several Information Technology Service Management (ITSM) work sessions within the oil and gas and utility industries. The challenge was to build consensus through identifying what is important, making recommendations and decisions and establish direction that would enable the IT organization to technologyunfolded.com  improve processes and services offered to their customers. The following article briefly outlines a number of lessons learned that came from our experiences.

An ITSM Work Session should provide the foundation for your organization to create the blueprint to propel IT services and business value forward. In establishing an ITSM initiative the following key groups must be involved:

Strategic: CIO and Directors to establish strategic intent, vision and enterprise objectives

Tactical: Directors and Managers to establish improvement objectives, priorities and program charter

Operational: Managers and Key Stake-holders to establish solution, roadmap, business case and project charters.

Fundamental to any ITSM session when engaging these groups is to develop a clear problem definition, defined and approved by the executives or senior steering committee. This is an area which IT often falls short. The lack of a clear problem definition negatively impacts the tactical and operational levels of the organization and limits the ability to move forward.

When working with your teams, build an understanding of all the work that is taking place in the IT department right now and how it fits within the ITSM support and delivery relationship models. Discussion, training and clarity will be required to ensure your people understand the ITSM relationship and delivery model. By engaging people in a defined work exercise, your teams can map out and see how their work aligns with your ITSM program requirements. This is effective in establishing leadership and team buy-in.

Establish a clear understanding of your points of pain (PoPs) and the IT maturity. PoPs can be established through focused brainstorming sessions. Once collected, your PoPs should be looked at from an organizational and process maturity perspective. This is often missed as IT has a habit of looking only at processes and tools to solve problems. Align your PoPs with the industry maturity model standards (non-existence, chaos, reactive, proactive, service, value). It is important that the content be translated into a service management maturity grid and aligned with the Information Technology Infrastructure Library (ITIL) process categories. Work to obtain various IT teams, customers and business representatives’ perspective on the ITSM organizational and process maturity levels. This builds some reality into the PoPs and maturity levels thinking by dislodging IT from a position of working in isolation.

Build a business case and program plan that can be activated by your people. At this point you

 

 

Leave a Comment