I was responsible for the improving the managed service architecture of a multi-year service contract already in-flight. There had been significant issues raised over the quality of the service up until my engagemement.

The main complaints were:

• Support resource not seen to be solving any reported issues
• Missing roadmap meetings
• Not feeling the value

An action plan and strategy was put in place, for me to conduct quarterly service reviews where I would present the latest features of the products and recommend strategy for upgrade and utilisation of these features, including any enhancements we could provide to the service.

The support resource issue was identified as being a follow on outcome of the customer not willing to log tickets and instead engaging the named resource directly. In this way the resource was being treated as a contractor and being asked to work on various unspecified tasks and issues. In discussing the issue with the client, I suggested they could either continue with no SLAs and agree to the support resource under 1-day per week effort, or that in order for us to track performance and ensure requests were deailt with, they would need to engage with the service and log tickets.

However, as many of the requests would have been out of the scope of the service and meant engagement with professional services, they did not want to implement this change. They prefered to carry on under the existing arrangement, without further complaint.

During this time I was also able to implement health checks for them and identify a number of security vulnerabilites which were esclated to their CISO. One was the identification of plaintext username/password strings in running processes, and the other was production level software running under a non-service account credential.