What's your UX design process?

1- entendimento do problema 2- entender que alavancas de negócio minha solu??o precisa mover 3- investir tempo analisando os dados que eu já tenho 4- entender o que eu ainda n?o sei sobre o assunto e levantar hipóteses 5- definir os métodos de pesquisa que irei usar no processo e os perfis de usuários que preciso para entrevistas ou testes

The UX process is a straightforward one and infused UCD principles and processes in it. Research Market Research Secondary Research Primary Research Analysis Sentiment Analysis Experience Analysis Thematic Analysis Design Information Design Visual Design Interaction Design Testing Moderated usability testing Unmoderated usability testing There are different processes under each mentioned above. However, they all have to be executed by logically connecting and scientifically synthesizing, rationalizing, and reasoning with zero speculations zero assumptions zero biases, and zero loopholes. Is there anything that we do differently from the above?

Understanding the action space (either a problem or an opportunity) while focusing on who the users are, how people are behaving in that space, who is near to join the space but haven't yet (and why). This question is too wide. It depends on where the design is starting from: is it for an existing project? is it in the discovery process for something that has not yet been tackled? What is the mental model people are applying to approach this space? what are the available technologies that can help us achieving objectives?

Eu uso praticamente um diamante triplo, onde inicio com o entendimento do problema (me aprofundando até a raiz do problema quando possível), realizando pesquisas, analisando dados, passando pelas etapas de prototipagem e teste e indo até uma análise profunda pós lan?amento para colher aprendizados.

When you are understanding the problem, it’s important to consider a few things: 1. Who identified the opportunity or challenge? 2. What is the benefit to A) the user(s), B) the business, and how will it be measured? 3. Who is/are the user(s), and what challenges exist Once you have these items covered, you’re in a really good position to define the problem holistically.

When you are defining the solution, it’s important to evaluate the following: 1. What data exists about the challenge at hand? 2. Where is the data stored, and who owns it? 3. When looking at the data, what’s missing, and are there any new observations that need to be made? 4. When you look at the existing data and any new observations together, what gaps does your analysis reveal? The better your understanding of these aspects, the better your problem definition will be.

Motion design adds a layer of depth, aiding users in understanding the hierarchy of information and navigation paths. Achieving a blend of motion design, which guides interactions through animations, and functional UI animations is pivotal for a seamless user experience. This equilibrium prevents overwhelming users and significantly contributes to the interface's user-friendliness. Moreover, it's important not to overlook the aesthetic usability effect while designing the interface. Additionally, keeping in mind the insights collected during the research phase is crucial. These insights play a significant role in informing the design of the interface, ensuring that it aligns with user needs and preferences.

Design an interface that is accessible and easier to load for all. For example, not every country has the best and fastest internet out there, keep that in mind and design for versions that will ensure no matter the device used or internet speed available, the interface will load under certain speed. Also understand that countries might have different preferences for interface. Knowing your target users and design accordingly.

Usability is super important, in my opinion. No matter how much research you've done or how well you've met business and user needs, it all comes down to the regular folks who will actually use your product. If they don't like it, you've got to listen to what they're saying and make changes to fix their issues. To do this, you need to dig into the problems they're facing and find ways to make things better for them. To make this whole process work, you've got to test how usable your product is with real users. That's the key to making your product better and better.

I think this is a good starting point. But what I always find problematic about UX processes and diagrams are (1) they're mostly all the same--similar to what we have here right now, and (2) they almost always need to be a caveat that real projects and real life is a lot messier. Although, iteration is explicit on this list, for instance, in reality, there are messier smaller cycles in between and sometimes making 2 steps for ward and 1 step back (or worse, 1 step forward and 2 steps back).

The UX all about the building a product feature. So, normally it depends upon the nature of a product in some case we need to skip some specific steps but I always start with primary research, define,. empathizing and prototyping and then testing the key feature with real time user via A/B testing before sending it into final launch phase.