ZAP: ZAP Listserv Brainstorm Session 2 Summary

[jessicashanshanhuang]

Customization of Notifications

• clarification on when notifications should be sent -> notifications should always be sent regardless of applicant
• we should be able to differentiate who the applicant is in notification (i.e. if applicant is DCP, there should be a portion to click a link to learn more info)
• the more info link could point to general nyc dcp website

City Needs Feedback

• brought up when discussing with CN about user research survey, for the general public how would they find more information about community districts as it is uncommon for someone to know what CDs they live in
• solution: link to ZOLA for general public member to find mroe about what CDs they live in
• Stephen brought up an example to look at: City of Yes project on ZAP as an example for mockups

Defining Email Contents

• what fields do we want in the email -> the way to go is to opt for a simpler format
• suggestions: 35 words max per sentence, grade level 7-8 for readability
• will be linked to a no-reply.gov email

Where Will Sign Up Be?

• should explore both options of having it on ZAP and public website
• public website could just link to the sign up page on ZAP
• for now, sign up will live on ZAP

Include "All" Option for Subscriptions

• dependent on vendor
• can find data about how many projects expand more than one CDs that wouldn't be defined as City wide, most likely they will be under citywide

Other

• Presentation around early-mid august about design approach to get feedback
• frames and mock-ups to be ready in ~2 weeks

[jessicashanshanhuang]

update from tyler:

Hi everyone, Thank you for another productive session yesterday. Here are the next steps I have, let me know if anything is missing:

• The fellows and I will continue working on user stories. I made a new view filtered to stories in the Design Github project. We will be refining these stories and adding functional requirements to capture details not captured in the story itself. Once these stories and requirements are refined, they will be presented to stakeholders for feedback. Based on these user stories, the fellows will begin working on high fidelity renderings and/or prototypes of emails and the sign up form.

• We will hold a presentation with members of the steering committee and other stakeholders early in the week of 8/5. This will focus on presenting the email templates, prototypes, user flows, and other functional details that we want details on. It's important that we include any stakeholders that might provide feedback that we have to accommodate for an MVP.

• The fellows and Planning Support will working on preparing a survey to be shared with CBs and other external stakeholders as PS sees fit. We will not be waiting for results of this survey to begin work on the materials for the presentation to the steering committee. Due to the timing of this survey, we cannot guarantee that features identified based on the results will be included in an MVP.

• My team and I will continue meeting with vendors and other teams within ITD to research potential technical solutions. We will hold off on making any significant decisions until we get feedback following the presentation with the steering committee.