YedidaZalik
commented
1 year ago Next steps if this problem is validated Possible future why: We want potential users to easily find the information they need without having to bounce between the Home page/Features page/Why GC Notify page. We want current users to be able to easily refresh their memories or find updates. Then we also won't have duplicate content that requires us to make changes in multiple places when we update. A prototype of the 3 pages combined, to assess whether we should combine them.
- [ ] Identify duplicate themes within and between these pages: some of this may be covered by Élise's 2021 Notify website content audit although we've made changes to those pages since that audit
- [ ] Identify duplicate content within and between these pages (more specific info as opposed to themes above)
- [ ] Consider alternate structure to consolidate these 3 pages into one page; if that does not seem feasible, consider consolidating the 3 pages into 2 pages
- [ ] Demo proposed redesign to Notify team for feedback and decision by Yael, Phil, Jumana
- [ ] If decide to proceed, redesign based on feedback
Publication checklist [ ] Supporting feature is released and unflagged [ ] Create or update slug [ ] Page content and slug is translated [ ] Document links to and from the page [ ] Add page slug and title to inventory [ ] If new page, add WAF rule [ ] Create new page or update existing page content [ ] Create or update translation to the page [ ] Link translations by choosing an assigned translation [ ] If new page, save as draft [ ] If existing page, update the page [ ] Post page in Slack for last minute reviews [ ] On staging: Clear the cache through GC Notify’s admin panel [ ] On staging: Check links, images and language toggle [ ] Give a heads up to the app-team channel once ready to publish [ ] On staging and production: Clear the cache through GC Notify’s admin panel [ ] Clear Cloudfront cache in GCA as needed (Andrew and Phil are GCA admins)
whabanks
yaelberger-commits
As a user, I need to be able to easily refresh my memory when using Notify. As a potential user, I need to be able to easily understand the main features and benefits of using GC Notify so that I can decide whether to choose it for my team.
WHY are we building? We think there may be a problem because we receive support tickets about content that is on the public site
Eg. The heading "Skip the procurement process" is on the Home page and also on the Why GC Notify page. The content is similar but not exactly the same, so users need to look at both pages to get all the information about skipping procurement.
WHAT are we building? Recommendations based on review and research.
VALUE created by our solution Potential for improved user experience through more effective information architecture and updates won't need to be made in multiple pages.
Documentation and Artifacts
Good docs, figma mockups, ADRs, screenshots etc. Related to #747 Élise 2021 Notify website content audit Demo questions deck: https://docs.google.com/presentation/d/1fAe_IJltMMRGbQxJxHecVcujGAcS-7Yoz71tL04ix0k/edit#slide=id.g2c08db277d4_2_23 Support: https://docs.google.com/presentation/d/1_Rp1mmrAHzpDCf1ME0sW-oKgxwb5z3RzBdg9SbPI3jI/edit#slide=id.p1
Acceptance Criteria** (Definition of done)
To be refined through discussion with the team
When a user or potential user wants basic information about Notify, then they can easily find that all in one place
[x] Adrianne, Phil and Yedida meet to refine card
[x] Yael reviews notes on card, she makes or we make her revisions, and then she gives final approval
[x] Adrianne, Phil and Yedida meet with Élise to discuss objectives, once Élise has completed her Content Inventory & Audit of all Platform websites
[x] Validate of the problem and what the problem is by looking at existing data such as the research repo and support tickets and Jeana's surveys from demos (Jeana may already have a relevant question on usefulness of the website), there was a test on the homepage a few years ago
[ ] Consider running another test potentially using interviews or card sorting. In particular look at content we consider findable but on which we still receive support questions to understand how people want to find this information. Maybe they prefer to just ask or have a demo
[ ] After validation, present recommendations to Notify team
[ ] Emphasize link to new "Register for a demo page" on Why GC Notify
[ ] Include links to CDS in updated content for these pages
[ ] We could market the reports/Dashboard as a feature of Notify better
[ ] Generate appropriate log messages so that executions of this feature can be tracked
[ ] Can misuse of this feature cause harm? If yes, create an alert
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
Privacy considerations
Security controls in place
Measuring success and metrics
QA Steps