Thippana MOTHILAL SAINATH REDDY

Okay. Yeah. Sure. Uh, Hi. Uh, Myself, I'm. Uh, I have 6 years experience completely into UX and UI designing. I worked on, uh, 40 plus projects in different platforms like mobile, desktop, web, and, uh, custom devices, uh, screens. Also, I have experience on, uh, b to b, b to c markets. So, also, I have experience on, uh, design tools like Figma, uh, Adobe XD, Sketch, and InVision. Coming to my roles and responsibilities, um, I closely work with, uh, product managers, uh, project managers, product owners with clients to gather requirements, understanding the business needs, and the customer needs, all this stuff. And, uh, I'm also closely work with developers. So to understand their framework, uh, so as a UX, we design it to understand, uh, which framework we are going to develop the application. So, uh, coming to my core skills, uh, I'm I'm doing application from, like, uh, all kind of UX flows, UI design, uh, flows. Also into product design, uh, I design application from scratch to end. And, uh, I'm good at doing US user research and also, uh, uh, different UX research methods like the quality to research, quantity to research, computers research. So, also, I'm very familiar with, uh, design tools like Figma. So, uh, I design, uh, basic wireframes and high fidelity, low fidelity, medium fidelity. Also, I had knowledge in designing components with proper responsive layout design. Also, I had experience in prototypes, also creating, uh, uh, experience on designer sites, like a brand sites, all the application sites, like icons, all these stuff. Also, I have experience as a team lead where I handle 6 to 7 people to train, uh, them on the design tools and also on UX flows, the UX methods, research all this stuff. And I just want to see myself in the coming, uh, 2 years as a product owner or project manager. Uh, that's my goal for short term. Yeah. Thank you so much.

Explain how you utilize Figma for creating trendy UI prototypes. Uh, coming to, uh, prototypes, I have, uh, knowledge in different tools like I told, a Figma or VXT and Sketch and Envision. So coming to, especially, Figma, uh, it's, uh, most similar to Adobe XD, and we had a lot of, uh, features compared to XD and Figma. Coming to UI prototype spot, uh, like, uh, when I do designs like a low fidelity, medium, or high fidelity, So there is a navigation, like, uh, we call the user flows. There are app flows. Task flows will be there, uh, where we can navigate from, uh, one step to another step. So how the navigation look like? How the flow look like? So, uh, once we design the, uh, flowcharts, all this stuff, even the navigation charts, so that thing, the same, we can implement in the prototype where you can give connections from, uh, dashboard to, uh, in particular a specific page. So how to come back? Uh, not only that when I give, like, a hover effects, all these stuff. Uh, so when I place my cursor, uh, like, uh, by giving some animation effects, a list of coming under a prototype. Uh, also, the navigation part is the main thing in the prototype. Like, uh, when I, uh, navigate to the pages coming forward and backward, also the flow of it will work. So this prototype feature will helps, uh, uh, to understand, uh, the flow of the app. Also, when I share these products to the clients or product owners, so we'll ask them to just go through the flow. Just let us know, uh, how easy it is, out of it is. Just gives you feedback. So, uh, this, uh, UAV prototypes, uh, demo will helps us, uh, like, to improve the difficulty in the navigation part of all these things. And it's very great feature, uh, coming to prototypes. We can show a lot of, uh, I mean, animation effects while navigating the pages to pages, some slider effects, and also the different functionalities like sliding functionality, tapping functionality, scrolling functionalities. And these features, we can, uh, I mean, show you in a very creative manner, uh, while, uh, when you use the prototype or to, uh, make conversion of those kind of designs into real prototype, how it look like, how it feel like. So, uh, it's a main feature, uh, when you have to show the navigations. So I a lot of knowledge in these prototypes. I practice every day to, uh, come up with new kind of creative ideas while doing the prototype flow, all this stuff. Yeah. That's it mostly. Thank you.

