ITSM Tool Implementation – BAN THE CAKES!

ITSM Tool Implementations – BAN THE CAKES!

I’ve just seen yet another cake-based, ITSM tool implementation celebratory social media post in my timeline. You know the sort – a big “hooray,” pats on backs all around, and the photo of an IT service management (ITSM) tool “go-live cake.”

Don’t get me wrong. This is certainly a cause for celebration, and I do like cake, but I think that it’s important to understand exactly what you are celebrating.

Here’s my cautionary tale.

ITSM Tool Implementation

After the ITSM tool implementation afterparty

Now I might be ready to join GrOMIT (the GRumpy Old Men in IT). But far too often I’ve seen service desk or ITSM tool implementation, improvement, or transformation projects go-live for then, almost immediately, a bunch of “stuff” to happen:

  • The implementation/project team is disbanded
  • All financial backing is dropped or concluded
  • Ownership is “thrown over the fence” to IT operations

Now not all of these are bad things per se, and things can still work out well. However, more often than not (in my experience), the IT operations team weren’t sufficiently involved in the project and “build.” So, ownership of the new technology, and potentially ways of working, can be a little forced rather than embraced.

Then if post ITSM tool implementation changes are required, as you probably won’t get everything right first time, the builders have moved on elsewhere. Which means that either the operations team are left to make modifications with little experience, cue a cake that’s like the Leaning Tower of Pisa, or they need to call in help. Oh hang on, they can’t do that because the project budget is all spent.

Unfortunately, I’ve seen service desk and ITSM tool projects go from award-winning to a total mess within the space of a couple of years for exactly these reasons.

Planning, delivering, and then celebrating “half a job”

What concerns me more these days is that core service desk functionality is now just a starting point, and I’m not so sure that everyone takes this into account when planning their implementation, improvement, and transformation projects.

The service desk itself can be expanded beyond the initial implementation, think service catalog, IT asset management (ITAM), security, capacity planning, and a wealth of other beneficial ITSM capabilities. Then there’s the potential to utilize process automation across the enterprise – with human resources (HR) and facilities two popular targets.

The whole story becomes one of strategic planning for added business benefits.

Think big, or at least think bigger

So, if you have a service desk or ITSM tool implementation project don’t treat it in isolation, make it a part of an on-going continual service improvement (CSI) plan; keep your project team together (or at least a subset of it) to explore, define, and deliver additional future benefits; and budget accordingly.

The same is true if you are benefiting from third-party assistance. Think beyond the initial go-live and the cake eating. If you’re working with a tool-vendor partner, beyond choosing them wisely and then getting your service desk up-and-running quickly, look for a partner that wants to work with you in a strategic, long-term relationship. Importantly, where your business requirements drive the program.

Plus, this relationship’s mantra shouldn’t be: arrive, implement, eat cake, say goodbye. And, likewise, a service desk or ITSM tool go-live, and now seemingly obligatory cake, doesn’t signify the end of a journey – it’s just the start!

With hindsight, maybe wanting to “ban the cakes” is a little draconian. Perhaps we just need to act a little less like we’ve accomplished the unachievable and more like we’re merely pausing for breath before setting off on our continued journey of ITSM improvement.

So, plan for longer-term needs and benefits rather than just up to the point of all that ITSM tool implementation cake-eating. And this applies if going it alone or using third-party assistance in the form of tool-vendor partners.  

Martin McKenna Photo
Martin McKenna
Event Director at it500 Ltd

Over 30 years ago Martin McKenna joined Mitsubishi Electric’s Technical Services Group working on their Help Desk. He went on to manage the team and even created a basic service desk tool in DB2 before ‘real’ products were available. Since then he has been a product specialist, implementation consultant, trainer and project manager. He then moved into Account Management and Sales with Royal Blue/Touchpaper/LANDesk and worked on some of the largest, award winning, service desk software implementations in the UK. Nowadays Martin is the Events Director at it500 Ltd running events such as IT in the Park, plus other ITSM conferences in Scotland and can be found regularly blogging on LinkedIn. He also holds an MSc in IT and is in the process of writing a couple of books.

Want ITSM best practice and advice delivered directly to your inbox? Why not sign up for our newsletter? This way you won't miss any of the latest ITSM tips and tricks.

nl subscribe strip imgage

More Topics to Explore

One Response

  1. Excellent article Martin and you are right, too many relationships finish when ITSM is rolled out. Having recently seen this from both the client and the partner side, what I can say is that here at Service Integrators Ltd we believe in a relationship with the customer, working towards the correct outcomes and not just having cake and eating it. For that reason, we have recently started doing a Premier Support Service aimed towards ensuring the delivery of a customers CSI plan and allowing them to partner up with us to deliver it.

Leave a Reply

Your email address will not be published. Required fields are marked *