 Good morning everyone, I hope it's very exciting, you all have been hearing about AI, deep processions and today I would like to just take you through some of the daily hurdles that we all, as designers, as product owners, we encounter on a daily basis. So the topic is about design depth and I know most of you know about it, it was coined by Ward Cunningham, he's an agile practitioner and it was initially coined around technical depth and people borrowed it for design as well. So it's good that our last session ended with a case study on depth related issues, you know. So this is again connected with depth and we'll all allow Q-cressels and Q-cressels make you feel accomplished, right? So same way, in projects we are all living in a very constrained world. So there also we allow to get some Q-cressels, there are always pressure from all the sites in terms of time, cost and scope, everything, you know, it's under full pressure. So you skip many things and what happens is you started forgetting about long-term consequences. Just like we take depth and start a business without proper thought, you'll end up in deep trouble, right? So same thing happens in design and technical world as well. So what design depth is? So design depth is all about accumulated imperfections because we skip some of the initial design decisions that we have taken, right? So it happens, you have actually wonderful design in first place and then you, as you progress in the product, you skip many things, you miss many things and then that accumulated over a period of time and it becomes a very costly affair later to fix those. So that's the design depth. So how it will impact your product? So it will start creeping in slowly. You will start a slow decline in your product metrics like, you know, new people onboarding, the conversion rate, you know, you will start seeing people edition your product quickly, uninstalling the app. As it progress, these things get noticeable and it will start, as you just ignore these design issues, this will start compounding and your products trust this actually getting affected. And then people will start that you are unprofessional, you know. So all these things, then other bad thing is, you know, some people will start doing work around bad design things that you have taken and they get used to it. When you fix it with a good design principle, they get so used to it, it's very difficult to change themselves. So it's good to, you know, so just to tell you, in the product maturity cycle from a functional product, reliable, usable, pleasurable, you know, the design depth comes in between a certain stage. It's not about totally bad design product. It's not about, you know, something you haven't really started designing. So once you have some design in place, you started missing it and then, you know, it's accumulated over time. It's about the imperfections generated after a freshly designed project. So having a well-designed product is a prerequisite for design depth issues. Okay, when actually exploring this, I just, you know, try to spot myself for some of the design issues and one of my friend's start-ups, I mean, a lot of our colleagues and friends will have start-ups. I just looked at some of them. I just noticed this is from one screen. I have seen one rounded corner buttons, a button with soft edge, button with sharp edge. It's all about different personalities, right? I mean, so I don't know, when you ask a designer to design or a developer to develop a new screen, they don't know which one to follow. You know, it's like you have taken the liberty to design the way you want. And you ignore it. It's actually live product. People are using it. And one thing I've noticed is when I tried to warn some of these product owners, they feel like, I'm getting business, things are working fine, then why should I, you know, it's actually, I'll tell you how difficult it is to tackle this later. I mean, so what I would like to say is maybe there is a big crowd who doesn't care about such things, but when you fix all this, I mean, so what I would like to say is maybe there is a big crowd who doesn't care about such things. It's okay. Sorry. So that's good. You heard again. Okay. So, you know, so, but I feel when you make your design perfect. That's good. You heard again. Oh, no. Okay. So you want me to change the mic, but I feel when you make your design perfect. It's exciting. No, no problem. It happens. Yeah. So, okay. So, you know, what I feel is they might be having some business and traction around it, but they may be missing a big audience who care about design. Right. So it's not just like this thing. And, and there is one more thing I wanted to bring your notice is like you make minimum viable products. Right. Minimum viable product doesn't care about design so much. But if you actually forget about this at a later point of time and you just carry it with the minimum viable product to a lovable product, then there's a big problem. You have to be very careful about it. I just took our typical style guide to just let you know, you know, how these small little things can make an impact. It's not very easy to, you know, take care about 27 pixel gap and this little pixels and ensure that you are programmed to, you know, take care of all these things unless you have a proper design system in place or proper component library in place because at bulk you tend to skip all this. Okay. So, okay. These are there in general, but three things which I have noticed is number one, as developers, as techies, we just ignore design, you know, the little aspects of design and we focus on our technical stuff. I think in India, we are all techies more. We don't care about the users or the end customers, but just keep in mind end customers value such things a lot. And the second thing is project constraints. Yeah, I talked about it. And the third thing, which is more important, which happened to us, that's why we said from our trenches, you know, as designers, we miss some of the trends. We miss some of the insights that we are supposed to have it in the first place. And what happens with that is, I mean, I'll talk about one of our projects where it happened to our team. And as designers, I don't know, it should never happen. Okay. So I'll talk about that project a little later, but how to manage this, you know, when you have springs, when you have, you know, things, you make sure you have some time to fix all this design issues as part of new features, along with the new features that you plan, right? So make sure you have allotted some time and prioritized which is easily fixable and have high impact. And you can ignore which is like low, you know, impactful and it's very tough once you can ignore it and do it later. Okay. So how to minimize it? One thing is as a company or as a product owner, there should be a push from the top to focus on the design. You know Airbnb and some of the portal makes the difference, right? The owner itself is a designer. The founder itself is a designer. That makes a big difference when you have a push from the top. And make sure you have a live design system in place. Otherwise, I told you about those small pixels. You don't think anyone can manage without a design system or a component library to take care of such small things. Then make sure they adhere to the process, you know, don't just do the way they like. Don't just make sure the design is part of the process. And do periodic reviews against the system. There is one more thing against the system and against the trends. That's what happened to us. I mean, it's not like, you know, I'll just, okay, so, yeah, this is one of the screen that we have delivered to our customer. The customer was a fintech customer who was into asset management portfolio from US. And it's a long project that we have been doing, right? So people have been working on this project for a while. It's around one and a half years. We build the initial design and just continuing with the design. Till one point, one of our customers' customer sent an email to him. This looks like six-year-old design, four-year-old. It's happened a while ago, okay? And do you guys can spot anything bad about this? Can you? This is a responsive version, and this is a desktop version, sorry. That's okay. Yeah, I agree. I mean, there are such things. Any more? White space. Good one. So any big issues? Yeah, the button space. Button space. You should want to write? Yeah, I agree. Okay. So I agree to all of your point. That's what even our team will think about it. Definitely when you think deeper, you will get different small steps. But just look at what we have come up after we realized. The same screens when we redesigned. Okay. Can you tell us what we have missed in the first design? Can you even tell us what we have missed in the first design? Please. There's actually a lot, right? A lot of difference. But there is a fundamental thing. There is something called conditional disclosure, progressive disclosure, which has taken up a big trend. Have you noticed our Google Groups task screen? Have you noticed Google Groups task screen? When you create a new task, it's a tiny, cute form that's coming up nowadays, right? So when you want to do more about it, like when you want to assign someone, when you want to schedule a time, there are a lot of things to click here and there that will make the form complex. So the thing is when you present the form with a lot of fields in first place, everyone takes a back seat whether to complete it or not. But when you show them the minimum stuff they have to interact with, they will start filling in. When they look around, how do I assign somebody? How do I assign a target date? Then you have things around it. You can always bring it up. So we have missed a trend because we have started this project before this trend started. And we had all the design systems in place, design principles in place, design decisions were all taken well, but unfortunately we have missed the periodic reviews to look at the trend and refactor things in our design. So that's what happened to us. That's why we said it's a lesson learned from one of our trenches and I think I finished it much earlier. Thank you. It will help you to cover up the other. So any questions? I have five minutes on my... Yeah, that's right. That's right. Yeah. In fact, I like one of our earlier design courses, which I did, how UX people should prioritize. You should put a dollar value to everything that you are putting on SNF work. So you typically do this for new features, right? I think as you rightly said, for each design issue, you should put a dollar value and importance in terms of whether this is fixed, will my product get more value? Just like your credit card, if these bills are over to you. Sorry? I think just like your credit card bills, these design debts are over to you. True, true, true. So just like any other debt, if he feels that, yeah, that's a good idea. I think I'm done, if somebody wants to take...