 this question that comes up and even today it came up, oh so your parents are doctors and why didn't you get into medical? And so this question I've been answering for many years but I think what has carried forward is their ability to be able to understand people and also to be able to empathize. I've seen my mom waking up, she's a gynecologist, waking up at 2 a.m. sometimes there's a delivery that's happening so you know all those things have somehow been a part of my growing up years and that has helped me become a more sensitive person. So much sensitive that sometimes my parents would be like, oh but if you see blood you have to be strong because you can't be like oh that person is crying because you have to be stronger to see their pain also. But I think that sensitivity has helped me become who I am today and also helped me become a designer. And of course you know seeing my parents I was also keen on to pursuing medical but I'm glad to say that I'm in the design profession which requires you to be more sensitive, more empathetic and also more understanding towards others' needs. So here I am today presenting to you some of my experiences and although these experiences are related to the work that I'm doing at SAP but I think all of us could relate to it because we are in product teams, we are in big IT companies, some of us also have our own startups and some of you are entrepreneurs. So I think we also face similar challenges and I hope that my talk helps you connect with it and also helps you understand how we could kind of deal with those challenges. I just, how many of you, I'm just deviating a little bit from the topic but how many of you have followed the Olympics for 2016? Can you please raise your hands? Okay, great. So this is the excitement that just got over around all the events and what we really saw was a testimony of great effort and passion by Indian sports women and of course there were a lot of prejudices and a lot of things but they stood tall against it and these are some of the images of their grit and glory I would say and of course this is a great inspiration for women, not only in design but in all walks of life. So here I am just sharing some of these images but what we take from this is how it got translated into the design journey. So the preparations and hard work that have gone over the years and motivation to break the record was even higher at the Olympics and of course what we see here is a lot of effort that have gone into it but where I work in custom development it's really tough because it's not like a product scenario where we have huge time cycles and of course there is advantages to that where we have enough time to do user research and all of follow the exact process but in custom development I see it as a marathon. Running a marathon is like a 100 meter race and you have to get prepared for it and all eyes are on that. So what happens really is like it has that enthusiastic start and also dramatic finish in a very short span of time. So taking this analogy forward at custom development we learned that in shorter design sprints with the same excitement and rigor we could open doors to collaborate with customers on further requirements. So what exactly do I mean by the design sprint or with an SAP we also call it sprint zero. So the design sprint is a mini project in itself which delivers tangible results within a short period of time. So what we have is like the execution plan that has to be quick and collaborative in nature and which helps our customers envision the solution that much before it gets developed and also kind of gives them confidence that their expectations would be met and their vision would be converted into reality. So basically this is where the design sprint kind of fits in. So we have the UX concept and design which we call the design sprint and then we have the following sprints sprint one, two, three carried forward. I'm sure most of you who are in the agile mode understand the sprint cycle. And so what really happens is that a small engagement that has encapsulated in such a manner and helps build customer trust. Also assist customers to take conscious decisions while spending their money and also reduces risks. And what benefits is that we have tangible results. Also we get a better understanding of requirements and build deliverables which can further be consumed by the following up custom development project. So our focus really is individual interactions over processes and tools. A working software or prototype over comprehensive documentation. Customer collaboration over contract negotiations and responding to change over following a plan. So this is the shift that we have made and of course this is how it typically looks like but it's generally following the same cycle of design but in a shorter cycle I would say where we can speed up the innovation, we can issue discovery interview and based on the workshop mode and also build a quick prototype which leads to finally a specification and backlog which gets used up in the sprint, upcoming sprint. So where this actually helps us deliver quick tangible results in a short time, in a close collaboration and also it helps us create a joint understanding and of course budget is always an issue so it's an attractive pricing because we are doing a smaller sprint and we could use those design sprint deliverables into this upcoming sprints. So this is from the methodology point of view in CD where we think of the objective and what would be our commitment and of course what would be the customer's commitment and the deliverables. So I'll quickly skip through this and walk you through the other areas which is so what it really helps is that we could actually identify the initial ideas and a rough project size gets discovered. We are in the customer, we get the customer support and readiness early on which leads to close collaboration during the design sprint and we also get the required customer resources which means the user representatives or end users in IT. So how does it work in the plan? So basically the business process workshops that we conduct are generally over a span of three weeks to two months and these business process workshops lead to product vision. They also convert user research which further leads to understanding the end user requirements, the technical assessment which leads to architecture understanding and the mock-up or prototype creation which leads to a tangible result and then finally validation which leads to customer acceptance. So this design sprint actually helps us build a very good relationship with the customer early on and we actually try, the customer kind of gets to understand that this is SAP's way of working and there's a comfort level and the customer opens up to further talks and iterations. As we already saw in the earlier talks, design is a iterative process and until and unless we get our customer support we will not be able to reduce good results. So what is the design sprint we already talked about and why the design sprint? So SAP, as some of you would be knowing, is a world leader in enterprise applications and we are world's third largest independent software manufacturer but still we have our challenges and what are those? Basically, the top use cases are identified in the traditional approach but they're never budgetized. The value of the app is not tangible before the final design is there and of course we have concurrent business requirements yet their unclear effort estimates are based out of uncertainty and there are unrealistic customer expectations. Also, the backend integration is one of the main effort drivers which gets ignored. So the typical software development approach as we all know it is that as soon as we get the contract that gets signed, we get into the execution phase where we quickly start gathering requirements, documenting specifications, sprint, scrum planning, resources. That's the original approach which most companies follow and of course the shorter timelines but there is a shift with the design sprint is that it acts as a hook to build trust early on. So it helps. Basically, the short timeline helps us build a relationship with the customer. The iterative approach helps us get quick feedback on from the customer and end user and once again it's a door opener for bigger deals and projects and we build our solution which is focusing on user friendliness so it's the end user that we get directly involved with and stay in focus. The visualization part helps us to deliver reusable mobility components and also reuse the design and specification backlog which was created in the design sprint in the following CDP and also the design to budget. So if the budget is constrained basically the customer gets to understand what is the design process and the value of design gets up front, you know. So basically the customer support and helping building the requirements base and the design solution gets evangelized early on. So customer point from the customer point of view it's valuable because it increases trust, decreases the entry barrier and we give tangible results so it's a wow factor and of course we've mitigated a lot of risk of taking on a huge piece to be able to do it all in one go and we establish a working model. From a custom development point of view it's higher win rate and we could support sales cycle. We have given accurate estimate because we've already worked with the customer once so we understand what is there and there is IP protection for the early sprint so it doesn't really go to the competitor and there is software and software related there is a lot of revenue generated from this software and software related services. So the design sprint thus fits very well from a technology and business value point of view and it is this impact which is created by the design sprint by focusing on smaller milestones which leads to bigger milestones in future. So the impact that is made through the design sprint and that gives this end users a glimpse of what could be achieved and in a short span of time it further helps gain trust and give assurance that SAP has the right skillset and know-how and could be a trusted partner in the journey. To gain insights into the requirements and also tie up with them in their vision. So these are some of the deliverables which come out of the design sprint which is our vision nerves and scope document and initial product backlog as well as a user experience of a prototype and then a final financial proposal for the next offer. So this is our new approach towards focusing on design and helps building trust, excellence and success. This impact which is getting created is at the low entry barrier risk mitigation and tangible results which we already talked about. Again, an established working model and so many times I've seen customers, project managers saying that what is the value of UX? And of course to that I would just say it's experience by doing. Until now, this is the experience they work with us. Just recently I was on a customer site and my project manager was like, but you're a UX designer, what will you do? I don't know why am I taking you on the customer side and by the end of the workshops, by the end of the design sprint he actually came and thanked me that thank you. I mean today I finally realized what a great impact it has made and it saved us so much cost of building it straight away. So I think it is essentially experience by doing and we all have to fight this battle as UX designers and we're continuously striving but it's the same grit and determination that we saw in Olympics that women in design have to also take up. So with that I would like to, since we're running out of time also, I would like to thank you and for questions, are there any questions? So are there things that women's print cannot solve? Cannot solve. So see design sprint is focusing on smaller tasks so we're not taking the whole chunk altogether. So yes, it's not solving all the problems in one go and that's the whole idea that we are not going to solve all the problems in one go. We're just going to give the customer a flavor of what it is to get one problem solved at a time and once the customer is happy, those deliverables get anyways converted into the project and we obviously have continuous workshops later on. So what that answers? That the research work is included in this grid of we do a full research and then start sprint design. So the research phase is included in the design sprint. There was one slide which I showed, I'll just go back to it maybe. That was the how part. So we have in the design sprint, we are focusing, that's a good question because we definitely are not covering all the research part in one go because as I said, we're limited on the time and it's a very short design sprint. So but yes, it helps in a way because we are focusing on, so we understand and prioritize. So it's called prioritizing backlogs and when we're trying to understand user requirements. So we definitely get an overview and from that we prioritize that in the design sprint we're taking these and in the upcoming sprints, in the upcoming engagements we'll be taking onto those. So at least the customer gets to understand the process and the value of it which is otherwise missing. Otherwise everything's taken, you should only take it back much that you can chew. So it's like that. But sometimes we have to go back and get, if I get further research, I get points where I need to go back and change my design to further older ones. How do we deal with the situation? Yeah, so if you do change, see in any case, you will be, at least for the design sprint, in the workshop mode it's like a war room situation where you're actually there understanding, creating and coming back with validated stuff. So it's not that you close everything there and there. And what comes up is the next new thing. So sorry, just one minute. So yeah, so basically you're closing all the things that you promised for that design sprint within that period of time, whether it's three weeks or four months or two months, basically it's shorter time duration. It's not like a one year or two year cycle. And what comes up next is the next phase of workshops. So basically this is like sprint zero. You could say it's like preparing for a race. Thank you.