Background/Goal

This epic holds v1 desktop usability test feedback & recommendations (see subtasks for granular feedback in need of review/triage). This feedback can also be viewed in deck format (slides, PDF).

Goals of the usability tests

1. Deepening our understanding of the usability and adoptability of the registration enabling user flow
2. Checking the usability of various messaging options for organizers and participants, as well as filter options
3. Gather feedback on the look and feel and on copy and wording throughout the user experience

User flows tested

For this round of usability tests, @CKMIE89 and @gonyeahialam focused on:

• Event page + registration creation
• Messaging participants
• Participant contacting organizers

Methodology

• Number of tests: 5
  • 3 wikimedians with experience in organizing events including 2 who had been introduced to V0 (3 FR)
  • 2 non-wikimedians organizers (2 ENG)
  • 1 female, 4 male
  • Countries: Senegal, Cameroun, DRC, Burundi, Ghana

Main lessons learned

• Simple flow
• No major usability issues on the registration enabling and event management flow
• Creating the event page, and the look of the editor is a barrier for new organizers
• Still not obvious how participants will contact organizers
• Adding recipients to messages in not always clear to organizers using the messaging feature
• Confusion between the “Event Page” and the “Event details page”

Main questions surfaced

• Is anonymity to be considered in the same way for participating in an event and editing articles?
• Can organizers be easily contacted by participants?
• Will there be a way to differentiate between the number of “registered” participants and the number of participants that actually came?

YUX-recommended prioritization [corresponding Phabricator priority level for subtasks]

1. No usability challenges even if all usability heuristics might not be respected [lowest]
2. Look and feel issue: not a priority to resolve [low]
3. Minor usability issue: solving this is a quick win [medium]
4. Major usability issue: important to solve, should be considered a priority [high]
5. Urgent usability problem: necessary to solve before launching the product [unbreak now]