Even though in-person UX sessions are typically ideal, sometimes budget or travel restrictions necessitate remote UX work. This article presents guidelines for remote user research, UX workshops or presentations, and collaboration.
Meetings are for sharing information; workshops are for solving a problem or reaching an actionable goal. We compare the differences in purpose, scope, length, structure, and preparation time for workshops and meetings.
Design and user research usually report to either a centralized UX team, a product team, or a hybrid of these. There are clear benefits and drawbacks to each model.
A parking lot captures unrelated questions or out-of-scope conversations during UX meetings or workshops to keep the discussion focused and maintain momentum.
A portfolio highlighting your design process and past work shows others who you are as a designer. The process of creating a UX-design portfolio allows you to reflect on your skills and achievements.
Asynchronous remote ideation allows people to contribute ideas whenever it’s convenient to do so, but synchronous sessions lead to faster results and more team building.
Remote UX work is challenging, but using digital collaboration and communication tools can mitigate some of its difficulties. Our recommendations are based on NN/g’s experience as a remote company.
By placing colored dots, participants in UX workshops, activities, or collaborative sessions individually vote on the importance of design ideas, features, usability findings, and anything else that requires prioritization.
As part of an Agile team, UX professionals should participate in all Scrum events in order to maintain open communication, influence product success, and productively contribute to the team.
User need statements, also called problem statements or point-of-view statements, are a tool for defining and aligning on the problem you are going to solve.
A portfolio of past projects can advance the career of a UX researcher. Present the right work, summarize your findings, and communicate clearly to showcase your skills.
Retrospectives help teams reflect on their process, identify strengths and areas to improve, and turn insights into actionable plans for better future work.
Like tech debt, UX debt piles up over time and, if left unaddressed, leads to compounding user problems and costly cleanup efforts. Agile teams can modify their processes to track and resolve UX debt.
Data from 257 UX professionals shows that quality UX ideas come from ideating early in the design cycle, drawing inspiration from user research, and working with a group. Many struggle with generating ideas because they lack time, managerial support, and a methodology for conducting effective ideation sessions.