More than one large government organisation is looking to transition themselves from a narrow inward focus to a new role of an IT service provider. Without exception these transformation projects carry high risk, and in the government world that immediately means high visibility too, creating a perfect storm of risk if not managed well.

The nuts and bolts of the technology are usually in very good hands: the servers, the database, the applications, the network, the desktop and end user devices - the tech transition itself can be tested, piloted, corrected and implemented. This is not where some of the real risk resides.

There is real danger is when you overlook service management. As someone said at the recent ITx Conference "Imagine doing an engine transplant while the aircraft is still in flight".

Having done this before, there are some simple checkpoints to consider from a service management point of view.

1. Start with the overall key guiding principle. In government departments this may be something like the Digital Transformation Strategy - this is a key input document or artefact
2. Look at the total technology landscape. This is usually contained in the overall Enterprise Architecture - key input document or artefact 
3. Identify the technology components that are going to change. It might be the infrastructure, the database, the applications, or even the network, or end user devices; this should be in the high level technology road-map - key input document or artefact
4. With a little bit of luck, a programme has been set up and it has broken this down into individual projects, each dealing with one aspect of the technical change - key input document or artefact
5. A key part of this is drawing up a matrix outlining when each technology component will be changed for which customer or business - input for project planning
6. From a business perspective, you may be moving to the cloud, changing suppliers, outsourcing, multi-sourcing, in-sourcing and/or positioning yourself as a supplier of IT services to others in the sector. It doesn't matter which, all of these have Service Management implications that need to be considered, and form the high level requirements - input for service design 
7. While it's common for every project to have granular technical work-streams, the following should be also be added as over-arching work-streams: 
   1. commercial, legal and procurement
   2. certification, accreditation, risk and security
   3. reporting
   4. service management tools
   5. communications and cultural change
   6. partners
   7. customers 

8. From a Service Management perspective, translate the overall digital transformation strategy into a high level Service Management strategy. Doing so is going to help inform the high level service model - your key output

9. Using any number of frameworks and best practices, and my preference is to use TOGAF (The Open Group Architecture Framework), look at the "as is" and in collaboration with your internal and external stakeholders define the "to be" Service Management model - another key output

10. To inform the Service Management Project Plan, use the high level technology road map and the program or project plan. This will ensure that service management related cut-overs are locked and synchronised with the technology and/or partner and/or business changes - this output completes the puzzle

11. The steps above are very much in line with GEA-NZ which I would use as a guide. GEA-NZ also recommends "sprints" and perhaps you could use it to design and implement each ITIL process.  

12. With respect to transitioning, my preferred approach is to gradually wind down support for the old service on the old model and old partner(s) over a period of time and all new services supported by the new model and new partner(s); piloting or running in parallel where one can - as opposed to a big bang cutover.

Transitioning to becoming a service provider is a big step with some scary risks, and usually people have it in hand but the golden rule is to remember your end user. They're the ones who are going to feel the smoothness or roughness of this transition, so make sure your service management is damn near perfect.

Note: published 29th Aug 2016 by the Institute of IT Professionals in their IITP Techblog and on LinkedIn 31st Aug 2016

There are more than a few nuances as organisations undertake the journey to transformation, digital or otherwise. Service Management is a key component to success.
 

Sunit Prakash has had many successes in organisational transformation on a global and local scale.

More importantly he bears the battle scars from the many lessons learnt. Don’t be one of the walking wounded - or worse.

Call him and head off some of the challenges before you even get to the pass.

#ServiceManagement #ITIL #ITSM #Transformation #Transition