Design Intent - Design Feedback - IBM Skillsbuild Training Program Intake Form (VA Form 22-10282)

[allison0034]

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

• Great work! Please watch the recording for all of Matt Dingee and Ryan Thurlwell's comments. Here is a link to the guide to digitalization form.

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: Matt Dingee: Remove the demographic questions. Reach out to Nancy Clarkson and work with her if you need help with getting your stakeholder on board.
• [ ] Must: Review the guidance for using the email address pattern. If the user is authenticated and the email is prefilled, you do not need to ask for the email a second time. You really do not need to do this even if they are unauthenticated as testing has shown most users copy and paste and don’t review their initial entry
• [ ] Must: Matt Dingee: Follow the relationship to Veteran pattern and move that question to the front of the form. You can work with the forms team if you have any questions.
• [ ] Should: The options for the question "What is your main area of focus?" may confuse some users. I know this is what is currently on the PDF but you may want to consider testing to see if users really understand what those options are. You could possible add definitions to help.

Governance team actions

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

[arianaadili]

• After several discussions with our team, stakeholders, Nancy Clarkson, and Matt Dingee, we have received approval to retain the demographic questions. We have collaborated with CAIA on both the disclaimer language and the placement of these questions within the form, ensuring alignment with their feedback. You will find these questions, along with the disclaimer ("stop") page, at the end of step 1 ("Your personal information").

• The application will be unauthenticated, meaning no fields will be pre-filled. The email will only be asked for once, during step 1.

• For the "Relationship to Veteran" section, it is being used in the context of "which one best describes you?" based on the form’s flow.

• The question about the "main area of focus" and its answers must stay unchanged, as advised by our stakeholders (this also appllies to adding definitions for each field). However, CAIA suggested that we add an "something not listed here" as an additional answer choice.

[arianaadili]

Upon further stakeholder feedback, we have been asked to incorporate a couple of additional options for the demographics question. We will ensure that these changes align with the format previously advised by Matt Dingee.