Innovation Journal - Cognizant

Innovation Journal - Cognizant Innovation Journal - Cognizant

cognizant.com
from cognizant.com More from this publisher
26.11.2014 Views

REWIRE - KIOSC AVM involved in developing such a framework. To start with, they summarized areas where service delivery gaps could exist: Cognizant’s delivery director for a large life sciences vertical answered an insistent call on his mobile phone. It was his boss, the business unit head of life science. He shared an interesting challenge from a customer that he had just met. While the client was satisfied with the deliverables of the latest project, the BU head explained, there was a concern that not all of the client’s portfolios were speaking the same language. Everyone’s scorecard was green, but since each portfolio had its own way of doing things, it was hard to compare the value-adds being delivered across projects. The client engagement included improving operations, business processes, business continuity, enterprise efficiency and risk/security, as well as reducing enterprise costs. The client’s CXOs felt that since Cognizant was known for its innovation and proactive best practices, maybe it could establish a rigorous service assurance framework across all of these areas. The application portfolio Documentation and knowledge Processes and tools People Then, they analyzed all the aspects that could lead to service failure: People-dependent activities lacking rigorous processes Delivery team’s confidence level in responding to issues Delivery team’s knowledge of customer processes SLA adherence Penalty clauses for SLA slippage Proper infrastructure support Such a systematic approach would be a great opportunity, the business unit head reasoned, since it would be applicable to all large AVM projects and could even be a new service offering. The framework should enable a proactive response to alerts and incorporate best practices that existed within Cognizant’s individual practice areas. The delivery director was inspired but also a bit overwhelmed. He called his team together to discuss the multitude of challenges Using the Toyota Model of innovation, the team then proceeded to seek more understanding of the situation by sending out surveys, interviewing stakeholders and observing team members working in their development centers. The team sought input from project managers, project leads, business analysts and users community. There was a multitude of meetings, full of food and, of course, Excel spreadsheets, and presentations. 91

REWIRE - KIOSC AVM The team summarized the most important findings: Business users reported reliance on experts to resolve data issues. This led to the need for a robust knowledge management foundation for knowledge assets and training. Managers at the client end reported slipping deadlines, resulting in business escalations. This signaled a need for integrated service management to ensure proactive planning and periodic reviews. Global incident managers said there were too many high-severity L1 tickets with no structured root cause analysis. This led to the formation of operational blocks, which focus on operational execution through proactive prevention and coordination with the customer ecosystem. innovation should provide a holistic view and a proactive approach and also that it should be technology/portfolio/business unit agnostic and allow every portfolio team to execute excellence every day. “KIOSC is very detailed and ensures that all the aspects of the managed services model have been covered.“ – AVM Service Engagement Manager New members of the team felt there was a lack of structured and formal knowledge transfer processes and, as a result, risked missing SLAs. This led to a need for scope management to address gaps in scope and ensure service delivery. Application managers said they were unhappy with the quality of the updates provided by the support team. This led to the formation of change management, which ensures improved schedule, quality and cost adherence. These insights gave the team a fair idea of the causes of service failures, as well as the must-haves vs. good-to-haves. They had identified the core components of a service delivery framework that would highly satisfy customers. It was clear that the service assurance 92

REWIRE - KIOSC AVM<br />

The team summarized the most important findings:<br />

Business users reported reliance on experts to resolve data<br />

issues. This led to the need for a robust knowledge management<br />

foundation for knowledge assets and training.<br />

Managers at the client end reported slipping deadlines, resulting in<br />

business escalations. This signaled a need for integrated service<br />

management to ensure proactive planning and periodic reviews.<br />

Global incident managers said there were too many high-severity<br />

L1 tickets with no structured root cause analysis. This led to the<br />

formation of operational blocks, which focus on operational<br />

execution through proactive prevention and coordination with the<br />

customer ecosystem.<br />

innovation should provide a holistic view and a proactive approach and<br />

also that it should be technology/portfolio/business unit agnostic and<br />

allow every portfolio team to execute excellence every day.<br />

“KIOSC is very detailed and ensures that all the aspects of<br />

the managed services model have been covered.“<br />

– AVM Service Engagement Manager<br />

New members of the team felt there was a lack of structured and<br />

formal knowledge transfer processes and, as a result, risked<br />

missing SLAs. This led to a need for scope management to<br />

address gaps in scope and ensure service delivery.<br />

Application managers said they were unhappy with the quality of<br />

the updates provided by the support team. This led to the<br />

formation of change management, which ensures improved<br />

schedule, quality and cost adherence.<br />

These insights gave the team a fair idea of the causes of service<br />

failures, as well as the must-haves vs. good-to-haves. They had<br />

identified the core components of a service delivery framework that<br />

would highly satisfy customers. It was clear that the service assurance<br />

92

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!