Discuss the project where you had to adapt your design due to unexpected changes and requirement. Okay. So, um, if any changes in the project, like, generally, we follow, uh, Azale and scrum methods. So this agile system will help us a lot to, I mean, uh, to monitor the application, the status of the application, whether it is going properly proper manner or not. So when there is, uh, requirements, then, generally, there are new requirements, uh, when you when you got from client side. Sometimes when as for the business requirements, when it don't work, as for the customer needs, sometimes it won't work. So we need to change the I mean, uh, some of the features, some of the functional, uh, flow in the app. So the time like, generally, we follow documentation for every, uh, UX methods while, uh, starting UX onwards, the research part, everything. So, uh, we have designs, uh, design, uh, thinking sessions. Also, uh, we have to freeze some time, like, uh, once the requirement is clear. So we we have to freeze the requirement and start the work. So, uh, generally, we follow all the UX methods, uh, to come up with a better solution for this, uh, existing problem or whatever it is. Uh, it's from the, I mean, the main problem statement. So, uh, we we'll do lot of AB testing methods, like, uh, not only one solution, like, a 3 to 4 solutions. We we go for the best solution. We do usability testing when we did in some screens, the flow. There's alternate way, uh, to show like that. But, generally, we follow we follow a lot of, uh, standards, uh, to maintain the basic standard for the application. Also, we had to follow, like, a different trendy kind of design to create video, all this stuff. And sometimes, uh, there is a change. A lot of changes will come from the client side of the product owners. So to make some changes in the, uh, application, all this stuff, like, uh, as UX designers, that time we had to understand why this change came. So, uh, how it is going to I mean, uh, is there, uh, any effect on the business needs, the customer point of view, or the client point of view? So we had to understand this stuff, uh, whenever new requirement, a new change coming to the, uh, uh, existing flow. So to understand this and, uh, check with the existing, uh, current session what you're doing, like a current application, uh, thing. So, uh, is it going to make any, uh, different effect, uh, different kind of, uh, effect is showing on the on an existing system or business? So, uh, we can take it as a light. Uh, what is the difference? Uh, how much, uh, difficult, I mean, new changes is to understand clearly and to come up with the proper, uh, knowledge, proper solution for that. So, definitely, when you're following Azale methods and we had to, uh, understand the new requirement and we had to think about time. So, uh, is the correct time to use that change and, uh, keep it in application? I'll be able to take some time. So these things, generally, uh, we, uh, discuss with a team of our higher officials, like, uh, our product managers and project managers. Also with the developers, how much time it will take if you make this change, uh, with this project. Also, deadline of some MVP product. So coming to the next deployment. So we had to control all these, uh, scenarios whenever there's some changes will come, uh, keep in mind. And we had to go for the best decision in that time as per the, I mean, uh, current thing, how it's going. Yeah. Thank you.

Okay. Describe how you, uh, validate the efficiency of your navigation design. Coming to the my, uh, navigation design, like, uh, we do, uh, have these prototypes. So, uh, it helps, like, uh, to understand the clear flow of the app. We call it any, uh, task flow like that or any, uh, user flows. So, uh, we have steps to follow for this. Uh, there is a method to, uh, complete the task to set up a goal. Like, uh, to set up a goal is, like, uh, the payment gateway. So, uh, from starting, uh, search for a product, uh, add the product to the cart and check your process, like, uh, proceed to payment, all these things. This is my goal. We have, I mean, uh, user flow for that payment flow. So, uh, the navigation design is like, uh, the product, it helps a lot, uh, in well-being the navigation designs, all these things. And, uh, there is a proper structure we follow. Like, uh, we have information architecture. So to understand the broader point of your application. So coming to any specific screen, so we have the flows in a specific screen. Also, we we have to show overall structure of the application. So as UX UX designer, not only me and any user, uh, so to understand the company structure's application, it helps them, uh, so where exactly we are. So, uh, under which page, which options will come. So, uh, these, uh, structure will helps us to define the flow, uh, the navigation flow, all these things. So we always keep in the mind, like, uh, information architecture is important when you are designing any application. Sometimes, uh, there is a chance to forget the flow, and, uh, you need to make a proper documentation. If you have the documentation, the information architecture, so you can come back and check out the, I mean, uh, whatever the current, uh, I mean, requirement, uh, the the standards, all these things. So based on that, we can simply, uh, work on the remaining, uh, future stuff. So the navigation part is very, uh, important. So for that, we maintain, uh, like I told, the information architecture and the proper documentation. Also, for each page, we have, uh, the flows, uh, user flow or the task flow, all these things. Yeah. And, like, we do we do usability testing while we, uh, design some basic screens, uh, that is mid medium fidelity, high fidelity, or low fidelity. So we give those screens to the, uh, team, the designers, designers. Uh, it depends on the company. I mean, the things. So we'll ask them to just go through the, I mean, uh, the flow. Just click on that button. Take a look at the component. Just see how it look like. So, uh, so just let us know your feedback. Are you facing any difficulty? What's your pain points? What do you like in this design? So any any changes you are you require. So, uh, these things will helps, like, when you do the testing part. Uh, so further, we need the prototype, the navigation, uh, all these things. So those inputs we've taken, and we had to work on the I mean, further improvement of the application. Yeah. Thank you.

