Prototype in usability testing starting Nov 28

Background: Design research is awaiting V2 prototypes so they can do a round of usability tests. Ideally, these tests can happen before the engineers begin working on building V2, so that insights from the usability tests can inform the decisions made in V2 planning and development. Ideally, we would have a V2 prototype by early December. Note that the prototype does not need to be "perfect" or have everything in place. We fully expect that we'll continually iterate and improve upon our plans over time. However, the purpose of the prototype will be for us to learn and move the conversation forward, both in terms of our usability tests and our sharing of our plans with other stakeholders (internal teams, volunteer organizers, etc).

Update: In the interest of time, we have narrowed down the scope of the V2 prototype, so we can begin usability testing in December.

Relevant resources:

• V2 checklist
• Registration project requirements spreadsheet
• Prototypes in Figma

Acceptance Criteria:

• Create a prototype of V2 of event registration for usability tests:
  • The absolutely essential epics to test include:
    • Private registration (let's test our current implementation and see what users think in testing)
    • Support for PII (see epic T321822 for details)
    • The ability for the organizer to register as a participant (see epic T321823 for details)
    • Multiple organizer support (see T315577 for details)

Nice to haves that are not strictly required for prototype:

• Improvements to the registration configuration form (see epic T321814 for details)
• Talk page support for communication (see epic T321830 for details)
  • Note: This was already worked on as part of V1, so I don't know if there is more work to do
• Multiple event support (see epic T321811 for details)
  • Note: To simplify this, perhaps we can just allow multiple event dates/times for V2. All these events would need to have the same organizers, and we can perhaps not focus on multiple locations because that adds a lot more complexity and events with multiple locations are more likely to just seem like separate events
• A recommendation for how the participant can contact the organizer (see epic T321820)
  • Note: This may make more sense as part of the event creation project (and, if that is the case, that's okay!). We just want some design thinking/recommendation for a way that this can be done, now or in the future.
• Maximum number of participants (see epic T321818 for details)
  • This involves the organizer being able to set up a maximum number of participants per event. If the event registration exceeds the maximum, registration should be closed and the participants can be added to a waitlist. If someone leaves the registrant list, the next person in the waitlist can be automatically enrolled and they can receive a confirmation email.