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

Midpoint Review - Design Feedback - Veteran Facing Forms - Patterns - Form submitter pattern #99486

Open
14 tasks
allison0034 opened this issue Dec 19, 2024 · 0 comments
Labels
collab-cycle-feedback For VSP Collaboration cycle feedback assigned to VFS collaboration-cycle For VSP Collaboration Cycle requests and improvements design midpoint-review Collaboration Cycle Midpoint Review

Comments

@allison0034
Copy link
Contributor

allison0034 commented Dec 19, 2024

Next Steps for the VFS team

How did this touchpoint go? Give feedback on the Collaboration Cycle at any time.

  • 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

  • I do like that you are linking directly to the forms needed when the user answers "no". Work with IA on that flow.

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: Work with content and make sure there is information around being an accredited rep/alternate signer before they start the form.
  • Should: The answers for "Are you currently a VA rep or..." seem a bit off. The first 2 answers start with " I'm..." and then the third answer is just "No". I had to reread the question a few times. Maybe it would be better to just list all the possible "I'm..." options. Eg. I'm not any of these or none of these apply. Also, I would add the "I'm in process of becoming and alternate signer" to the answers somewhere. Be sure to do research around this, this is just an assumption. Work with content, they may have different advice which would trump this. Make sure you think about all of the possible users flows for this. If the user clicks the link to fill out the other form and then comes back to a saved form where do they land? Do they know they need to change the answer to this question?
  • Should: The warning alert for "If you are not currently an authorized representative" is conditional and considered Immediate feedback. You can use a slim alert if you would like.

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
@allison0034 allison0034 added collab-cycle-feedback For VSP Collaboration cycle feedback assigned to VFS collaboration-cycle For VSP Collaboration Cycle requests and improvements design midpoint-review Collaboration Cycle Midpoint Review labels Dec 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
collab-cycle-feedback For VSP Collaboration cycle feedback assigned to VFS collaboration-cycle For VSP Collaboration Cycle requests and improvements design midpoint-review Collaboration Cycle Midpoint Review
Projects
None yet
Development

No branches or pull requests

1 participant