Service Mapping for Annual Limits Enforcement

[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? WHAT are we building? VALUE created by our solution

Documentation and Artifacts

Miro All maps Figma screens Product requirement doc

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

[yaelberger-commits]

Please add your planning poker estimate with Zenhub @amazingphilippe

[yaelberger-commits]

Reviewing solutions being explored so far this morning

[jessicalfan]

Created v1.0 of several solution user flows. Got set up in Figma, now beginning light prototyping of visual indicators of annual limits.

[amazingphilippe]

Created wireframes and happy paths. Some discussion about how to handle current and future exceptions is needed to shape the user flows. Stroy refinement?

[yaelberger-commits]

Service mapping, wireframes and screens are all underway Conversations in Slack about exceptions Bring to team discussion/Josh

[yaelberger-commits]

Bring to Story Refinement today

[jessicalfan]

Clarified two scenarios with team (hard limit, flexible limit), drafted service blueprint of the first one.

[yaelberger-commits]

Jessica and Phil will work on 1st Scenario Blueprint today and get Yael's feedback

[jessicalfan]

Explored UI options for visual indicators around annual limit across pages (with Phil). Started on 2nd Scenario Blueprint - continuing that today.

[yaelberger-commits]

@amazingphilippe did some designs/mockups for annual limits on the dashboard.

[yaelberger-commits]

Phil and Jessica looked at more service maps for SMS/Emails. Also looked at Figma mockups. Bring this to Dev Design review this morning

[yaelberger-commits]

Jessica will share 2 scenarios (hard limit and flex limit) Get input on priority features from the team

[yaelberger-commits]

Jessica and Phil to meet this morning following a design jam yesterday

[yaelberger-commits]

Yael will bring some decision points to Josh for discussion, Yael, Phil and Jessica to meet early next week following sync with Josh

[yaelberger-commits]

Phil and Jessica to sync again this morning following sync with Josh yesterday

[yaelberger-commits]

Jessica will blueprint out more detailed paths for 3 user groups Thinking about blueprinting the way we increase default limits, especially for SMS Start on Requirements doc

[yaelberger-commits]

Phil started working on the PRD. Continuing today

[yaelberger-commits]

Jessica working on Blueprinting 3 scenarios. Can share first one in Story Refinement. Then will work on how we transition existing users to a higher default limit. If time, will help Phil on PRD