Open YedidaZalik opened 2 years ago
This could fall under Growth's mandate. I'm leaning towards iceboxing it for now @YedidaZalik
Needs updating and refinement
Please add your planning poker estimate with Zenhub @YedidaZalik
@adriannelee do you think it would be possible in the future to test if the use cases we select resonate with our clients?
Yael has been drafting what these use cases might be, still in progress.
@yaelberger-commits Yep. I'll add to the research backlog
Added to this existing question. We/I marked it with "CX" previously
As a Notify user, I need to understand what the best use cases are for Notify, so that I can know if Notify is the right tool for me and my team before I invest time in onboarding and getting approvals to use it.
WHY are we building? People don’t fully understand what Notify is or what it's best used for. We’ve seen people during research and support tickets confuse it for an email service (like gmail), or try and sign up with a service that we can't support (volume, urgency, reliability) WHAT are we building? best fit use cases (based on scenarios and template categories) with accompanying marketing content to publish on the website and use in demos and conversations with clients. This can also include guidance for users on how to use template categories and can include example templates and be our MVP of exemplar templates VALUE created by our solution Users will understand the main purposes of Notify and best fit use cases, which will lead to better understanding of how to use Notify effectively and less time and effort wasted onboarding if Notify is not right for them. It could also lead to an increase in uptake as more public servants see their needs being met and the value added by using Notify.
Documentation
https://docs.google.com/document/d/1BSFLYwAUJT7dRDalmtuKlM9SoIZAkuGi-X1GQ-08XkI/edit
Acceptance Criteria** (Definition of done)
When a user completes onboarding, they will clearly understand the reason that they are using Notify.
If this user story emerged from User Research insights:
[ ] Link research insight back to hypothesis from Epic or Objective in Airtable
[ ] Once change/fix/feature is implemented, mark insight as "resolved" in Airtable
[ ] Once change/fix/feature is implements, link insight to design artifacts (Figma) in Airtable
A11y
Bilingualism
Measuring success and metrics
QA Steps