Collaboration Cycle Kickoff [VANotify, Email Unsubscribe VA.gov Page]

[miabecker]

Steps to complete the Collaboration Cycle Kickoff

VFS Product Manager

• [ ] Create this issue and notify the Collaboration Cycle team of this ticket in the in #vfs-platform-support (see Slack Workflow (User guide).
• [ ] Answer the questions below and attach any artifacts you have available.
• [ ] Close this ticket when kickoff is complete and Platform has provided the recommended touchpoints.

Platform

• [ ] Review the responses and comment in ticket with recommended touchpoints and practice area involvement.
• [ ] Platform: Add project to the Platform Collaboration Point Tracker.

Artifacts (if available)

Provide links or documents for the following:

• Draft of product outline We want to build a page on VA.gov that users will be directed too when they click an unsubscribe link in emails from VAnotify.

• Wireframes, mockups, or prototypes See attached

• Any other artifacts you have so far

Questions

Please refer to the guidance in Getting Started with the Collaboration Cycle for detailed information and examples for the below questions.

1. Will your work result in visible changes to the user experience?

• [X] Yes
• [ ] No

2. Is your work a new product or an iteration to an existing product?

• [ ] New
• [X] Iteration

3. If this is an iteration, please tell us what product or feature you're iterating.

Product or feature: VA.gov

4. Are you making changes to the visual design?

• [ ] Yes
• [X] No

5. Are you doing research with VA.gov users?

• [X] Yes
• [ ] No

6. Will your work involve changes to: (select all that apply)

• [ ] Tools and applications*
• [X] Static pages
• [ ] Both

For tools and applications, take into account if any static page entry points will need updates.

7. Will your work include:

• [X] New content
• [ ] Changes to existing content

8. Are you making a change to the user flow?

• [ ] Yes
• [X] No

9. Are you making a change to urls, navigation, or entry points?

• [ ] Yes
• [X] No

10. Does your product or feature have Google Analytics tracking and a KPI dashboard in Domo?

• [X] Yes
• [ ] No

11. If yes, do you need to capture any other analytics or metrics in addition to what you're currently tracking?

• [X] Yes
• [ ] No

12. Does your team have a Github label for this product?

• [ ] No.
• [X] Yes. Please specify: VANotify

13. Who is the VA business owner for this body of work?

• [ ] VHA (Veterans Health Administration)
• [ ] VBA (Veterans Benefits Administration)
• [ ] NCA (National Cemetery Administration)
• [ ] VACO (Veterans Affairs Central Office)
• [X] Other. Please specify: OCTO

Additional information

Please refer to the Platform Collaboration Cycle guidance on Platform website for more information about the Collaboration Cycle.

[shiragoodman]

@miabecker when you're done with this ticket, please notify Collab Cycle on #vfs-platform-support channel per the steps listed above. thanks!

[natashaj7]

Here are a couple of mock ups for the unsubscribe page. MVP version:

Unsubscribe with data collection:

[shiragoodman]

Hi @PM-handle. Thanks for completing this Collaboration Cycle Kickoff ticket! Based on your responses, your project is a new static content page so we are recommending the following Collaboration Cycle touchpoints:

• Design Intent
• Staging Review
• Privacy and Security Review

Post Launch:

• Full Accessibility and 508 Office Audit

Since your work impacts static pages, please reach out to Dave Conlon to review how your work may overlap with any existing work. This will help them prioritize and identify possible areas of support needed from other teams.

The following practice areas will be included throughout the Collaboration Cycle process:

• Design
• Content
• Information Architecture (IA)
• Quality Assurance (QA)
• Accessibility
• Product

We understand that scope of work and/or solutions can change as you work through your design process. If you find that your scope and/or solution changes, please reach out so that we can update and/or modify your touchpoints appropriately.

Your project has been added to the Platform Collaboration Point Tracker. When you’re ready to schedule your recommended Collaboration Cycle touchpoints, please review the guidance outlined on the Collaboration Cycle Touchpoints page.

[shiragoodman]

@rtwell @allison0034 @seanasewell looping you in here since I didn't recommend a Design Intent (since it's not needed for an iteration to a static content page). VANotify included some mockups above. Maybe you'd like to discuss in Design Office Hours?

[miabecker]

@shiragoodman can @natashaj7 and I come to the Design Office Hours? And or do you want to report back out to us. Also is it still considered a static content page if we have buttons on the page sending folks to different places?

[mnorthuis]

FYI, this is a new page, not an iteration to one, so I would recommend a design intent.

[allison0034]

@miabecker you are always welcome to come to design office hours for any informal feedback. We have them every Tuesday 2:30-3:30 pm ET. Per Mikki's comment, if this is a new page a design intent would be beneficial for the team.

[shiragoodman]

thank you @mnorthuis and @allison0034. Sorry @miabecker , based on your responses above, I had assumed this was an iteration to an existing page. If it is a new page, we would recommend you have a Design Intent. I'll update my recommendation above. Please let me know if you have any questions.

[bevnobev]

Hi @shiragoodman. Questions for you. As a part of this effort, I'm assuming my former team requested an endpoint for va.gov/notifications/unsubscribe/SID. Is that a part of this ticket or a separate ticket? Thanks in advance

[shiragoodman]

hi @bevnobev - I apologize for taking so long to reply. Endpoint requests are not part of the Collaboration Cycle. I recommend reaching out on #vfs-platform-support on Slack and tagging front end.