Design Intent - IA Feedback - My Education Benefits, How to Apply Veteran Edu Experience, Application Recommender Tool

[erinrwhite]

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

• Thanks for coming through collab cycle!
• I like that this tool is using the data we have on file to make a recommendation. We don't see this often enough.

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).

• [ ] Must: continue to work with CAIA on updates to page content and flow of information on the page(s), as well as placement of the check eligibility widget on this/these pages and others. Also make sure to clarify entry points. Tagging @jennymayoco who you met with before, and who was on the call with us.
• [ ] Must: remove duplicate versions of forms per @mnorthuis for a few of these forms there are two versions of the form - authenticated and unauthenticated. During the meeting y'all indicated that removing the unauthenticated forms is on the roadmap. Please make sure this stays prioritized to avoid duplication of forms and a confusing experience.
• [ ] Must: identify and plan for unhappy paths This tool is going to provide helpful information for lots of users. For users who aren't eligible, or for whom the widget errors out, what clear and actionable steps can we provide? And if the widget requires LOA3 authentication (verified accounts) please show a meaningful message for LOA1 users encouraging them to verify their accounts.
• [ ] Should: plan to show users the status of submitted forms If a user recently completed one of these education forms, can they be shown the status of that submission in this widget, or a link to check status? How might we support folks who have completed a form already?

Governance team actions

• [x] Format feedback as individual tasks (check boxes)
• [ ] 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

[erinrwhite]

Couldn't assign you, @alexander-ferzola, but tagging you here in a comment!