Thippana MOTHILAL SAINATH REDDY

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

I utilize Figma for creating trendy UI prototypes. Coming to prototypes, I have knowledge in different tools like I told, Figma, VXT, and Sketch and Envision. So, coming to Figma, it's most similar to Adobe XD, and we had a lot of features compared to XD and Figma. Coming to UI prototype spots, when I do designs like low-fidelity, medium, or high-fidelity, there's navigation, like user flows. There are app flows, task flows, which allow us to navigate from one step to another. So, how the navigation looks like, how the flow looks like? Once we design the flowcharts, all this stuff, even the navigation charts, we can implement in the prototype where you can give connections from the dashboard to a specific page. How to come back? Not only that, when I give hover effects, all these stuff. When I place my cursor, giving some animation effects, a list of coming under a prototype. Also, the navigation part is the main thing in the prototype. When I navigate to the pages coming forward and backward, also the flow of it will work. This prototype feature helps to understand the flow of the app. Also, when I share these products to the clients or product owners, we ask them to go through the flow. Just let us know how easy it is, how out of it is. Just gives you feedback. This prototype demo helps us to improve the difficulty in the navigation part of all these things. It's a great feature coming to prototypes. We can show a lot of animation effects while navigating the pages, some slider effects, and different functionalities like sliding functionality, tapping functionality, scrolling functionalities. And these features, we can show you in a very creative manner, while using the prototype or making conversion of those kind of designs into real prototypes, how it looks like, how it feels like. So, it's a main feature when you have to show the navigations. I have a lot of knowledge in these prototypes. I practice every day to come up with new kind of creative ideas while doing the prototype flow, all this stuff.

When we encountered unexpected changes and requirements in the project, we had to adapt our design. Generally, we follow Azale and scrum methods, which help us monitor the application's status and make necessary adjustments. However, sometimes business requirements don't meet customer needs, so we need to change the features and functional flow in the app. We document every UX method while starting UX research, and we have design thinking sessions. Once the requirement is clear, we freeze it and start working. We follow all UX methods to come up with a better solution for the existing problem. We conduct AB testing with multiple solutions, not just one, to find the best approach. We also do usability testing for specific screens and flows. To maintain the application's standard, we follow a set of guidelines. Additionally, we need to adhere to trendy design principles for creating videos and other content. Changes from the client side or product owners can be significant, so as UX designers, we need to understand the reason behind the change and its potential effect on business needs, customer perspectives, and client expectations. We need to assess how the change will impact the existing flow and system, and determine if it's the right time to implement the change. To make informed decisions, we discuss these changes with our team, including product managers, project managers, and developers, to determine the time required to implement the change and the impact on the project's deadline. We need to control these scenarios and make the best decision based on the current situation. In the next deployment, we'll have to consider these factors and make adjustments accordingly. We'll have to go with the best decision at that time, based on the current situation.

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

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

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

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

How do you approach responsive design for different device screens? Okay, coming to responsive design, like I told, I worked on different platforms and mobile, web application, desktop application, and tabs also. And also on custom devices. So while designing, we have to keep in mind for which device we are designing, like for which platform. If it is a mobile application, and also it is for Android or iOS, we have to keep in mind all these things. So based on that, we have to focus on standards. For Android, what's the standard we have to follow? So we designed mostly a minimal screen design first because if you see now in our generation, there is a different type of screen sizes, mobile screen sizes. If it is for larger screens, I need to make proper documentation. Like, if I can see the minimal screen, how it looks like? What's icon size? What's the menu main menu bar size? So these things we had to make a documentation. So for that, we had to keep in mind the grid system. Also, when you're working for multi-platforms like web and mobile and tab, we have to focus on the responsiveness of the application, and also we have 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, like when you want to create a proper responsive UI. So we have some standard methods in the UA, and also I learned a lot from developers when I work closely with them, and I do some research. So when creating a responsive design, in what methods we have to follow, which grid system we have to follow. And also, there is some component-based kind of system where I learned from React JS. So this helps any developer when I design something, like when I share my designs to developers, he can easily understand. Oh, okay. This is the system he's following. This compound sizes look like this. He designed like that. So when you click on any component, it will show the code, the structure, everything. So that code structure, we have to keep in mind, whether it is properly created or not. So while sharing any asset, if a developer is going to finish any issue, so those things we have to pre-check while designing, and I maintain proper assets things, proper steps to design my screens, or mockups. And mostly, that's the main thing, like we have to keep in mind for which device we are designing, that one. And also, a total grid is for where we follow a total column grid, sometimes an 8-column grid of a mobile, an 8-column grid, 6-column grid, if we're coming to tabs, same. And also, mostly in the mobile, we follow a 4-column grid. So it depends on the kind of application we are designing? So, 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 a menu bar, so how many components are there? How many tab systems are in the menu bar? If it is 3 components are there, so there are 5 components, 6 components are there. So how I would design that one, coming to the mobile responsive view if I wanted in a bigger screen tab? So what the screen size looks like, what the button size looks like. So these for these things, I have a design system, so which I learned and I on my previous experience. So those design systems, we have to take a reference all the time, and we have to share the details to the developers when 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, 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 consistency, generally, we're talking about typography or color theory and layout responsiveness. We follow standards. Like, coming to this color theory, I follow the 60-40-10 rule. So, also, we had to think from a customer's point of view and the end-user's point of view. I mean, also from the business requirements, what they're looking for, the brand colors, the brand strategy, all this stuff. So, once understanding all these things, we have some idea. Like, okay. I have to use the existing brand assets, our brand colors, our brand typography, all these things, or we are dealing from scratch. So, if we're dealing from scratch, we have to think about what kind of application it is. If I take this kind of color theories, how it is going to suit the brand. So, we had to explain the benefits of that. We had to explain the standards of that color theory and typography. And, also, these things, like, keep in mind, whether we are following proper UI standards or not. So, coming to various platforms, like I told, we had to maintain the same consistency regarding the platform size, the responsiveness, and also the color we are using and the typography. We do user testing, like, once we set up the structure of the assets for the any application. So, we try to follow the same assets, like I told, the design system. So, 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 check the responsiveness of the system, it should be the same everywhere. So, if you keep it proper consistency, there isn't any confusion to the user. So, he understands, okay. This button represents this thing. This color represents this thing. So, if some warnings and pop-ups will come, how it looks like. So, these tenets, we have to set up. In my experience, I did a lot, and we can take a lot of reference from the existing design standards, like, we follow W3 and also some, if you design for Apple, we follow the 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 Slack. So, this helps us a lot, when you take reference and compare with your existing application. So, it's like a proper structure, are we following or not? If you keep in mind, 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, you can maintain a proper consistency throughout the application without going to other sites. So, these things, like, we have to do some usability testing, like, to understand that time, whether we correctly follow the standard or not.

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