Design Intent - IA Feedback - Education Data Migration, Yellow Ribbon 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!

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: organize information without using a table I agree with the feedback in the meeting that the information can be presented without a table. There is an information hierarchy that can be used to help break down the display further. I think one way to do this that @scjwalker raised during the meeting is being able to group programs by graduate/undergraduate/other. It seems like this will be the primary way that users would want this information displayed. From there, the information can be broken down by school/program. This might be accomplished using a combination of cards, accordions, search results (using filters for program type and school) or just headers and subheaders. (Looks like y'all are already working on this in your mobile mockups.)

• Should: when possible collaborate with CAIA IA's If possible keep in touch with @scjwalker from CAIA about user flow, title tags, breadcrumbs, h1, link text and other IA components for this tool.

• Should: clarify big-picture user flow The current user flows are very interface-centric rather than task-centric, which might make it difficult down the line to ensure that you're doing the thing that you'd like to do with the improvements to this tool. It might be helpful to think in terms of steps the user should take rather than links they should click. Based on the user flow you provided, it sounds like this is what the intended flow for the tool is?

  • User wants to determine what yellow ribbon benefits are available from the institution they already attend? or institution(s) they are considering applying to?
  • User finds the VA.gov education benefits pages, and this tool
  • User searches for the institution(s) they want to learn more about - or the geographic location where they know they want to study
  • The tool shows them what benefits are available at each institution
  • They can compare benefits across institutions

Governance team actions

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