Design Intent - IA Feedback - Debt Resolution, Streamlined Waiver

[sterkenburgsara]

VFS actions

• [ ] 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

• Very impressive user flows. I cannot understate how helpful it is to see the branching logic described with user scenarios!

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:

• I really commend your huge effort here - this is a complex form and you are introducing a lot of very technically difficult branching logic. Knowing that all of these new branch paths are deviations from the current-state, I think you should submit a ticket to work with Sitewide CAIA and request content help. Specifically, I would encourage you to ask for focused help on these branch pages - clarity there will be key to ensuring successful outcomes.
• If you do any user-testing down the road, I would encourage you to include tasks that specifically measure/look at whether there is any hesitation or confusion on those branching pages.
• One last thing - a plug to connect with the Forms Digitization team (PO is @humancompanion-usds) - they have introduced a lot of really nice personalized language in step/chapter headings (example: "your information" instead of "Veteran information"), are working on some updated error messaging (with help from sitewide CAIA), and have improved plain language in alert messaging. Those things are not necessarily living in the forms library yet, but would be good to have on your radar.

[HeatherRienks]

@sterkenburgsara - thanks so much for the helpful feedback! I have created this ticket (#57719) for our next steps.

cc: @josephrlee - @mgleo @charlottecesana