Can you share experience with the design sprints and how you contributed? Uh, coming to design sprints, uh, like, uh, we we follow some design, uh, flow we have. So from starting, uh, requirements gathering, uh, and also, uh, define state, ideation state, empathy state. Also, we have circular method like this. Uh, it depends on the company, and, uh, generally, as UX business, we we follow every every week, every 2 weeks. The same thing is, like, uh, getting requirements, understanding, uh, the concept, and also working on some UI, uh, things, also coming back to, again, some research part. So it's like, uh, not spending a complete time on, uh, the Webex side when we are working some agile methods and the scrum, uh, plans. So, uh, as for the sprint, we have to work on the tasks. Like, uh, we have set up some task. Suppose if you are designing some, uh, admin kind of application. So for now, my task is to design, like, a dashboard only or some settings page or some menu side menu page. So I had to focus on that one. So every sprint, we have set up some goals, and with with net goals, we have to check, uh, so which task have to complete this, uh, sprint and its menu system. So, uh, just complete the menu system, first of all, and complete 1 1 by 1. So, like, that we we we plan our sprint. Uh, in every sprint, we follow the same method like I told. Doing a research part and design the screens, making testing, if there is an improvement in the testing, but again, going back. So, like, there, we can, uh, one day, we finally freeze the requirement, uh, with all the designs. So that is the thing. Like, uh, we have to start the development process. We share we can share those designs to the developers. So they started working on that development side. And, uh, coming to sprints, my experience, uh, like, uh, the team collaboration is very important. So while you doing some now nowadays, while doing this remote work, so we have to collaborate very, uh, closely with the developers, also with project managers, product managers to understand the requirements very clearly. So and to, uh, freeze the final, uh, solution for that. So, uh, we need to keep on, uh, um, asking the product managers and, uh, clean the status in the sprint meeting. So, uh, as of now, uh, for now, this is the solution what we provided. So this is the final one. Are you like it or not? Are you going to provide any, I mean, input? So are we going to freeze the requirement? We can start work on some other things. So many developers is going to work on the, uh, completed task like that. Yeah. The sprints, uh, are very helpful for us because, uh, to, uh, maintain proper time to, uh, complete the application within deadline. So definitely, we are going to follow the design sprints. So we have a lot of, uh, methods we follow while doing design sprints. So there is a lot of UX methods, the research methods, and the UI side, a lot of, uh, UI principle things to, uh, standard standardize the to to make the proper application working functionally while doing the, uh, design sprints. Yeah. Thank you. And, uh, coming to the my contribution mostly, uh, we had to, uh, tell them about, uh, what we did in the sprint, like, explain we explained the, uh, task, whatever it is we designed, clearly to the developers, uh, the product owners. So we had to take the feedback, and, again, we had to work on the if there's an existing, uh, new inputs like that. Otherwise, we had to freeze the requirement and had to move forward to other steps. Yeah. Thank you.

