So, you’ve identified the need for a new ITSM system.  You might be starting from scratch (although that’s never really the case).  You might be upgrading between versions or procuring a system from a new vendor or implementing new tech.  But where do you start?

Sometimes it depends upon just why you need to change your system , but our experience tells us that one essential to being adequately prepared is understanding your ‘As-Is’ processes.  How you do business now, how your service desk operates and how the business operates and interacts with that service desk or service provider.

Why do we feel that this is an essential action?  Your ‘As-Is’ as will necessarily form the basis  of the ‘To Be’ processes.

Businesses need to ensure they are able to understand where they want their Service Management business to be when the new solution is implemented and how to implement with minimal disruption to the business.

Related Posts


Is ITSM really ready ‘Out of the Box’?

As ITSM has evolved in recent years, there has been an appetite and ability to move towards ‘Out of the Box’ implementations where not a stitch of code is changed in the ITSM solution during Read more…


Don’t Disrespect the Data

There are many moving parts that ITSM Implementation teams need to consider in the scope of a project. Commonly the main focus is on code and configuration and second to this is data. This is Read more…


When to call it quits or start again

Whilst working on some of our marketing collateral, I came across a project where I was requested to work as an independent project management consultant, evaluate a project and recommend how the project and their Read more…