Version 2 of quarterly usage reports

[yaelberger-commits]

Description

As a (user), I need to be able to do (X) so that I can achieve (Y) outcome.

WHY are we building?
Quicksight gives us new BI capabilities
WHAT are we building?
Version 2 of quarterly usage reports that include cost of messages sent and % of failed messages that recipients never received
VALUE created by our solution
clients can see the financial impact of failed messages and the user impact and may be more motivated to clean up distribution lists or reform their data collection for contact information/preferences

Documentation and Artifacts

Good docs, figma mockups, ADRs, screenshots etc.

Acceptance Criteria

Given some context, when (X) action occurs, then (Y) outcome is achieved

• Cypress UI tests if needed.
• 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
• Update the status of related findings, insights, and hypotheses on the Research Airtable
• Once change/fix/feature is implemented, link relevant Airtable records to design artifacts (Figma)
• Does the feature change our Information Architecture? If so, update the Sitemap in En/Fr

• A11y
• Bilingualism
• Privacy considerations
• Security controls in place
• Measuring success and metrics

Related Research Airtable records

• (find stuff yourself)

QA Steps

• Tested in a realistic production scenario