Midpoint Review - Design Feedback - Transition Experience, tbd, V1 Transition Experience

[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

• This recently went thu DSC for experimental design. I am documenting the result of that meeting. Summary from DSC meeting:
  • Not a candidate to bring to DS for now.
  • Would prefer you stick to using the tags b/c it is something we have
  • I would not make it a candidate to bring to DS for now.
  • You can use in your application, but if we do add the warning one Jasmine shared, we would ask you to go back and update it.
  • Will use this for version 2, then for version 3, will work with Jasmine to implement colored tags.

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: Currently our guidance says that all forms must include the penalty notice component. Add the component to your review page. Your application is slightly different, if you can get legal to agree it is not necessary feel free to comment on this ticket.

Governance team actions

• Format feedback as individual tasks (check boxes)
• Assign this ticket to the VFS team member that opened the Slack request
• Add the VFS team product label
• Add the VFS team the feature label (if applicable)
• Add the touchpoint labels
• Add the practice area labels
• Add the Collaboration Cycle initiative milestone