Can you describe a scenario where you significantly improved the user experience through your design updates? Improve the experience through design. Right. And coming to the user experience, uh, part, uh, if you see, uh, Norway, uh, generation trends, uh, we mostly focus on a new kind of, uh, new look of the UI. So it will use, like, any user, like, feels like a wow. It's a very trendy design. So it not like old kind of design like that. And, also, uh, we we try to mostly focus on functionality. So without distributing the main functionality, we had to provide the main, uh, main, uh, UA features to provide better user experience to the customer or end user point of view. So new new way updates mostly like, uh, we focus on, like, mostly how to improve the existing application. If it is already finalized and already, uh, using by the end users, So, uh, we we mostly focus how to improve the existing application, uh, as per the business point of view. So to end the, uh, money, uh, to improve to improve the ROI of the company. So, uh, these things, like, uh, improvement always is, like, helpful to the customers also without, uh, getting some boring to the application, adding new features. Uh, so for these things, we are keeping on doing some surveys, okay, getting feedback from the customers. So understanding, uh, the business needs and also our future plans, how to take forward uh, this application, uh, for the future generations. Are we going to add any new features to the application to make it as a mode better? Uh, so, uh, these things, generally, we do, uh, for the existing applications to, uh, provide better user experience for that. Also, mainly, we focus on the, uh, usability, uh, principles. So, uh, my favorite principle is, like, uh, visibility of systems data mostly. Like, we are not designing only for, uh, an admin, so it can be understand by any user at least a 50 to 60%. If I'm the user, if I don't have any knowledge, uh, regarding any admin kind of applications, at least if I see the screen, I can understand, like, uh, oh, okay. I'm exactly at this place. Okay. Uh, there should be some, uh, settings page. So there should be some data, like, uh, changing the settings in the admin panel, uh, going back, going to the dashboard. At least, uh, like, it's user friendly application. So these things we have to keep in mind mostly, uh, when I'm doing my, uh, feature in push to any existing application. So to make, uh, to provide better user experience, uh, for the end users. Not only the end user point of view, we had to keep in mind the business, uh, needs also. Do we need currently this kind of feature or not? If we have this feature, how it is going to helpful to the business? Also for the customer, for the end user. So we had to keep all these points in mind, and we had to, uh, come up with the, uh, solutions. And, uh, it's, uh, it's a routine process, uh, what we do in the our UX journey. Yeah. Thank you.

Coming to updates in the current design trends, generally, uh, I follow company standards, like, uh, also into design standards. So if you're if if you are using any mobile application, or it's for Android or Apple or iOS, and the desktop Windows or macOS. So we have to keep in mind, like, first of all, did we following the general, uh, standards or not? Also, do we have the disease system or not? So once we finalize and standardize all these setups, and, also, if you're working on any, uh, new updates current, uh, coming to design trends, Like, uh, I mean, if you see, uh, there is a lot of trends, but without avoiding the I mean, functionality, without violating the functionality, we have to, uh, provide the feature, uh, and also we have to think about, like I told, uh, in in my in my previous questions, like, uh, so, uh, we had to focus on business point of view, not only on customer point of view. How it is going to benefit to the company, uh, if I'm adding new, uh, trends to the like that. So to keep on improving my knowledge, generally, I attended mostly, uh, a lot of workshop in the link LinkedIn. I'm doing, like, a lot of brainstorming sessions with the teams and also checking up the what is a new of, uh, application in the market, how it is going on. Uh, I follow mostly, uh, Nielsen Norman Group, like, to get out of knowledge, to reading some articles. Uh, I read a lot of books. Uh, design of everyday things is my favorite book. Uh, so, uh, I mostly, uh, spend my time on reading and gaining some knowledge. Uh, also, working on AI tools, like how AI tools, AI features will work in the design and how it will help to the design industry, uh, as you've explained, how we can use it. Uh, so, uh, these things, I'm, uh, everyday, uh, uh, building mind, uh, skills and learning about existing, uh, new technologies, uh, and understanding, like, how it is very helpful to me, uh, especially to my career, uh, to move forward. Yeah. So mostly, uh, these workshops I attend in LinkedIn and also, uh, like I told, uh, a lot of, uh, design, uh, websites and design companies like Group. So there's a lot of, uh, UX things they'll tell us, like, current trendy teams. Uh, like, they are doing a lot of research. They have the, uh, that much of, uh, big data they have. They're doing a lot of research things. Those things. So when they connect any some seminars, uh, I I I'm always allowed to attend those seminars and gain knowledge from them. Not only that, we have a lot of, uh, companies into design and also in human psychology. So these things, like, I up to date, uh, attend those sessions and getting this knowledge and applying it to my current, uh, job roles, like, uh, and the application, what I'm designing. So and understanding, like, how it is going to helpful to my company or my application. So and understanding, like, how it is going to affect. I'm doing some research on that one if I apply this kind of, uh, new, uh, feature. So how it how this is going to affect to my company. I was discussing with a lot of, uh, stakeholders and with the product managers. So this is my idea. So what what do you think? It'll it'll take a lot of collaboration between the teams, like, gaining some knowledge and understanding, uh, the current process, how it is going on these things. Thank you.

