What ,How, Why approach

In this article, I am going to tell you about a method/approach for every UXD, this is a good approach to validate the problem statement at the beginning of the Empthazing Phase

Let us consider a scenario🧐 to understand this method or approach So you are the designer who just got your first project by your seniors/client so you follow the basic approach and framework to design the solution i.e Empthaize users, Define the statement ,ideate,prototype ,test yeah that’s the basic road map to build a product

But you might have heard it much time unless and until you don’t think for the users while designing (keeping users at the center of the design we call it as user-centric design ) so you put your all efforts doing research, conducting interviews, surveys day and night just to analysis the user needs and frustration

But here’s the catch this approach helps to validate your research and definition phase productively. You can use it as a shortcut or a good way when you just have the quantitative data(qualitative/quantitate data)and you don’t have enough time to collect the qualitative data

What you can do is that just after analyzing the quantitative data

You just ask these question to yourself

why I am designing this……?

what is the need…..?

how can I do this …?

this list will be as long as your questions that satisfy your need to do the particular thing.

just ask yourself before Designing a product and have good satisfaction when you answer these questions to get a clear idea about the data you have, resources you have, the technology you have, the design you will do are they enough to give a clear justification to the above-listed questions?

Just give it a try, it will really help to work very fast in a short time duration with maximum productivity in giving a user-centric output
Because from starting you are keeping users in your mind and provide a solution

Thanks for reading