What is the best UX Process?

Question

Hi Guys,

I've been working as a Product Designer from almost about 3+ years and I've encountered to so many designers and hiring managers. The reason I'm posting this message is that in my recent interview I've been told that your process is not right or how can I put this not efficient. I've would love to know from you guys what process you follow and what is best practice. My UX Process is [Strategy>Research>Analyisis>Design>Evaluate>Launch].

Leona Lee · Accepted Answer

Hi Vikas, thanks for posting the question.

Personally there's no right or wrong process in a project, most of the time it's based on the specific request and also each of your team member's responsibilities; also I guess what the HR wants to hear is more than the keywords but the detailed process (as I'm also going through interviews at the moment so yeah,...)

I work as a freelancer at the moment and can't represent other designer's working process, but personally I would always start from:

- finding user's real pain point (so the Problem finding), the first round of researches done with googling most of the time;

- and then do the UX research (with business goal of course), including conducting the user interviews (the general questions and the contextual questions), then analyzing the data, you would see a similar pattern, in which it would help with distinguishing the target group, e.g. the most common behaviors as well as the surprising behavior/the edge case, by now you would already have a persona (so the UX research),

- then based on the specific needs of the project sometimes I also do the storyboard; (so the User storyboard)

- then based on that what I do is making the use-case diagram, not necessarily but it would help me to sort out a rough user journey flow (so the Use-case diagram)

-for this based on the feature of the product you can go further with details or start with making sketches on paper to start the UX flow (so the UX flow) - before that based on project if it's necessary I would go and meet the rest of the team or even clients to present the use-case diagram for them, so to keep everyone on the same page;

- then it's all the design process, the more detailed UX flow, low fidelity screen, high fidelity screen, interactive prototype, clean up the Sketch and make the UI Library, making deliverable assets...(so the Design & Deliverable assets)

- then during the Sprints catching up with devs, QA to see if everything is working or fixing broken UI etc etc; or it's not prioritized at the moment to keep it to the backlog; after the first release and then fixing the new issue with the second sprint; so the QA, Backlog, data collection, then you may have new user pain points..., yeah so the iteration process.

so yeah overall I guess it's the expanded version of what you have had right now (the 5 keypoint you have mentioned in your question); if it needed to be summed up it's like Problem finding - UX research - User storyboard - Usecase diagram - UX flow - Design - QA - Backlog

but still I hope this could help you a bit and yeah, let me know how did go as I'm also still learning so always good to adapt new knowledge as well as the new working process;