 So, before I actually start, I would like to allow what I actually hinted is that mindset is important. So, today basically what I am going to share with you is from a design perspective, what the mindset can be and how it can actually impact your organization with really, really great products. So, why as you can see that I today prepared today for whichever design, so we will be touching upon the concept of design as a you know part of the operations. How many of you have heard the term design ops or day jobs ok, it is a relatively new term that is taking rounds on the internet like you know. So, it is basically a mindset like how we can actually come up with proper operations you can define operations for the design for the organization, so that you know it can actually correlate and you know complement day jobs. So, before I go into all those things let us start with the very basic thing because we are now talking about design. So, let us see I mean what design is basically you know the traditional thought like you know the belief is a design is being treated like a discipline ok. So, design can actually you know kind something good or maybe he can create a new UI that looks really nice. So, we see design from the point of view like it might be something related to a discipline where it relates to the look and feel of something you do, but if you see in a product sense design is mostly it is not only limited to part actually how it looks or feels it is more about like how it actually functions. So, I think you know I am just stuck in with the typical partisan problem of deep jobs design is how it works. So, if we see from you know the multiple you know others to how we try to define design right. So, one of the I mean comes from the you know very popular approach that we follow that is design thing. So, from design thinking I mean if you try to see design, so it is like a creative problem solving. So, if you are creatively trying to solve it you are actually in the process that you are going through is design. So, in that broader sense actually what I am trying to do here is I am trying to analyze that design of some desktopsies and I am trying to you know I will really know extending what are those you know high level aspects of everyday jobs and how exactly you know it managed to your organization. And you know if on a ground level what exactly you can do to make sure that you are doing that. So, basically if we agree that you know design is all about like creative problems solving that is the order who is trying to code, he is trying to balance the if else it was like. So, he is putting you know his creativity at work, so that we can put it in the right place to make your product work. So, in the similar life when a product manager actually tries to come up with some kind of user and he is trying to get insight from the market on the user and then he is trying to come up with ok this will actually work. So, he is trying his creativity under you know his area he is going and trying to solve it. So, in that sense if we see all the rules are actually the same. So, in that sense if we see that in any organization all those business development you know you know everything is right. So, all of them we can actually know with all into this mechanism. So, if that happens then this idea is basically the common thread you can see here that will connect everything. So, it is like this. So, when we are talking about head jobs that means we are trying to come up with you know some kind of new kind of answer may be the best practices. What we can do to make sure whatever we are trying to do the way we are actually trying to solve our you know I mean creativity solve our problems right. How we can do that? So, there are so many actually approaches how may be there like we follow different type of processes like let's say as I implement from the process point of view we are also coming let's say design making is actually you know leading the many organizations and then there is user centered design and someone can actually start doing something like you name is ok I have started by only 3 to 4 persons I will go with you right. So, there are so many processes are there. So, when we are talking about head jobs it also means like we are actually plus all those processes in second way. So, that it makes sense we can do things we can actually you know design case in a seamless way other we can say you know many more. So, that is what is. So, when we are actually talking about the organization. So, as I said I know because all these personal parts of you know you are calling under design right. So, any organization can be treated as a design organization. So, there is no organization in the world which actually it is not even a design in their daily life right or daily work program to solve some problems to come up with some product of the services right. So, that in that sense every organization we have to travel right it is all about the different type of operations that happen within the organization. So, let us say we are following some process right. So, there are always certain types of communication that happen. Let us say I write as a designer I need to offer my product manager to get some requirements right on the right. Come up with some kind of like workshops as you like that is the same. So, I go and I need to get to a role. So, mine is one role then this is another role right. And we are actually having some kind of feedback flow. I am providing some inputs I am getting some you know feedbacks coming. It is the same way for the other side right. So, in that sense if you want to say there are a lot of roles actually that are involved in any of those common assets starting from product wellness by developer appetite types, user researches, user experience name, you know visual designer, etc. So, you see those are different roles and in each of the process that we actually follow basically what is happening is we are having some kind of you know versus the feedback loops that goes to different roles. So, it is just as you can see what it does is it helps you find it and end up in the shortage and the most effective feedback. So, it is like let us say we are trying to come up with a new product and let us say the product manager has some reason of a new mobile phone whether you go and do a if you study in the market so you just insights or you will just move here you know one after one design thing session in the organization that depends on what is what type of feedback loop is trying to follow. So, it is actually the possibility of feedback loops that you know the different roles are going through. So, design jobs or the day jobs that still helps you finding out what is that right feedback loop of sequence that you need to follow so that you know you reach your you know you have your goals effectively in the service path. So, how exactly this is like how you began the thing is how exactly happens in the now we see before that we need to keep in mind that they just itself is a mindset just like the mindset of day jobs. So, if we see day jobs whenever we talk about day jobs so we the immediate thing that comes to our mind is like ok automation CICD we will do like you know and then we also talk about all those you know that supports it right. But then basically if we really see day jobs is a mindset where you know it actually tries to remove the weight from the process. But if I is predictable because that you can actually replicate in the period and you know they have to limit the level and you can automate certain things right. So, make it back with you make sure that you know feedback loop is actually solved so that you take some action on that. So, this is basically the you know the day jobs mindset, but if we see yeah. So, so basically from the day jobs mindset if we see then there are certain things mostly the pieces in the product life cycle the day jobs such as like you know build you deploy you test so that kind of you know actually fall. Then the initial aspect of the any product life cycle is ok in the actual organization right. So, we do ideally we do design or maybe the you know traditional sense of design in that sense right. So, those blocks are never touched or maybe when it is touched it is not actually basically done. So, to overcome that aspect day jobs actually help you to move to the next level take day jobs mindset to the next level what it does is it is no more limited to the development field or deployment you know cycle. What it does is basically it connects the vision field or you do whatever you are telling you. So, one example is like you have said there was a need. So, when the usually is actually you know having these by the investment is getting the delivery product. So, when you build that and you deliver it for where you deliver you can follow mindset systemically you know technology oriented which is dead. But when he is getting he finds oh ok this does not look good I was expecting it to you know feel like I thought. But you know those kind of aspect that we actually see it is not something which is complete or which is something logical that might have actually come in the initial phase when the product vision was clear. So, how you can connect from that product vision experience that you should get some end is actually you know is what you can solve. So, basically everywhere you can do is what you know we try to address and definitely it is all about human aspects. So, what how the product actually impacts emotionally like a person mostly touches upon the areas which is more than the quantified you know attitude is that we are trying to see. So, if you take any moment like one example is like let us say a testing I mean a testing scenario. So, typically if I go and I try to conduct with you right. So, basically what we see is like we can do something like 100 testing code quality checks and whether the functionality source is in the random type in the compiled type errors and those kind of things and then in the severity of the issues that we typically see when 4 and 5 are mostly cosmetic errors which you will get you know mostly when client is actually you know doing the UATV. So, at that time it is like you want to do anything right ok there is some bug in the code you know some compile development it is not like that. But mostly what you know the viewer customer actually says is ok it was good, but you know I wanted some Facebook and W experience. But you know that is never defined that is something human. So, he is connected to his experience. So, fascinating is the those kind of aspects which is related to the human right. So, those are at the right hand side if you see. So, like cosmetic issues, maybe usability issues, acidity issues I am not able to use it. Maybe it is something like user feedback or something like that. So, if you see if I am going left hand side or right hand side it is like a human brain. So, in depth of mostly we are more focused on this area that is the automation and the technology actually helping us to really do a good job there. So, what we are trying to do is basically we are taking over to little bit other also. So, basically I think this diagram actually explains that. So, these blocks are actually like vision and design. Whatever we are trying to develop in a product. But in a DevOps specifically from development department and testing. So, we cover all these. So, in DevOps basically it is super safe way of doing it. It is taking DevOps to the next layer in the terms of privacy. So, basically you can say like so, anyway all these are things. Then how do we make profit? So, where does that? Let us say you are running a startup then you know maybe you are running a team in an organization and where to start actually. So, let us see. So, step one is basically it is about you know establishing touch points. So, touch points is as I said in every organization and all the processes and the kind of you know how this is that happens on different levels. So, everywhere and there is some point where one role is talking to the other. Or maybe any let us say I am logging into a project management software. So, that is a class point where I will be as a project manager as a role. I am actually talking to a system where the discipline is about project management. So, or maybe if I am talking to a product manager I am a role. That is another role. So, a product manager is a different role. I am an interaction designer I have a different role. I am from a different discipline. He is from a different discipline. When we talk certain things happen. So, basically that we need to explore and those are each of them are actually one touch point. So, the first step is to find a touch point where you can actually you know remove the waste or you can improve the device or you can optimize it. So, how you can actually then identify those touch points. So, basically the I always let you know you can apply design. So, design thinking is as I think most of you know mostly about emphasizing defining and finding out the problem and then you know I get you are finding out the solutions or the solutions they say the services or the options rather than finding out the solutions. So, so that you can quickly over time you can go over that you know ideas. So, basically the whole of results is apply design management to our own process to find out the solutions and always let us say we want to improve what are the processes we are calling for the design in the broader sense. Then we need to apply the to our own process to understand and see where are those touch points. So, basically it will help you to find that out and also to find out some solutions to that. And then in design thinking there are multiple tools that actually helps you. But one thing we need to remember is in finding all the touch points those touch points can be anything it may be a role to role kind of like let us say a real role to visual design role or a QA role or a architecture role. So, there those roles might be complicated or having some kind of feedback or it might be a discipline discipline let us say he is a product manager and another guy is actually an architect. So, basically they both are knock on it is basically two disciplines are actually under the feedback. Similarly if let us say in a user research is talking about some kind of methodology to implement in the market to get know the feedbacks maybe the insights he is talking about some frameworks within that. So, the part of the key of the touch points are basically how it is identified what kind of those touch points can be those we need understand and identify so that we can some kind of solutions that will help us to remove those some kind of actually I wrote about one tool called metal process diagram basically this is when you actually use this anything you can come up with so many you know methodology and tools one of them is actually like let us say you use your mind mapping and you know you can use your personality and like so similarly this is one where you actually try to so basically the first step is to understand what is happening in your device based on that you can optimize so you need to find out what are those touch points so one example can be like let us say this is a pf character so so each of them actually actors the possible actors so product manager is actually doing one interaction design basically these are one touch point I think the outcome of this will be taken in the next so maybe what will happen is maybe actually talking about so you know visa like this I am envisioning this kind of product and he says this kind of interaction you can come up with that then the next thing is interaction design manager actually understand that certain technology I need to know what are those what is the feasibility and all so he might actually connect the other one touch point then what we do so who actually helps things like this one sample is like let us say the product manager is actually here and he is trying to do some kind of marketing analysis so basically what are the options so the idea is you need to understand at each role at each decision what are those options with that you need to have that you know what you can optimize understand so this is basically now a domain like marketing analysis so now you can say like you know there can be point people areas like customer analysis product portfolio those different you know mechanisms like why we use it so maybe so now what I am going to do is this actually right use category so he is trying to follow this so now within that there are prototypes principles what is that so now he will so if you see this is how you know now one domain is actually falling into the other domain it is the marketing research guy so the person who is marketing research guy he will be having a domain similar to this so this is basically the overlap so this is how PPD actually helps you to visualize how exactly you what are the options then how those communications are happening so that you identify the clutch points and then you try to solve so this one is actually showing like you know easier way how you can do that using some iron normal iron so one example let us see so here is a scenario so in a traditional design yes there is interaction design so planning is done interaction design then he did some I mean see he did some work and then your designer came up with some kind of there is some reviewer actually they transferred that how he developed now if you see in this kind of scenario there are four roles are set I have just to take now three of them each of them are actually using different roles and now all of these they actually try to follow some kind of some kind of maybe style right and also some kind of some people so this is a correct scenario so if we try what we can do is like the ideas you can create a solution and okay based on that can we actually have only you know one role who can provide some kind of that can actually be transferred to the designer who comes up with requirements can we use that directly as in the production development UI core can we do that so that's the kind of solution in the actual technology but this is the kind of solution that came up so what will happen is each is when we are actually trying to reduce one role we are doing some time and maybe the complexity we are trying to reduce so now what happens is basically you end up with some kind of solution that you saw then you will find out something like what is the solution from the technology and what is the solution from the technology and what is the solution from the technology and what is the technology and so now we are putting that you are replacing your the parts you are replacing your natural word of action so basically you are like how then you need to think now I have a suggestion can I actually translate that through technology so that might something like this so many people don't know then what will happen because the design system has changed can you use directly that to create an export and use so that is the whole lesson of what solution we got there so now looking at that actually I have the pattern and now because those patterns are not like that the buffer is actually open the grids are there it's he's hiding that and he's dragging some patterns from the below pattern then we will export that as a code so this is one of the solutions that we saw in the example one where there is one process that is running in the mechanism and then we edit the touch points can we auto reduce the touch points that is the whole purpose of this example that is he need it here now and he's exporting that as some kind of a code so the next thing is let's say we see another example and then I will close possibly so in this example we see so like both there so in an ideal case this is a concept of the last year so basically what happens is the ideal system that will try to better all the details from each stage of the product and try to proceed all our new ecologies like all those you can have so this is an ideal possible so if we try to see here what I mean ideal let's say these are kind of so if we want to try to solve this kind of problem then we break that into multiple areas so what is like can we get some or 25 so it's more on the side if something I'll show you why some people it's good some people you say why do you say there's nothing wrong to each of those answers so it's similar to that so so somehow you need to bring some kind of batch which you need to compare automatically tracking so and there are other things like a bit back and then some set of standards you know running your application like you know a severity and other things but then this is how you can actually also and so so if you create this prototype it's representing the past talks where you get some design so what happens is you drop your file and it tries to come up with a standard in that so that's where it gets it gets which you can actually compare so the natural when you create whatever file I will use any way you have something let's say sketch and all it's going to create it also you can come up with some kind of resources actually like you do some kind of benchmark for all those other aspects it automatically tries way how you can actually go and achieve it but so we need another there is anything that actually so what is that actually the culture so as we actually ready for where you can come up you want I mean how we can fix the culture what this kind of culture the solution lies in the open there if you see all those aspects are highlighted so what I'm feeling age of civilization that actually implements design of age of basically there is like you should go with this book and give a try to this book because what we need because the reason is what we saw this culture that is the step zero step one step two but this actually step zero so basically it's like we need to fix our culture we have to fix our culture then the next step whatever and then apply this so that is the ten thousand good overview of age of design and how we should actually do it for the coming types I hope you enjoyed this main idea can get into our chance all details you can get and randomly I don't block age of see there are multiple approaches that are existing to them let's say for example so we know that we have to we'll be sitting there we'll say ten persons sitting there what is the reason that each of those persons they are they are you see many people will be they won't be talking so there may be multiple things that is the reason behind it may be like what the right thing won't be what the diversity is you don't understand so that might be another reason so you need to create an environment so that every person even if he is not a class it should be open enough and very free to talk and there should be enough you know so that you shouldn't be afraid of discussing certain things because it's all about it so to achieve that we need to achieve good enough for that because if you see that currently it's a time when the market actually becomes business that process is changing next time we will you know mostly if a body might be run by the company then what is that the given aspects that has to you need to make sure that our organization is ready to actually clear actually that so it's all in geometry then in any way then this is the thing that actually is needed for the culture it's what it's a free now thank you guys