Innovation Journal - Cognizant
Innovation Journal - Cognizant Innovation Journal - Cognizant
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
- Page 41 and 42: RETHINK - TRADE RECONCILIATION HUB
- Page 43 and 44: “The mark of an artist is how muc
- Page 45 and 46: REWIRE - A BETTER BUSINESS INTELLIG
- Page 47 and 48: REWIRE - A BETTER BUSINESS INTELLIG
- Page 49 and 50: REWIRE - A BETTER BUSINESS INTELLIG
- Page 51 and 52: “One must be something in order t
- Page 53 and 54: REWIRE - DEALER TAB Non-availabilit
- Page 55 and 56: REWIRE - DEALER TAB invested in the
- Page 57 and 58: “The less effort, the faster and
- Page 59 and 60: REWIRE - FASTr Increasingly, physic
- Page 61 and 62: REWIRE - FASTr ”We have to be agi
- Page 63 and 64: RETHINK - FASTr The final solution
- Page 65 and 66: “The ones who are crazy enough to
- Page 67 and 68: REWIRE - iASSESS A leading educatio
- Page 69 and 70: REWIRE - iASSESS Feature for Teache
- Page 71 and 72: REWIRE - iASSESS President Obama’
- Page 73 and 74: REWIRE - iASSESS Q: So, your team
- Page 75 and 76: REWIRE - PLATINUM DWBI Article 10 P
- Page 77 and 78: REWIRE - PLATINUM DWBI Common Chall
- Page 79 and 80: REWIRE - PLATINUM DWBI approach, th
- Page 81 and 82: "Now that we have met with paradox
- Page 83 and 84: REWIRE - EXTENSIBLE ERP Managing he
- Page 85 and 86: REWIRE - EXTENSIBLE ERP time, the q
- Page 87 and 88: about the business, go to the accou
- Page 89 and 90: REWIRE - KIOSC AVM Article 12 KIOSC
- Page 91: REWIRE - KIOSC AVM Proactive identi
- Page 95 and 96: "Necessity is the mother of taking
- Page 97 and 98: REWIRE - DESCRIPTIVE RFT Photo: Shr
- Page 99 and 100: REWIRE - DESCRIPTIVE RFT manager al
- Page 101 and 102: "The man with a new idea is a crank
- Page 103 and 104: REINVENT - CONCIERGE SERVICES Artic
- Page 105 and 106: REINVENT - CONCIERGE SERVICES On bo
- Page 107 and 108: REINVENT - CONCIERGE SERVICES appli
- Page 109 and 110: REINVENT - CONCIERGE SERVICES as we
- Page 111 and 112: REINVENT - TOPICS CURATOR Article 1
- Page 113 and 114: REINVENT - TOPICS CURATOR Helps ass
- Page 115 and 116: REINVENT - TOPICS CURATOR sifting t
- Page 117 and 118: "If you want to build a ship, don't
- Page 119 and 120: REINVENT - SEEDING INNOVATION Cogni
- Page 121 and 122: REINVENT - SEEDING INNOVATION Team
- Page 123 and 124: “Don't confuse the art of the pos
- Page 125 and 126: REINVENT - 124
- Page 127 and 128: REINVENT - INTO THE NOVEL NATION Ar
- Page 129 and 130: REINVENT - INTO THE NOVEL NATION ha
- Page 131 and 132: “Discovery consists of seeing wha
- Page 133 and 134: REINVENT - THE REAL DEAL 3. Some ap
- Page 135 and 136: REINVENT - THE REAL DEAL Clearly, t
- Page 137 and 138: REINVENT - THE REAL DEAL 5. Since t
- Page 139 and 140: REINVENT - THE REAL DEAL circulatin
- Page 141 and 142: 20 12 Innovation Journal Cognizant
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