Design Intent - Design Feedback - mhv-secure-messaging, Filter Redesign

[allison0034]

Next Steps for the VFS team

• [ ] Assign this ticket to the team member(s) responsible for addressing feedback provided by Platform.
• [ ] Comment on this ticket:
  • If the Platform reviewer has any Thoughts/Questions that require responses.
  • When Must feedback has been incorporated. As appropriate, link to any other GitHub issues or PRs related to this feedback.
  • When Should/Consider feedback has been incorporated, or if any feedback will not be addressed. As appropriate, link to any other GitHub issues or PRs related to this feedback.
• [ ] Questions? For the most timely response, comment on Slack in your team channel tagging @platform-governance-team-members.
• [ ] Close the ticket when all feedback has been addressed.

Thoughts/questions

• This is great and I am glad you are working with other teams.
• Matt Dingee and Ryan Thurlwell were unable to attend the meeting and I would like to get there eyes on this. Matt is back in the office August 26th. @humancompanion-usds and @rtwell can you please watch the recording and provide some feedback from the team? Recording link Passcode: 7Y8VbZ*5
• Not sure if an accordion inside an accordion is a great idea.
• Experimental design ticket

Feedback

Practice areas will document their feedback on the VFS-provided artifacts following the Must, Should, and Consider Framework. Platform Governance reviewers may also provide additional notes that don’t comment on the artifacts themselves but are important for implementation (eg. engineering/coding notes).

• [ ] Consider: Consider putting all the filters in just 1 accordion. I know you said you were concerned about screen reader tabbing so work with accessibility.

Governance team actions

• [x] Format feedback as individual tasks (check boxes)
• [x] Assign this ticket to the VFS team member that opened the Slack request
• [x] Add the VFS team product label
• [x] Add the VFS team the feature label (if applicable)
• [x] Add the touchpoint labels
• [x] Add the practice area labels
• [x] Add the Collaboration Cycle initiative milestone

[rtwell]

my initial thoughts/questions:

1. Making it clear that users are only able to filter the current folder seems key. it's not super apparent in the proposed design, esp relying on "filter messages in Inbox" to communicate this. It also makes some assumptions about what messages are or are not in the inbox / users' mental model.
2. That said, what is our rationale for not going to a new page to filter? Yes, its a bit clunkier, but it seems like a) it would allow users of focus completely on the act of filtering (which can be rather nuanced) b) Makes it even less obtrusive on the Inbox page c) a link to a new page could also help make it clear which folder is being filtered e.g. “Filter messages in this folder” d) it would scale well across tools, esp since filter functionality will be different from tool to tool.
3. Did we want to consider a filter/advanced filter situation? Esp if we know most folks don’t use the additional functionality. Filtering on its own page would support this I think.
4. The filter results aren’t super clear to me (at least from what I saw in the video—which is in figma but the links in GH are sketch, which I cannot open). @erinrwhite addressed this in the video.
5. clear filters/reset filters — love that it is persistent — interested to see how users interpret that button

[underpaid1ntern]

CC: @emilytaylorux