## Background
This task involves the work of conducting quick usability testing with users across different experience levels to learn how they experience the new “Edit full page” button implemented in T409990 that enables switching from section editing to full-page editing on mobile, and to decide what (if any) UX adjustments the team needs to prioritize making before beginning a controlled experiment of the intervention (T409112).
=== Timeline
- ✅ ~~**Nov 25, 2025**: BM to share first draft usability test (T410614) w/ PP~~
- ✅ ~~**Nov 26, 2025**: PP to share any feedback on usability test (T410614) w/ BM~~
- **Nov 27, 2025**: BM to run first iteration of usability test (T410614)
- **Dec 1, 2025**: BM to share findings from usability test usability test (T410614) and name what (if any) aspects of UX she thinks need to be addressed before start of experiment (T409112)
### Decision(s) to be made
This test is an effort to make the following decision(s)…
- Which button copy best communicates the action and drives confident use?
- {nav Edit full page}
- {nav Previous sections} / {nav Next sections}
- {nav Switch to full page}
- Is this solution — including the button copy — sufficiently safe to ensure people do not fear losing their in-progress edits when they tap it?
- What (if any) UX adjustments are needed before broader rollout/experimentation?
### Open questions
- [ ] When prompted to edit a section beyond the one they're currently "in," do people organically/intuitively discover the button T409990 introduces?
- [ ] What do people expect will happen when they tap the button T409990 introduces?
- [ ] What (if any) confusion/hesitation/uncertainty/etc. do people experience along the path of arriving into section editing and locating the content they'd like to edit that lives outside the section the editing interface exposed by default?
-- //E.g. @bmartinezcalvo + @ppelberg are curious to know how (if at all) people perceive the skeleton the button appears atop.//
### Usability testing findings
// Add here the usability testing findings once completed //
### Acceptance criteria (or Done)
[] Implement the prototype in T409990 with 3 copy variants
[] Conduct usability test and analyze results
[] Decide on what (if any) adjustments will we make to T409990