Roushan Kumar

Oh, well, I started my, uh, design journey journey in 2017 with Avantika University, and I did masters of communication design where I learned the UX design. Since then, I have been working in field. I mean to say I started in 2019, and there I joined couple of internships to gain my experience. And then I, uh, recently, I was working with AML RightSource where, uh, my role was to conduct the usability testing and doing the troubleshoot of UX and providing the solution related to it.

Okay. So for this case, I believe there was 1 onboarding page where it had, uh, multiple fields. And when I did the user research, then I find out, like, those fields are not really necessary, and not all the users fill those all fields. In fact, some of the users also complain, like, these fields are very long and the form is too big. Nobody feels means at the end, I found out, like, nobody feels all the fields. So we decided to remove some of the fields that were not necessary. Apart from this, we also introduced a kind of setting for a per user, Like, they can go to the setting and hide some of the those fields for their user. Like, user will not have to suffer with so many fields. Apart from that, I realized when user makes a mistake while filling the form, they, uh, means that platform didn't use to display where user has committed a mistake. And, uh, the field was kind of messy in itself because when we start typing something, then the field name disappears because the what what the field name was, whatever the field name was, it was written inside the field box. So, yes, I provided, uh, some sorts of solution for it. 1st, I did the research for it, reduce the form size, the field, uh, the number of fields so that the form size could be reduced and then I introduced the how we can prevent the error from happening. Means I started using the asterisk marks next to the field which was comp compulsory because some of the user completes the form without knowing which field should be filled completely. And at the end, they use they end up making mistakes, like, they are not they were not aware, like, oh, this field was supposed to be filled because the asterisk marks that was there, either it was in gray or it was not, uh, completely, uh, available there. So I introduced, uh, this thing over there. And the other thing, even if some user has made some sort of mistake, then it used to show on the top, uh, like the alert. Uh, like, yes, you have made some sorts of mistake, but it didn't tell me exactly where. So I introduced, like, if user makes a mistake, then, uh, the UI should scroll to that particular area where user has committed a mistake, and that thing should be highlighted entirely so that user can know here they have made a mistake.

Yes. This is a a kind of a real life question. It it always happens as I talked about, uh, the situation of a field in my last question. So what happened there, uh, it was a kind of technique, not a technical constraint. In our organization, they said, like, they can't they don't have the front end developer right now. So they said, like, please reduce some of the work that the front end developer that needs a front end developer. We may have them later, but for now, let's, uh, reduce, uh, those kind of work. So, basically, what I did, I reduced I didn't change the, uh, field style, but I said them at least if we can align those all fields so that it looks better. Apart from that, they also disagreed for having the setting option because they said, uh, like, it it it required a lot of work. Absolutely. And, uh, they agreed on having the, uh, kind of page to scroll at that particular place where they have made a mistake. And they also could not agree on the fields of having like, if somebody starts writing, then the placeholder So scroll to the top of that field section, and they agreed to it. So I redesigned. I actually didn't redesign. I removed some of the elements from there, and I mentioned this all the stuff in the acceptance criteria so that it doesn't, uh, uh, make the developers more confused.

Yes. It always happens. Like, we have to present our UI, UX ideas to our stakeholder, maybe be it the program manager or the developers. And, uh, what happens here, like, we should should not be presenting our the entire the core stuff that we know, but we should, uh, kind of design the, uh, uh, kind of those all screens or those all problem statement or the findings that uh, we have done in UI UX concept in a meaningful way so that they can understand. Like, suppose if it's a program manager, then they doesn't need to understand that those all the details of every pixels and reason behind taking the color theory, deciding the typography, and the resulting, what the program manager may need to know, like, uh, what value it will bring to the company and how much time it might take to conduct it, And we can also show the research behind those things, why do we want, and we can show upfront. Like, if we make such changes or if we design something like this, then it will have this much of benefit with a proper research. And let's say if we are presenting the same, uh, concept to a developer, then it should, uh, we should not provide the research thing and all thing what the matter, like, they just need to see the elements in place, everything, other is it everything in a day, like, what is the size of fonts or the spacing between them on the layout and those are all things.

