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.
The type of workshop will dictate which tools your team should use. Ultimately, with limited time and budget, your best bet is to use a tool your team already knows how to use.
There are 7 activities that act as a foundation for every UX exercise during a workshop or collaborative team meeting. By understanding these, you can create almost any other exercise you need.
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.
With an abundance of digital workplace tools available today, organizations must carefully approach tool curation to preserve employee productivity and their workplace experience.
A parking lot captures unrelated questions or out-of-scope conversations during UX meetings or workshops to keep the discussion focused and maintain momentum.
In cognitive mapping sessions, users are asked to produce a visual representation of their mental models. This type of user interview can provide stimulus for conversation, generate insights, and act as a facilitation aid.
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.
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.
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.