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


Remedy Testing – Can Any Tester Do It? We think not.

Through the years of working with Remedy, it has often been stated that Remedy ‘isn’t Rocket Science’ and any tester can test it. I’ll be honest with you and say that this has irritated me Read more…


Project Management and Budgets

This post is slightly different to some of our others.  This time we’d like to know a little about your experiences and contrast them to our own.  Our expertise spans sectors, but is always in Read more…


Project bottlenecks at testing

We’ve touched upon this in an earlier post on Project Lifecycles and Engagement.  As we’ve all experienced, but organisations seldom learn from projects.  Spending ramps up towards the end of a project as delays and Read more…