How do you approach responsive design for different device screens? Okay. Coming to responsive design, uh, like I told, I worked on different platforms and, like, mobile, uh, web application, desktop application, and tabs also. And also on custom devices. So while designing, we have to keep in mind, uh, for which, uh, device we are designing, like, uh, for which platform. Uh, if it is a mobile application. And, also, it is for, uh, Android or iOS. We had to keep in mind all these things. So based on that, we had to, uh, focus on standards. For Android, what's the standard we had to follow? So we designed mostly like a minimal screen, uh, design first because if you see now in our generation, there is a different type of screen sizes, mobile screen sizes. If it is in for larger screens, so, uh, I need to make proper documentation. Like, uh, if I if I can see the minimal screen, how it look like? What's icon size? What's the menus main menu bar size? So these things we had to, uh, make a documentation. So for that, uh, we had to keep in mind, like, the grid system. Also, when you're working for a multi plat multiplatforms like web and mobile and tab, we had to focus on the responsiveness of the application, and, also, we had to focus on which grid method we are following. So I have some knowledge on development side, like React Native, so React, JS. I understand some of the concepts, uh, like, uh, when you want to create a proper, uh, response UI. So we have some standard methods in the UA, and, also, I learned a lot of from developers, uh, when I work closely with them, and I do some of my research. So when creating a responsibilities in what methods we have to follow, which grid system we have to follow. And, also, there is some, uh, component based kind of, uh, system where I learned from React JS. So this helps to any, uh, developer when I design something, like, uh, when when I shared my designs to developers, he can easily understand. Oh, okay. This is the system he's following. Uh, this compound, uh, sizes look like this. He designed like that. So when you click on any component, it will, uh, when you use the tools like Figma or the VXT, it will show the code, the structure, everything. So those code structure, we have to, uh, keep in mind, whether it is properly created or not. So while sharing any asset, uh, is a developer is going to finish any issue. So those things we have to pre check, uh, while designing, and I maintain proper assets thing, proper steps to, uh, design my screens, uh, or mock ups. And, mostly, uh, that's the main thing, like, uh, we have to keep in mind for which device we are designing, that one. And, also, uh, like, a total grid is, like, for where we follow a total column grid, sometimes a 8 column grid of a mobile. Uh, 8 column grid, 6 column grid, if we're coming to tabs, same. And, also, mostly in the mobile, we follow 4 column grid. So it depends on the, uh, what can I say, kind of application we are designing? So, uh, and and types of features are there, how many features are there in that screen. So if you take any one screen, if there is any steps are there, some like, if you take menu bar, so how many components are there? How many, uh, tab systems are in the menu bar? If it is, uh, 3 components are there so there are 5 components, 6 components are there. So how I would design that one, uh, coming to the, uh, mobile response view if I wanted in, uh, bigger screen tab? So what the screen size look like, what the button size look like. So these for these things, uh, I have a design system, so which I learned and I I, uh, on my, uh, previous experience. So those design systems, we had to, I mean, take a reference all the time, and we had to share the details to the developers when they they got any doubts. So without coming back to us and asking, hey. I forgot this one. Can you please explain? So they create a code design system. They can check it, uh, the for the solution. Oh, for this device, or this is the solution like that. Yeah. That's it mostly. Thank you.

