ZAP: ZAP Listserv Brainstorm Session 1 Summary

[jessicashanshanhuang]

Things to note down for design from 7/17's meeting

Milestones vs Project Status

• how ZAP informs users are based in milestones but are communicated publicly through project statuses
• for the UX, notifications should have some method to take users to the project on ZAP
• content wise, notifications should reflect how project statuses are portray on ZAP
• for MVP, we will specifically focus on Filed and Public Review

Notification Speed

• discussing the notifying users recurring, weekly vs daily
• Getting more details about whether users should have the option to choose a preference, decision also involves what vendors are going to be used
• initiating user research by conducting survey, with the help of PS to workshop the survey, can pass it on to community needs which consists of the 59 CD managers
• most likely preference option is post-mvp

Email Bundling

• bundling emails by subscribed CDs

note: ~150 projects go into public review every calendar year, therefore on avg, a project goes in the public review every other week

City Wide Option

• ZAP currently has choose of up to 59 CDs, and 60th option which is city wide
• CDs options currently being the more popular choice
• making sure we are able to communicate that if a user choose city wide, they only get notified of that option

Unsubscription Flow

• mvp will be a link to unsubscribe
• option to modify will be post-mvp b/c complexity involving account mangement

Other

• three app types: DCP, other city agencies, private sector
• comms team will need a product brief for press release