ZWIFT
Pairing Experience Update
4th January 2021 -- *updating doc 8/4/21
- UX
- Margaret Thomas
Overview
The new pairing process will automatically pair with devices and enable the user to manage all devices on a new screen; the update will continue to use the current design language. The focus of the pairing experience will be to streamline and automate device pairing while adding the ability to control device priority configurations. Currently, the pairing screen design is built for a limited number of connections. It breaks out connection information in an intuitive way.
The guiding principle for the pairing process update is to reduce options by limiting the screen to critical information to get Zwifters riding quickly with less cognitive load. We will do this by reducing hindrances to users like nice-to-haves or disabled states that don’t apply, rather by giving them needed alternatives instead. This means, reduce the number of actions needed to pair devices while offering information and settings as a utility to manage device priorities.
Goals
- Automate the pairing process.
- Centralize control and modification of device setups and profile selection
- Reduce cognitive load and learning curve required to understand the pairing screen/process. Avoid jargon and references to backend processes.
- Make adjusting the setup configuration effortless and simple regardless of the complexity and number of devices being used
- Integrate ZC download and login
Scenarios
There are five unique flows representing the overall new experience
- 1st Party, 1st Pair
- 3rd Party, 1st Pair
- Second pair
- Multiple profile sign in
- Changing sport to running
Process Phases
Phase 1, Research & Discovery
The first phase is focused on user experience, we will create wireframes to represent flows and information priorities. The Zwift internal UX designers will prepare rough wireframes for 2 paths/methods to complete the ‘1st party, 1st pair’ process. For the remaining scenarios above we are preparing key screens and states.
There will be an internal UX review including ACQONB PM to review the overall content.
The testing in this phase is for directional input to identify and eliminate extraneous information and steps as well as find actions that may not be accounted for. We will test with 5-7 participants to validate the clarity and efficiency of the updated flows. The test method is TBD, generally, participants will be asked to accomplish tasks based on the related user story tickets.
At this time we will review the revised wireframes with the HDWINT PM and ACQONB PM, architect, Dev/Eng, and related partners. The goal of this review is to evaluate the feasibility, and that requirements have been met. (if Sumo is going to do the UI, the UI designers and engineers will be included in this meeting.)
Phase 2, UX Design - Wireframing & Design
UI design will skin approved wireframes using the existing design language, in Blend, creating an interactive prototype appropriate for usability testing.
This prototype will be reviewed with the PM, partners, architect, and Dev/Eng, to evaluate the feasibility. In this review, we will work with engineers from both Zwift to outline implementation prep and process.
Phase 3, Testing & Validation
Final user test, method TBD pending consultation with UXR. We will consolidate the test outcome with UI to make any changes. (Confirm user story tasks can be completed through testing.)
At this point, final review with partners and stakeholders as part of the monthly design review including Execs.
Complete the interactive prototype, deliverable to be discussed and defined in partnership with Dev/Eng
Calendar (Pending review)
The dates below represent the week of, not the specific date except where specified. The sprints shown are projected approximations.
Phase 1 - Research & Discovery (Sprint 1: 8/4 - 8/17)
- Review the progress of the first flow concept for ‘1st party, 1st pair’
- Review ‘1st party, 1st pair’ exploration/options and key screens for scenarios 2-5.
- Prep Wireframes for testing
- Review wireframe test prototypes with HDWINT team for Explanation and feasibility Review Wireframes flows in the weekly design review (Apr 6).
- Start UX user testing process
Phase 2 - UX Design - Wireframing (Sprint 2: 8/18 - 8/31)
- Kick-off UI work. Updated wireframes handed off for visual design to UI designers
- UI progress review
- Complete the prototype with minimal interactivity, ready for testing. Review with partners and stakeholders as part of the monthly design review including Leadership.
Phase 3 - Testing & Validation (Sprint 3 9/1 - 9/14)
- Kick-off testing and review outcomes of testing. Evaluate timing needed to refine the final behaviors prototype.
- Interactive prototype complete, deliverable to be discussed and defined in partnership with Zwift Dev/Eng