 Thank you. Hello everyone. Today I would like to share with you all the story of who is one of the largest financial enterprise which created its own ecosystem and how it helped its clients to succeed with it. So this 232-year-old investment company is serving its clients who are property owners, financial advisors, government, corporations and handle it with individuals with its 12 business clients and more than 250 client-raising applications. That's how it helps them commit to opportunities across 100 markets in 35 countries. There are a lot of destructive innovations happening in the financial industry today. The highly-complete and financial startups which are popularly called the SpinTechs are revolutionizing the financial world with high-end technology. Technological trends include wearable computing, big-data analogies, cryptocurrency and more. At this age of interruption, what's a company's innovation initiative? So 250-plus applications, they were all developed at different points of time, will focus on a single service to address specific business requirements. But because of that, the clients of today are going to a fragmented and disjointed experience. So a strategy solution was devised to solve that. That's the digital ecosystem, the strategy to a new generation technology platform. The motto is to deliver a unified experience which is simple, powerful and secure as well. The enterprise user experience team joined hands with business and technology companies in shape. On our road, we faced a lot of challenges. Firstly, the whole thing is a legacy system. It didn't encounter significant changes over a period of time, but it had innumerable features used by people of ages. And there are multiple user groups like financial advisors, local leaders, operation associates, sales assistants, their usage patterns and priorities should work. And all applications need to comply with serious regulatory requirements. Ever all, the clients are never the same. They have specific business requirements for which we use to provide customized business solutions. Considering all these factors, what was the first step in the initiative? See, we wanted to start with collecting the evidence to discover the problems in the existing system. So we worked out a great survey to all our clients to collect their feedback on four major assets. So how effective is their application in accomplishing their everyday job? How easy or difficult is the whole experience? How enjoyable is the whole experience? And how likely were they recommended to others? The results brought us the reality that the application helped them just to complete their task. It didn't provide them an end-to-end seamless experience. It wasn't much effective, easy or enjoyable. You'd probably guess whether any recommendations were a fact. And now, it was time for us to take little deeper. We wanted to analyze the usage factors with respect to the application, device that they use, frequency of usage, functionalities. So for all these analysis, we have a dedicated usage analytics team with us who work on things like click-through feedback and service calls. And with that, we had answers for all the questions related to usage factors and most of it was functionality of application last month. How many people have used a feature using mobile last month? How many people have adopted global version to date? Which is the top two user groups of any application? So look, we had surveyed and usage analytics reports serving as evidence, modified the key users. So it's time for us to do some field work with that. User researchers from the team went to meet our users in their workplace. They spent full day with them. They wanted to analyze how they schedule their day, what are all their motivations, frustrations, a magnitude of manual work involved. They tried to, at the end of the day, we have got interesting insights like most of the advisors who do sensitive jobs like placing trade for their investors start to use their application on their way to work or even at their home. And most of the operational associates who work for more than 9 hours a day, they hardly take any breaks. So this helped us to understand our users and their work lives much better than before. And with those observations, we created the prospective user journey maps for all the user groups. We plotted their actions, their gaps in the experience, their own suggestions to improve the experience, frustrations and everything. This helped us to find the opportunities to improve the experience. We use it analytics and the contextual enquiry we have found that there are serious problems in the existing systems in our behavior. So we conducted usability tests on the UI home and the behavior that existed in the system. But this time, we wanted to use our own employees because we wanted something by asking that of a known user who are totally new to the system. We tried to mimic the client system's UI behavior with our own internal applications. I would like to show you some examples of a test that we have conducted. So the first is test on moral values. So we just gave them a simple task of adding a member to the dashboard. So it's with an internal application. So in that, the panel will be inside that column where only 10% of the people who are able to complete this task successfully without any problems. All of us had problems in finding the call to action and selecting the content and verifying the action. The next is the most extensively used usage pattern in our applications. We had crazy long forms. The last number of weeks. It's basically because of the regulatory requirements. So here we tested with two versions of the forms that we had. One is with the long forms in which all of those fields will be the single page. So once we get what completely uses from the whole experience to be really exhausting and boring. But we really like the other version. More than 80% of the users really like to use this exact version. They are completely the forms of much ease. So likewise, we have conducted tests on everything that's been evaluated. So now it's the end of all the research and analysis that we have conducted in our existing system. So the whole needs are now and trying to prove their findings into action of the results. What are they? So most of our clients are users of our multiple services. They are logging into multiple applications every day. One application to manage client info details. Another application to provide the retail market use. And across all applications, no one is as steep as the edge of the functionality as the overlap. Things like the stock client and the cons can be found in most different applications. And it was found that they were all redundant and added to the product list as the most important spoiler of the experience. As I said, all the applications were developed at different points of time. They all had their own set of UI elements and behaviors which were improperly fun. From simple input-form elements to huge reports, everything was limited to different behaviors and the level of user centeredness was very low. And there were problems in consistencies with the ramification patterns as well. And people had serious problems in finding the information that they wanted. They were able to find the right information only after at least few unsuccessful patents. So having found all these insights, it was time for us to ideate and design. We wanted to start that phase by creating a structure for the whole ecosystem. This was expressed by inviting for the process to help us understand all the services that we offer. With that understanding and the previous analysis that we have done, we tried to come up with numerous ideas. Before zeroing on one of them, we asked ourselves a few phrases. Which structure would eliminate the problems with redundancy, functionalities and information mining, which is going to help users and all different user groups. Which is going to improve the business. By asking all these questions, we have come up with a taxonomy and tested it with our real users. A set of 150 users who are drivers in their role, the services that they use and even the geographical locations were part of this whole process. We used the close card setting and chronology in which we had the primary menu fighters. And the users are supposed to place the functionalities under respective menu. During the whole process, we encouraged them to think about it. So at the end of the session, we have got valid performance with which we have created the taxonomy that exists today with the system. The next thing we are going to do is our own design system. A design system which will be bought, which will serve as a foundation for all future design solutions already from quick and smaller ones to large and highly impactful ones. Something which will make the design and the subsequent development process by the faster and heavy user center. With those things in mind, we have devised some influence points. It should be consistent throughout the organization. It should help them do their everyday job with much efficiency and effectiveness. It should be scalable to accommodate future use cases and requirements reusable from a designer's and developer's perspective and insurable responsibility. So we started this whole design system exercise by doing task analysis. We identified gaps in the existing task flows. We defined the rules among the task flows. And then we tried to do all the elements of the design system into one major component, which is typography, color palette, layout, interaction patterns, and application. I'd like to show you some glimpses of the design system that we have created. So this would show you the layout, which was based on different compactors and mobile. And this would show the components like colors, typography, text flows, patterns, to a tab, progress bars and everything. So every way in a maintenance behavior were defined based on the different scenarios in which they would be used. Next comes the component groups which has data grid, model windows, forms, etc. And the next part is the developer's model. So this shows core associated with everyday maintenance behavior. This is something which brought the whole design system into life. No designers can be without testing a migration right. So the beta version of the application was released to all of the users and with their feedback and usage and analytics the whole system was updated before we released the final version to all of us. After all this, what's the impact that they have created? Just at the end of the first month of its release more than 50% of the existing users adopted this version. And the user satisfaction increased to 75% and the net promotion increased to 60%. But through all these quantitative aspects we learned that the overall productivity of the users improved a lot. They were able to complete their everyday job with more efficiency and less time. They were happy using a simple sophisticated powerful system in every environment. I'd like to make a whole story with Bruce Bruce once again. The design at the end is about creating better things for people and along the way can generate better profit system. And today we had the privilege to make this a great deal by creating positive impact in our users' lives and in our business system. Thanks for listening. Yes, so as I said we have multiple services, multiple business lines. I'd like to put some examples like we have investment management wealth management we call it as clearing services so we call there too many clients like banks they call it a city bank or something so common. They were all clients and they were using different applications but we are on a road that there are people who are using our multiple services and they were using multiple applications so the whole experience we learned that it is a disjointed and fact untimely experience so we wanted to optimize it by creating a single approach by creating a single system where all the people can use a single system to move all their jobs that's what we call as the digital ecosystem. We actually created our ecosystem which could house all the services that we offer all the services that we offer using hundreds of applications we created a single ecosystem where all the people can use their services and just go along in and use their services. Another question was on the productivity is it a productivity group how are you willing to measure that? These are the quantitative aspects one other aspect that people can share is the road activity that we have it's just two months right we have analyzed it our usage analytics team I would like to explain how our usage analytics team works so they basically work on things like feedback and prove it wrong so like if you are into an application and using a particular feature once you start a particular task they have to have a starting point and consider that the end point or you are just placing a trade for your own investor so how long are you taking what is the average time taken by most of the users completing that trade they were all able to measure that but still we couldn't give it as a quantitative aspect because it wasn't a short thing so that's how we said that another aspect is the overall productivity of the user for most of the users so what kind of challenges you faced while migrating the front end and back end technologies in your presence even though I never wanted to capture the technology side we created our own frame of platform for this a bit of motivational issues that you have because developers always have that association since then there is a customization all the clients will never use all our service so one in one people who have use or micro service where another people just got into the system they'll just be in two services of us so the customization part that will come up well in our initial stages of development that's the greatest challenge that we had in the customization of all of us can I ask one more question how do you measure the consumption that your users are able are using certain features and not using certain other features it is definitely possible I'm not sure about the exact technology that they are using they are using some log files and all so if a particular application has multiple menu items and multiple functionalities and under it those people can really able to measure how much what is the usage of a particular functionality it's easy to find it that's the work of usage and how it's seen to analyze the usage patterns thank you Abhinaya for your super slide thank you