Aditi Narvekar

Hello. I've done my graduation in a bachelor's degree in designing. Currently, I am not working, but I have done my job in GlobalLogic MNC as a usability and design analyst. After my two years of experience, I have done one year of experience in Bombay Design Center as a product designer. So, overall, I have a total of 3.8 years of experience in a project, but including my internships and some of the 2 to 3 months internships, it's total 4 years of experience I have in UI UX designing. So, yeah, this is the whole overall background. Thank you.

In a data form, I have used it in user research where I have conducted some user interviews and stakeholder interviews, which have provided valuable data and insights about the users, helping with design decisions. Additionally, when we conduct testing in UI UX Designing, after developing a screen, we can gather data from Google Analytics, which allows us to see, like, how many users are using the website or identifying problems users are facing. This data helps us make informed decisions accordingly.

First of all, the first step of taking a user, like, conducting user research is, you need to understand what the product is if you are redesigning the product or it's a completely new thing from a client. So first, we need to see how to identify the target users. How are we going to interview the users, some stakeholders, or some business persons about it? So when we start with this, we get an idea about the product, and we also get an idea of what users want in this product, so we can move forward and edit our product accordingly.

So, yeah. Definitely, there are some conflicting feedbacks happening from different stakeholders. But we need to understand their point of view also and what our design needs also. So there has to be some middle solution always, and we just need to find it and research about it. Once we get the middle solution, we can explain again to the stakeholders that this can also happen and this can also make the website look better, and also, the user supports this according to the user's interview, and giving them a scenario for this product. If this is a good way, then everything can happen in a very nice manner.

So I stay updated on UX Design Trends and Tools. It's from reading blogs on Medium, talking to my colleagues, my senior people, and my friends in the same profession, to see what's new. This is new. Can I get to learn this? Also, for UI designers, we can get information on new trends from award-winning websites.

So, basically, my way of creating a design that can be easily implemented by the development team is, like, 1st creating the brand style, the design system for it, what the color style should be, what the typography style should be, how the button styles could be used. So this all will be consistent in the overall website. Once this design style has been created, we can hand over this to our development team, which is the style we are going to create. They can then start creating it in their development format. And once they're doing that, we'll start creating the screens where we use the same elements, so there's no disturbance for them and for us. I prefer 1st creating a design system. It's very important, and creating the components are very important to start with the design.

To all users, it is based on the product. If the product is for children, then the target users are the children. If it's an ecommerce product, then the target users are from a particular age until this age. When we get to know about this target user, first of all, we need to know about these users. If I take a category of age 25 users, how they behave or what they are mostly likely to do, the age group of 40, 40 plus, how they are likely to behave, or the age group of 60 plus. So depending on all the users, we need to see what is accessible for them. The color style, the type of typography should be not too small and not too big. It should be mostly readable for the user. The color style should be not too bright, not too dull. It should be in a perfect palette where the user also has ease on their eyes. Also, we have to see about the accessibility of WCAG 3, where someone has color blindness. So in that color blindness, if red colors, they have to see green. So how do we analyze this for color blindness people also? So these all things are very accessible for a user to use.

I have worked on a product like Kokuyo Cameo, which is an Indian brand for stationery and artworks also. So, in this brand, the main side of this product is that they mostly sell their stationeries, color palettes, brushes, geometry boxes, books, drawing books, everything. And now they have started a new thing where they are increasing the users to join their art workshops, where the artist will give them some workshops or teach them new techniques and also some art contests. So, in this way, we get to know more about the artists in the market or some of the children who are going to join the workshop. They will do the workshop in hand, so their parents will also be happy that children are doing some activity there. So, this was some of the client was introducing in the Copio family, and we had to make it up to the mark for the user to use this. And now I can tell that the art contest or art workshops or some of the new techniques on the Kokuyo Camlion page, all the users have been using and they are very familiar with it. You can also go and see it on our Kokuyo Camlion website. If you sign in, you can get regular emails also. These emailers have been designed by me. For the Camlin website, the website is very aesthetically designed. There are not many colors used or not many different styles used. A simple CTs button style, a color scheme of red and black is being used. There, we have a simple navigation bar above and also a footer where the user can easily access all types of colors which he wants to buy, mediums he wants to buy, drawing books he wants to buy, or he wants to learn some new techniques, or he needs to sign up for an art workshop, and he needs to apply for a contest. So, easily he can access all these things. And, also, he will also get regular emails about, for example, that your artwork has been selected, your artwork got this many likes, or your artwork has been commented by a person. So, this has been very detailed work done for Kokuyo Camlin, and, Kokuyo Camlin users and artists are very happy. Also, the children also use Kokuyo Camlin website because it's very easy and accessible to use.

So, internal sessions are like, basically, I've done a project for a Jordanian company where they have their food product, which they need to sell in Dubai, Jordan, or the overall Asian market. So their website name was Mezet. There was one cooperating website, and one website where they used to sell the product. Dealing with this client is, like, they think very differently. They need more creative, more playful things on their website. They need their text to be very bold and visible to users on all their banners, or their products, and everything. In localization brands, you can see, for example, the banking sector. In the banking sector, mostly, we need to use very minimal products and the same components. The phone styles will be the same. The widgets will be the same. The tags will be the same everywhere. The button style should be the same. The colors will be the same. If you're using a credit card of different types, we have to decide which credit card goes in a banking sector. There are two very different designing sectors: international and localization.

Surely, from the analytics, we have to take the feedback because they are the ones who are going to use the website. So their feedback matters for us mostly. So we go through each and every feedback from analytics or some of the ratings also. And we try to understand the reason behind it, what is this, and what was the problem. We again try to go back to our designs or website. Is there some bug coming in the website or in the development? Is the design not feasible or was the CTO not involved? We have to identify that. So I think the feedback from the analytics is very important and should be kept in mind every time after the development of the website also.

Front-end development, we are very used to connecting with the developers, and our design team. So every time I design something, I first go and talk to a developer. Okay. This is the thing, what we have designed. What is your point of view on this? Because they have to design the whole flow, and they have to see how it works. They have to fill the data also in the backend. So every time I go and talk to them, there is something new to learn from them. Okay. After this flow, this is what will come. This is missing. Okay. You need to add a form here so the user can know. So these all things are very helpful from a front-end developer because the person tells a complete flow about the website or he develops a complete flow about the website. So when he is developing, he gets to know a lot of things that are missing in between. And it's good that the person is coming and telling us, and it's good that we are taking the knowledge and making the changes in our design process or need to add some screens or need to add some pages which we missed while designing is very helpful when a front-end developer is telling us and giving us knowledge.