Design Intent - IA Feedback - Secure Messaging

[jimuhh]

VFS acceptance criteria

• [ ] Let Platform know when the Must feedback has been incorporated
• [ ] Leave any comments for feedback you decide not to take
• [ ] VFS team closes the ticket

Thoughts/questions

• Consistency of control use.
• Is search msgs a separate page?
• Semantics of controls: Disabled should show gray.

I realize that this project is operating within stakeholder constraints. So please feel free to cite me as an advocate for any different approaches you may want to pursue.

Feedback

• Must = the feedback must be applied
• Should = the feedback is best practice
• Consider = suggestions/enhancements

Must:

Rework Menu semantics

Avoid mixing nouns (folders, sent) with verbs (compose, search)

Should: Contact IA/Content for support in emulating successful email design patterns and content organization schemas.

Consider:

Platform directions

• Update "Issue Title"
• Link to collab cycle Request epic
• Add your feedback
• Add assignees based on collab cycle touchpoint
  • Design Intent: VFS designer, VFS PM (optional), yourself (optional)
  • Midpoint Review: VFS PM, yourself (optional)
  • Staging Review QA Only: VFS PM, yourself (optional)

[MarciMcGuire]

Thank you @jimuhh!

This looks like the feedback from our design intent on Friday, but the issue name appears to be for another team. Our project is MyHealth - Secure Messaging. Just wanted to let you know in case you needed to modify it.