Work process

Different projects call for different methods and end results, naturally. Some may need to refine an existing process while others might have a whole new information architecture defined. I would adjust and choose different methods and techniques,  but I follow a general process for every project.

Note: These processes are rarely linear, hence the steps are just an indication. They could be intertwined and repeated before final delivery.


Define the requirement

At the start of any project, I would like to have general business needs, requirements for the project clearly laid out. Then things would be discussed, such as deliverables, timeline and expectations . It is of the utmost importance that I stay on the same page with the rest of the team. At this step, I will share my hypothesis for what I expect the problem might be, and estimation how long would it take for me to solve the problem.


Discover and understand

During this phase, I start to collect information (such as user survey, interviews, user data report) and explore the problem space. I will try to gather a good overview of what problems has been resolved, and what have not. Additionally, I would also look into your company’s product development history to get better idea how it has been developed.


Interpret research and synthesis insights

After the discovering phase, I will start to interpret the gathered information. The research phase allows me to define the right scope of users and pin point their needs and pain points. Insights are revealed and I set goal and metrics for this project to hit. Things are getting clearer at this stage.


Solution + ideation => iteration

This phase will be integrated through out the later part of my work process. It is filled with discussion and ideation among stakeholders, developers, and any related persons in the organization, in order to find good solutions to solve the problem.



This is the phase with something visible for team members to review. I will strive to create an interactive prototype. It could be a hi-fi Figma prototype or an interactive website. The level of details and fidelity depends on what is necessary to solve the problem and with which I can further test.


Test test and test

During this phase, I will test the prototype with users, developers and possibly with stakeholders. The purpose is to see whether the solution we have been working on is on-point, plausible for future development and eventually fit in team’s overall goal.

My design value

My front-end development experience

With my background as a front-end engineer, I speak the language of the developers I work with. As a team player, I believe it is important to understand and empathize, not only with users but also with team members and stakeholders. Knowing how to code helps me understand limitations and possibilities, also keep teammates on the same page by being the bridge between each of them.

Connect and collaborate

I believe UX designer should be the chain - connect the stakeholders, team members and users. I would like to be the one to conduct, gather and process research according to project needs; invite team players to bring out their opinions and suggestions; eventually connect dots with the team, refine insights and solve the problem. I enjoy being collaborative and collecting insights from places one might not think to look.