Design Intent - IA Feedback - Sitewide - Facilities, VA Medical Centers, Police Transparency

[erinrwhite]

VFS actions

• [x] 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.
• [ ] Close the ticket when all feedback has been addressed.

Thoughts/questions

• Thanks y'all for bringing this to us! You are on a tight timeline and we appreciate your work.

Feedback

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

• Should - definitions for dashboard terms: In the Summary of police activity stats dashboard section, ensure there are ways for users to get quick definitions of what certain terms mean, ideally adjacent to the dashboard cards. The FAQ is helpful, but/and its placement further down the page makes it a less ideal candidate for this information. This might be a good use case for an additional info component, but I leave that to the team.
• Should - Police vs. Policies: Differentiate links/labels clearly between Police pages and any "Policies" pages or links. It sounds silly, and there isn't much difference between the two words!
• Consider - page granularity and linking: The Summary of police activity dashboard is a bit disparate from the rest of the content on the Police landing pages, and the use case is slightly different (as the team illustrated with two links from the VAMC landing page, one under "Prepare for your visit > Security" and the other under "Spotlight"). Longer term, I could see breaking the data dashboard out onto its own page. In the short term, consider linking directly to the Summary of police activity from the VAMC homepage. This forefronts the new content and shows our commitment to compliance with the new law.
• Consider - VA-wide data: I imagine there will be a use case where users will want to see all of the VA police data for all locations, or to understand how location-specific data fits into the bigger picture. How might this initial design anticipate this use case? Would it be useful to use VA-wide data to help situate or contextualize the local data?

Thank you!

[davidmpickett]

Noting that there is now a ticket that addresses a possible solution to the Should - Police vs. Policies: feedback received here https://github.com/department-of-veterans-affairs/va.gov-cms/issues/16234