Saloni Sinha

So I'm a UI UX designer. My relevant experience is 4 plus years, and my total experience is 7 plus years. From in my last company, my task was to design the websites and responsive design for the for those websites and be worked for the clients. The solution we we would provide to the website. So the website, uh, focused on the user, not user, but declined prospecting in business course. So it was a it was a client based company service based company, and I have worked on multiple products and website. I've also worked on worked in product based company before that, before QD 42. So I have worked on 2 products, Boom and This Matter. Yeah.

Yes. I worked, uh, with b to b SaaS company companies, um, in my previous company, which was, like, I already mentioned QD 52. I worked in that company for over 2 years, 2 years and a and 6 months. So there were several times that we, uh, would I got to work on soft products. So it was triple based, uh, web websites. And so our most mostly be focused on the problems which client would discuss with us and, um, we have we would, like, maybe, uh, maybe website, like, easy to, you know, understand for especially for the users because they have to use the website and make it easy, make it more intuitive, and they would, you know, uh, provide you solutions with the problem. So, yeah, I have worked off these SaaS products.

Yes. So I have worked on 2 product which are totally focused on, you know, huge experience. So one was Canon. Canon was the website for for the, uh, wedding photographers. So our task in the US designer was to, you know, make so easy and comfortable for the photographers. Not only for the photographers, but also for the user, couples, you know, newly couples who are would be couples who are, like, who want to who want to create a who wants to get a good photography, uh, put put a shoot in their weddings. So that was the scene for the Canon website. And the problem in Canon website was to increase the users, increase the users. And the the second website was the, uh, UNICEF Laha website. And the problem with the users was below. Is too low. They were not really educated, uh, technically also. Like, they could not use the digital products easily, especially and first focus on the women and girls of the cities and countries which are, like, not well educated, as I told you before. So the design had to be focused on the on those users. So it has to be, like, more feminine look and less scrolling, less text so that they should not read a lot, but to figure out but, uh, the solution which that company is providing, they should get the get the solution, not with the text, but with the videos and the images like this. So these 2 products are majorly focused on the, uh, UX.

Yeah. I did receive a constructive fee of criticism when I was working with Syngenta. So then I worked with Syngenta for 1 year. It was in the same QED company. So this agenda is in data we would work on the products, which to basically for agriculture, farmers, and, you know, uh, managers. Branch managers mostly who have farms huge farms. So the part which I got to design I got to design was a dashboard. So a few things which were really important with user should focus on. So it was not very prominent from the dashboard. So that was a criticism that was a criticism I got with my manager from my manager. So what I learned specifically when I was working on the dashboard that within a limited, uh, space, how much information you can put, how much of especially the important one. And especially not only important one, but to keep it on the to keep it on such a way on that, uh, pay where you users should automatically, uh, focus on that important parts of the, uh, design within that small area. So what is important? What is less important? What you can hide? That is something which I learned from that specific criticism from my manager in Syngenta.

The key key components of a design system are like there should be consistency. Right? And it should be accessible accessible to everyone, not really designers, but also developers and other stakeholders. I have worked in the design system, and it was very much, uh, you know, easily, you know, we can customize it. So but only if you can customize it. Not everybody has the right to do that. So yeah. Well, accessibility and consistency are very prominent and keep everything the naming of the layer the naming of the layer is very important because that's how, uh, developers search and, you know, they program in such a way so that naming is very important in the entire design system or style guide. And, yeah, these are the things which are very important.

So remote environment. See if so we mostly use like, if I'm taking interview remotely in conducting user research, if it is online, then we do it to they help off, you know, on phone. And sometime we use Google service, especially if it is 1 on 1, we do it on phone. Otherwise, the Zoom link or Google Meet good ways to do to conduct the user research.

Yeah. It's a good question. How do you balance user needs? So our first motive is to understand the users, and because we do not know what are they asking for. There's no way, like, we can get the business growth. So if user is satisfied and they are using your website, they are coming again and again to your website, then definitely you will gain the, uh, gain something gain the revenue, basically, because you hit the business goal. So somewhere we have to balance it. Not every user requirement is important, so we should take it as a whole and try to balance it. Because sometimes even users don't know what they want. So you have to do the tricky things like so introduce some points, some new features to the entity user groups, and then try to understand what majority is saying. And then, you know, then see if it is, you know, if it is if it is profitable or not. So in this way, I think instead of, you know, focusing on something on one thing, whether it is in school or user need, let's, uh, take let's, uh, you know, back take a step here. Each thing, you know, balance to balance each other. So that is very important. So yeah.

I focus on, like, majorly what they are looking for and try to, uh, introduce things from their point of view as well and try to focus on the profit they could they should get from this design or the solution I'm providing. So instead of, you know, putting instead of saying, like, I think like that, I think we should say, like, if you do this way, there might be more profit instead of doing that way. So just tell them the what profit they would be getting with the design process instead of forcing your point of views and your conditions to them.

This is something which I explained in in in the question. So what I learned from my manager, from my experience is when there is a complex data that we have to present in user interface, the dashboard or or mobile application because these are the things which are very concise, very small, so and very limited to space. So I think the most important information along with the action button should kept should be kept on the top so that users can focus on that without putting extra efforts. So there are some ways, like, you know, giving the there are some laws in your it's like giving the extra focus on the contrast or put it in such a way where users should not spend lots of time to click on the button or the color of the button or the text if it is very important or sometimes, you know, make it larger or put it in such a way so that it should look that this this is important. This is less important. It could be hidden. And if I want something extra, then I think I can click on that button and then read the history of the information. So that is how we show the complexity in user interface.

I think the easy way to say, if I would get a chance to redesign complex form, I would try to, first of all, focus on the typography, put try to give good white space between the content and the forms, the input box boxes, and give clear, you know, error messages, you know, to make it make it very easy and easy to understand easy to understand for the user. And, uh, try to try to provide in such try to provide the information that try to try to create the form in such a way so that users should not get confused. Instead, they would click only where they are supposed to click. So more clear big buttons and with clean clean typography, good space in between the input boxes. I think this is best digit to provide the information, uh, to provide to to create the complex form.

Waiting for a dashboard. Since dashboard is a part most of the time, it's a part of some website or some clue or concept. So majorly, if it is do good. So color scheme, mostly what I do, like, uh, and then if I'm selecting appropriate color for dashboard, so I I try to check the the thing, the kind of client, the kind of industry it is. So it's supposed to be enterprise level client. So I'll try to use the very the colors which are very very, uh, you know, uh, reliable post blue color and black, which is bold and very bold, very early color. So it depends on the industry also. Yeah. Not like something like yellow or pink or orange because it shows the mood of the of the industry.