Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Design] My VA TMA: support silent failures audit (documentation & UX portion) #93548

Closed
3 tasks done
Tracked by #76500
ajakabcin opened this issue Sep 24, 2024 · 6 comments
Closed
3 tasks done
Tracked by #76500
Assignees
Labels

Comments

@ajakabcin
Copy link
Contributor

ajakabcin commented Sep 24, 2024

Background

Per OCTO priorities we've been asked to conduct an audit of our applications and endpoints to determine if we have any silent failures. Tom is taking point on completing the audit for My VA and Profile with support from Daniel to execute. There are two sections within the checklist for documentation (user flows, general documentation of error handling etc.) and user experience (how do we handle errors in the application - or otherwise). This is where Tom and Daniel need some assistance from Design.

Chante will need to present on our findings on Oct 2 so this is top priority.

Tasks

Acceptance Criteria

  • Audit (documentation and user experience portions specifically) is complete and any follow-on tasks are documented in the spreadsheet and/or captured in our backlog
@ajakabcin ajakabcin changed the title [Design] My VA TMA: support silent failures audit [Design] My VA TMA: support silent failures audit (documentation & UX portion) Sep 24, 2024
@ajakabcin ajakabcin added design my-va-dashboard authenticated-experience VA.gov authenticated experience needs-refinement Identifies tickets that need to be refined labels Sep 24, 2024
@mattmarino-adhoc
Copy link
Contributor

Will sync with engineering about documentation on Monday

@ajakabcin
Copy link
Contributor Author

@mattmarino-adhoc and @twoangstroms - re the user flows, I think it will be sufficient for this audit to say "yes we have them" and point to our user flows in our use case documentation. If they're looking for something more specific we can address post-audit presentation

@mattmarino-adhoc
Copy link
Contributor

@ajakabcin that works for me

@ajakabcin
Copy link
Contributor Author

One more note there's some guidance in the silent failures overview with considerations for creating user flows that calls out identifying points of failure. I think what we have is probably sufficient but we can create some follow up tickets to review them to more specifically call out where points of failure could occur.

cc @ACParker89 (flagging for you for Mike M)

@mattmarino-adhoc
Copy link
Contributor

@ajakabcin yep, I'm discussing with engineering still, we can try to address them at least high-level in existing user flows before Oct 2 if we have time

@ajakabcin ajakabcin removed the needs-refinement Identifies tickets that need to be refined label Oct 2, 2024
@ajakabcin
Copy link
Contributor Author

Closing as complete - documentation is noted for the audit, we'll have some follow on tasks to update user flows with possible failure points

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants