-
Notifications
You must be signed in to change notification settings - Fork 14
Create 2026-06-24-multiple-branches-usability-testing-findings-june-2… #261
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
lorna-howes
merged 14 commits into
main
from
Multiple-branches-usability-testing-findings-June-2026
Jul 30, 2026
Merged
Changes from all commits
Commits
Show all changes
14 commits
Select commit
Hold shift + click to select a range
7d105bd
Create 2026-06-24-multiple-branches-usability-testing-findings-june-2…
lorna-howes 5ee91c1
Update research/2026-06-24-multiple-branches-usability-testing-findin…
lorna-howes 4b68826
Update research/2026-06-24-multiple-branches-usability-testing-findin…
lorna-howes b50e47b
Update research/2026-06-24-multiple-branches-usability-testing-findin…
lorna-howes 5d4a199
Update research/2026-06-24-multiple-branches-usability-testing-findin…
lorna-howes 82fa247
Update research/2026-06-24-multiple-branches-usability-testing-findin…
lorna-howes b5cb7c6
Update research/2026-06-24-multiple-branches-usability-testing-findin…
lorna-howes 34f425b
Update research/2026-06-24-multiple-branches-usability-testing-findin…
lorna-howes 7cc3ba4
Update research/2026-06-24-multiple-branches-usability-testing-findin…
lorna-howes 92490fc
Update research/2026-06-24-multiple-branches-usability-testing-findin…
lorna-howes d4a70b9
Update research/2026-06-24-multiple-branches-usability-testing-findin…
lorna-howes 7d94105
Update research/2026-06-24-multiple-branches-usability-testing-findin…
lorna-howes 8ced34a
Update research/2026-06-24-multiple-branches-usability-testing-findin…
lorna-howes 3044d39
Update 2026-06-24-multiple-branches-usability-testing-findings-june-2…
lorna-howes File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
89 changes: 89 additions & 0 deletions
89
research/2026-06-24-multiple-branches-usability-testing-findings-june-2026.md
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,89 @@ | ||
| # Multiple branches usability testing June 2026 | ||
|
|
||
| ## 2026-06-16 / Sprint 5 (Q1) | ||
|
|
||
| ## Aims | ||
| - To understand how usable the design is. | ||
| - To find out whether a longer or more complex form might present additional challenges. | ||
| - To uncover any challenges the design might present for users who have cognitive or neurodivergent conditions. | ||
|
|
||
| Can people easily: | ||
| - Add routes | ||
| - Edit routes | ||
| - Reorder questions and understand the impact | ||
| - Fix routes that have issues | ||
| - Understand what routing is in place in a form | ||
| - Navigate, use and understand a long routes page | ||
|
|
||
| ## Participants | ||
| - 8 civil servants | ||
| - Current users of GOV.UK Forms | ||
| - Intention: A range of experience of the platform and using routing | ||
| - Actual: More beginners than experienced users | ||
|
|
||
| - 4 **had** a declared a cognitive or neurodivergent condition | ||
| - 4 had **not** declared a cognitive or neurodivergent condition | ||
|
|
||
| ## Methodology | ||
| - Usability tests with form creators. | ||
| - 60 minute sessions. | ||
|
|
||
| ## Key Headlines | ||
|
|
||
| ### Adding the questions | ||
|
|
||
| - People work from a range of formats when creating their forms | ||
| - Half of people set up the question wrongly. Most commonly, they set up the list question to accept one or more options. | ||
|
|
||
| ### Finding where to add routes | ||
|
|
||
| More than half of participants struggled to find where or how to add routes. They: | ||
| - couldn’t find the ‘Edit question routes’ button | ||
| - didn't read the content on the empty routes page that said they needed to add more questions | ||
| - didn't understand why their options were not shown on the routes page (when they'd set the question up to accept more than one option) | ||
|
|
||
| When searching for how to add routes, people often went to the Edit question link. | ||
| They would usually focus on the options area of the edit question page, or go into editing the options. | ||
|
|
||
| ### Adding routes | ||
|
|
||
| Once on the Edit routes page, if the questions were set up correctly, they understood how it worked. They generally used the dropdowns to change the options quite easily. | ||
|
|
||
| However, people commented on the amount of stuff on the page making it more difficult, especially text and numbers. | ||
|
|
||
| ### The length of the form | ||
|
|
||
| Most people did not seem to find the longer form more difficult to use. | ||
|
|
||
| ### Reordering questions and editing / fixing routes | ||
|
|
||
| Those who did the task understood what they needed to do when they saw the error for the backwards route. | ||
|
|
||
| Again, the amount of numbers and text on the page made the task more difficult. | ||
|
|
||
| ### Understand what routing is in place in a form | ||
|
|
||
| Those who used the route descriptions seemed able to understand them with a bit of focus. | ||
|
|
||
| There seemed to be potentially a challenge when how the route is written in the original form is structured differently to the platform. | ||
|
|
||
| ### Using the keyboard to navigate (one participant) | ||
|
|
||
| They were the only person who seemed very nervous about making mistakes. | ||
|
|
||
| They were keen to be able to edit the routes for just one question at a time. | ||
|
lorna-howes marked this conversation as resolved.
|
||
|
|
||
| Their main limitation was scrolling the page while also using the keyboard to interact with the page. | ||
|
|
||
| ### Impact for people with neurodivergent conditions | ||
|
|
||
| Due to the interaction of other characteristics (experience level and job role), it was challenging to identify the causes of the behaviour of people with conditions. | ||
|
|
||
| In some aspects, people with conditions had a better experience and in some areas it was worse, but this was also associated with their experience level, and whether or not they were a content designer. | ||
|
|
||
| People with conditions were almost exclusively the people talking about the amount and presentation of the information on the ‘Edit question routes’ page. | ||
|
|
||
| ## Supporting Evidence | ||
| - [Report](https://docs.google.com/presentation/d/17oKU8GmFwv581oZGF-01JmcLt_LdqmLIV8RQvS7ba3c/edit?usp=drive_link) | ||
| - [Playback](https://drive.google.com/file/d/1I7C3MKqUhObp0V_t0IWFStDqlnCc6KEk/view?usp=drive_link) | ||
| - [Further documentation](https://drive.google.com/drive/folders/13U0idGiOdwr9PlnCD-oSuRk4I39ng1Qj) | ||
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.