[ ] 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 bringing this through the collaboration cycle!
I'm very glad to see this codifying existing practice around (1) asking for contact information at the front of the form and (2) asking in a particular order, depending on who's completing the form on behalf of whom.
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: avoid dead ends Echoing the feedback from design, for instances where a user is selecting a path that the form can't accommodate, provide a clear next step or exit path for those users rather than removing the continue button. If possible give as much warning up front as possible to avoid folks going down this path.
[ ] Should: get feedback from CAIA IA's on this flow I'm tagging the CAIA IA's here for their feedback and their situational awareness. @kristinoletmuskat @scjwalker They are often working with teams on these flows and may have additional things to consider for this flow. They are also going to be excellent champions for this pattern, and will provide teams helpful guidance on implementation. 👍🏻
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
Next Steps for the VFS team
@platform-governance-team-members.Thoughts/questions
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).
Governance team actions