Launched early this year, ITIL 4 reflects recent trends in software development and IT operations, providing an updated framework to bring philosophies such as Agile, DevOps, and Lean to the domain of service management. True to the original philosophy, ITIL 4 aligns IT services to serve the customer experience. But everyone in the IT engine-room must speak the same language if ITIL is to fulfil its potential.
Let’s look closer at Unified Communications to get a picture of ITIL at work. Generation Z-ers are spoilt for choice, driving up their expectations of brand experiences. No one sticks around for average experiences when so many shiny new options abound. Opinions are formed from a braided stream of interactions between customers and brands. Broadly categorised as customer experience (CX), each positive interaction adds to the balance in the customer’s bank of goodwill. However, bad CX results in a withdrawal – and when the bank of goodwill is overdrawn, customers walk out the door.
Here’s one example from the UC stable - voice, considered by many to be the latest UI. Despite the digitisation of communication in the form of emails, text messages, and online chat, voice remains a critically important real-time channel, preferred by people in the moments when big decisions are made.
Nothing frustrates customers more than having to repeat themselves or deal with a poor quality interaction. It can be the last straw in a strained relationship.
Technically, real-time interactions, such as voice, challenge IP networks, which are inherently not real-time. When problems start to occur those in the service management game without a framework tend to get stuck in the ‘UC circle of death’. The voice team looks into it and can’t see anything wrong with their applications, so they point to the network. Network engineers scratch their heads and point fingers at server infrastructure, or maybe back at the application team. Round and round we go. In the meantime, tempers rise, customers give up and the brand takes a hit.
ITIL processes lend themselves to UC because they unite disparate IT groups, using standardised processes and reporting to ensure everyone speaks the same language. So network engineers understand the language of the voice team, the infrastructure team, the application team, and so on.




