Open
Description
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
- Thanks for coming through collab cycle! Looking forward to hearing about your research at a Monday design meeting (nudge, nudge).
- I'm putting all my chips in for Ape.
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).
- Consider: on Elk flow, simplify initial condition entry: On the Elk flow, we are asking 2-3 questions about the new condition - name, [optional right/left/both], initial date. Can the date question be moved to be in the later part of the flow, in order to streamline that initial condition entry? That would make it even clearer that "we're asking you for the conditions up front, then will ask more details about each one"
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
Activity