Those videos were creating with that interface.

Yeah. It always happens. We have the conflict regarding our feedbacks from different stakeholders. So I do take them very positively. I note it down and analyze it, like, what the feedback is and come up with the my solution or the kind of my my thought process for which feedback we should be moving on or if we can have a new ID over there.

Let's see. It it happens, like, validating, uh, kind of the design idea. It might not be always suitable for the business requirement. It might go above the timeline. It might go above the budget. So as far as my experience, I just consult with the product manager or the program manager regarding my idea and my designs. And I asked them, like, with which design we should, uh, continue because in that situation, I usually create, uh, 2 to 3 options. Means it's I should be always prepared with those those options so that we can move forward with at least 1 idea because uh, not all the ideas are worth taking forward.

Yes. How do you ensure your designs are accessible to all users? Yep. The best way to do some sorts of testing and, of course, it also needs some sorts of experience. But above all, what I believe, uh, first, we should, uh, like, if there is any product, it can be accessible to all. But if we can define our user who are our main target users, and on the top of it, we can build it should be accessible to some other users also. And we can test with it, and we can do the mind mapping or do the brainstorming for the different constraints or how the different user might be using it, might be feeling about that product. We can map it out. We can draw the all the scenarios for a different user or at the end, we can do test do the testing with those kind of users. But before, we, um, we will have to define who are who comes under the all users so that we can test with those kind of persona.

Okay. If I am given any of a product which is a kind of feature rich and ensuring the minimal cognitive load. So what I'll be doing, I'll be defining the features, what are the things we have, and we'll be doing the brainstorming with the those all feature, how we can display or we can make it easily accessible to the user. And I will, uh, make sure, like, it should not be kind of cluttered with too many information, too many images, or too many icons, or using something different, or the kind of if we use something different at this given scenario, then what it will happen, it will make our user confused. And since it is a feature rich means it will already have so many elements for the user. And once I'll be, uh, done with the brainstorming with those all feature, I'll be doing testing on a paper mostly, or I'll conduct a user interview regarding those all feature, what our targeted user think about those all thing, and, uh, I will ask them, uh, what do they understand from those all, uh, the kind of listed, uh, feature or kind of, uh, those all feature things. And, yes, I will try to know their perspective. So once I'll be completely sure, like, this is the these are the features that we are going to introduce there in the app. And then I will create a LouFi kind of prototype. Maybe it's not, uh, the LouFi exactly. It should be just sketches on the paper, and I'll be just, uh, reaching some random, uh, kind of those targeted, uh, users to test those all things if it makes sense to them. And, yes, by doing this, I am 100% sure it will be a minimal cognitive load on the user and ensuring all the feature it has.

Yes. I have done 1AB testing. I don't recall exactly, uh, but I believe it was related to search because what happens, uh, when we have something on the means, uh, on our platform, we had a search field which was quite not working the way it should work. And I did some user testing on it. Then I come up with solution, and, of course, it had the 2 solution. But I was not sure to which thing was good, so I did the a b testing. Either I should go with the first solution or the second solution. So, actually, it's been old. I don't remember exactly what I did there. I don't remember.

Yes. This is a kind of good approach for doing any design revision. Actually, I have not got a chance to do such thing, but I believe if I'm working on some of the thing and I got analytics regarding some of the feedback into the or kind of any product. So how I will design, I will, uh, kind of revisions, uh, revision my designs. Uh, let's say if it's, uh, let's take the previous examples only if it is the onboarding form. And from the analytics perspective, I realize our users are not filling some particular fields or users are not uploading any document. So I will be a kind of redesigning or kind of, uh, revising by their design to reduce the cognitive load, and, uh, it will, uh, make the onboarding more minimalistic also.