Background

In T406808, we conducted a first round of usability testing using a Figma prototype. This allowed us to validate early assumptions about discoverability, comprehension, and expectations around Suggestion Mode. However, due to the limitations of a Figma prototype, we were not able to fully evaluate real user interactions, system behavior, or the end-to-end flow of Suggestions and Checks.

Once we have a functional code prototype, we should run a second usability test to observe how users interact with Suggestion Mode in a realistic environment. This next round will help us validate interaction details, unexpected behaviors, and the overall usability of the feature.

Decision(s) to be made

• 1. What (if any) facet(s) of the Suggestion Mode MVP experience does the Editing Team need to prioritize addressing during and/or immediately after the conclusion of the controlled experiment (T404600)?

Research questions

Include decisions to be made

Open questions

This section contains the questions/uncertainties that surface through designing the MVP. Prior to beginning the test, we'll decide which of these questions we'll prioritize using the usability test to help us answer.

• 1. To what extent – if any – do people become confused by the similarities between the blue text highlight which T404604#11233838 specified for suggestions and the blue text highlight which is used for existing text selections and hove effects?
  • @DLynch raised this point in T404604#11233971.

Usability testing findings

Acceptance criteria (or done)

• Implement a coded prototype
• Conduct usability test with newcomers and analyze results
• Decide on what (if any) adjustments will need to be made in Suggestion Mode