In T379131, we will be running an A/B test to evaluate the impact of lifting the constraint on the number of Reference Checks people can see in a single edit session.
This task involves the work of conducting a usability test of – what we're calling – the "Multi-Check (Phase 2)" experience to validate that the UX is in a good enough place for us to evaluate the impact of it.
Learning objective(s)
- How do people respond to being confronted by, potentially, a significant number of additional steps before being able to publish the new information they just finished drafting?
Decision(s) to be made
- What – if any – adjustments might we make to the Multi-Check (Phase 2) UX before beginning the A/B test of the experience?
Requirements
The usability test will be conducted on both mobile and desktop, using a scenario of an edit session where multiple paragraphs are being added. Upon clicking "Publish changes" (or tapping ">" on mobile), the user will arrive at the "Multi-Check (Phase 2)" experience where they will have multiple checks to complete.
Through this test, we seek to understand if the overall heuristics are functional for this prototype. The more conceptual learnings from having Checks and such will be evaluated through other tests once the feature is deployed.
For this test, we will be using the following prototypes on: Desktop and Mobile.
NOTE: consult with @ovasileva to ensure the research questions cover how people experience the "right-rail" Edit Check design and the Page Tools Vector (2022) introduced.