How do we ensure design consistency across various platforms and devices? So coming to the consistency, uh, generally, we're coming to typography or color theory and the layout responsiveness. Uh, we follow the standards. Like, uh, coming to this color theory, I follow, like, uh, 60, 40, 10 rule. So, also, we had to think from a customer point of view. I mean, also from the end user point of view. So the teaming part and, uh, as for business requirements, what they're looking for, the brand colors, the brand, uh, strategy, all this stuff. So once understanding all these things, we have some, uh, idea. Like, uh, okay. I have to, uh, use the existing brand, uh, assets, our brand colors, our brand typography, all these things, or we are dealing from scratch. So if we're dealing from scratch, so we have to, uh, think about, uh, what kind of application it is. So if I take, uh, this kind of, uh, color theories, uh, how it is going to suitable to that brand. So we had to explain the, uh, benefits of that. We had we had to explain standards of that color theories and typography. And, also, uh, these things, like, keep in mind, like, uh, either, uh, we are following proper, uh, UI standards or UI standards or not. So coming to various platforms, uh, like I told, uh, we had to maintain the same consistency, uh, regarding the, uh, platform size, the, I mean, the responsiveness, and also the color that is what we are using and also the typography. Uh, we do utility testing, like, uh, once we set up the structure of the, uh, assets for the any application. So we try to follow same assets, uh, like I told the design system. So, uh, if I'm using some color, primary color, secondary color, tertiary color. So if you go to the application in any platform, if you inspect and you check the responsiveness of the system, like, it should be same everywhere. So, uh, if you keep it the proper consistency, there isn't any confusion to the any user. So he understand, okay. This this button represent this thing. This, uh, color t represent this thing. So if some warnings and will come, uh, how it look like if some pop up will come, how it look like. So these tenants, we have to set up. Uh, so, uh, in my experience, I did a lot, and we can take a lot of reference from the existing, uh, design standard, uh, sites, like, uh, we follow w 3 and also, uh, some if you do designing for Apple, we we will equal for Apple design system. And for Android, we have material design system. And only that we have a lot of design systems developed by different companies like IBM and also, uh, uh, Slack. So, uh, so this, uh, helps us a lot, uh, when you take reference and you had compared with your, uh, existing application. So, uh, so, uh, it's like a proper structure are we following or not. If you have to keep in mind, like, uh, like, this is with your confusion. Are we clearly going in a path or not? So are we following the standards or not? If you are following proper standards, so you can maintain a proper, uh, consistency throughout the application without, uh, going any, uh, other sites. So so these things, like, uh, we have to do some visible testing, like, to understand that time, uh, either correctly we follow the the standard or not. Yeah. I see mostly. Thank you.

This could be experience with the designing for multiple language support. Okay. Fine. Coming to, uh, my experience on multi language support, like, uh, based on my previous experience. Uh, So I designed I also understand, like, there's a different culture going to different regions, like, uh, if you go to other, uh, continents, other states, other countries. So you have to keep in mind, like, uh, the application design, it helps to the lot of users, uh, also with how some disabilities and also when he don't know any language, a lot of even he's blind, when he's deaf, all these things. So keep in mind, so how we're going to improve application helps to the any person, uh, physically disabled, whoever it is. So we had to come up with the new features and also what can we improve in our application. One of the thing is language. So it's very important, like, uh, if you want to take your application to the, uh, heart of the any, uh, end user. So, uh, there are many people into the world who don't know the I mean, uh, any languages. Like, there are different language. Almost many languages are there. Like, I have worked on, uh, many websites, uh, generally. Uh, so not only in some application, most couple applications. So there is a option called change language option. So if you have that feature, so, uh, easily, uh, the person who knows the local language or that nation language, he definitely choose a language and, uh, just go through the data, understand about the company, about the future. So it's for it's for, uh, or it's very helpful, uh, to navigate to from 1 page to another page to understand the application. So, uh, for this, like, we do, uh, testing part. Uh, so with the people, like, who know some languages in the company or with the client side and also with the different countries to collaborate, uh, what we do on interviews and telling about how this is our application. Here, design like this. Can you just, uh, select your language, just go through the flow? Let us know, uh, what do you feel about, uh, all these things generally, which is very simple words. There is some standard words in every language. So to understand by any person, uh, so without affecting the, I mean, uh, the consistency in the application, like the characters. So if you're using some more than 30 plus or 20 plus, 16 plus characters, uh, in a menu bar, it won't fit. So for that, we have to find a unique, uh, small, uh, names, a small word. So it should be matched within every language. If I change the language from English to German, so the character strength, uh, how much it will be. So properly fitting in the or not. So we had keeping all these things, uh, in the mind and also designed for the better UI, also for the providing a better experience to the end user. So language is very important thing. So I definitely, uh, prefer, uh, if it is in any uh, application, uh, at least we have to provide, uh, minimum languages in the application. Yeah. Thank you.