Created documentation page for the 2nd round of branching feedback #205
+41
−0
Conversation
This file contains 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
| The aim was to understand whether the first part of of our recent iterations in response to the latest usability testing of branching were heading in the right direction: | ||
| * Is it easier for users to find where to do branching? | ||
| * Is it easier for users to understand how routing works? | ||
| * Is it easier for user to understand how to build 2 routes? |
There was a problem hiding this comment.
Suggested change
| * Is it easier for user to understand how to build 2 routes? | |
| * Is it easier for users to understand how to build 2 routes? |
|
|
||
| **They were not designed or planned as rigorous investigations, and therefore the findings and data should be treated with caution.** | ||
|
|
||
| The aim was to understand whether the first part of of our recent iterations in response to the latest usability testing of branching were heading in the right direction: |
There was a problem hiding this comment.
Suggested change
| The aim was to understand whether the first part of of our recent iterations in response to the latest usability testing of branching were heading in the right direction: | |
| The aim was to understand whether the first part of our recent iterations in response to the latest usability testing of branching were heading in the right direction: |
|
|
||
| Users still find it hard to understand and set the 2nd route, especially from the 'Set questions to skip' page. | ||
|
|
||
| Our understanding of the users' mental model has solidifed: users think they need to 'build' each route separately, rather than adding all questions that all form fillers will flow through until you skip them over some questions. |
There was a problem hiding this comment.
Suggested change
| Our understanding of the users' mental model has solidifed: users think they need to 'build' each route separately, rather than adding all questions that all form fillers will flow through until you skip them over some questions. | |
| Our understanding of the users’ mental model has solidified: users think they need to ‘build’ each route separately, rather than adding all questions that all form fillers will flow through until you skip them over some questions. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
PR Checklist
- (ADR, decision-record, engagement, research)
What
Added a page to document the 2nd round of user feedback for branching
How to review
Who can review
Anyone in Feature team 2.