Netizen Labs

Complex role management and sharing virtual sessions

Netizen Labs function

Manage your team with reports

Netizen Labs empowers anyone to conduct UX research virtually. Part of the process includes scheduling testers for  multiple sessions with different roles involved (observers, moderators, respondent).
Role
Lead UX Designer
Responsibility
End-to-End UX & UI Design Process
Collaborator
Product manager, product execs, developers, QA
Period
2025
Before

Goals

Business needs

  • Support moderated projects where multilingual is needed
  • Have scalable action feature to cater for large scale projects

User needs

  • Allow anyone to observe the session without special access
  • Support interpreter role for multilingual projects
  • Reduce workload on assigning and sharing sessions one by one for each role

Iteration & testing

Moderated interviews were done with 5 testers to validate if they understood the flow of bulk assigning and sharing schedules to different roles
After

Bulk assigning interpreters

Insights

Users understood that they can invite non-project members even without the description after seeing the “email” placeholder and the option to invite the email keyed in in the subsequent screens.

Actions

Removed the input description

Insights

Users understood that they can invite non-project members even without the description after seeing the “email” placeholder and the option to invite the email keyed in in the subsequent screens.

Actions

Removed the input description
Tested 2 interface with or without the input description
Confusion on the term “guest user”

Schedule sharing for various roles

Bulk sharing was introduced so that observers and interpreters can view the entire schedule and join from there.
Users can share one link that consist of all sessions to the relevant roles so instead of sharing multiple links of different sessions.
User flow

Interpreter and observers’ schedule screen

Once the link to the schedule is shared to relevant roles, they can access to view all schedules.

Seeing that there are no direct references for our use case, moderated testing was done to validate and refine the design for this new screen.
Iteration 1
Iteration 2

Insights

  • Users thought they are logged in when their name is in the header and feels that project name is more important
  • Session number in overview lacks clarity and users mistakenly think it’s interactive
  • Moderators are not needed as they only engage with project PIC
  • Session number in overview lacks clarity and users mistakenly think it’s interactive
  • “Join session” buttons feel redundant and unnecessary
  • The status column, which mixes buttons with rescheduling details, distracts from the primary goal of joining a session.
  • Showing rescheduling information that can frequently change adds to the confusion rather than helping.

Action

  • Replaced the interpreter’s name in header to project name as it is obvious enough who we are sharing the link to. 
The possibility of different interpreter receiving schedule irrelevant to them is small.
  • Grouped the status as separate accordions to quickly identify sessions
  • Displayed info in a list with actions helpful to interpreter and observers to distinguish info that is view only or interactable.
Final design of an interpreter’s schedule view

The results

Business needs

  • Have scalable action feature to cater for large scale projects
  • Support moderated projects where multilingual is needed

User needs

  • Reduce workload on assigning and sharing sessions one by one for each role
  • Allow anyone to observe the session without special access
  • Support interpreter role for multilingual projects