Getting a service suspended story map

[amazingphilippe]

Description

Building a story map to understand all the touchpoints of getting a service suspended. Linked to #842

WHY are we building? To align on an experience for the Notify team and our clients. WHAT are we building? A story map with the team. We want to include as many people as possible. VALUE created by our solution. We'll have a guide to create the right story cards and keep the scope consistent while we build that feature.

Acceptance Criteria** (Definition of done)

• [ ] We have a journey map as a reference.

---

• [ ] 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

• [ ] Tested in a realistic production scenario

[amazingphilippe]

Hey team! Please add your planning poker estimate with Zenhub @adriannelee @jimleroyer @andrewleith @jzbahrai @sastels @sharlychan-cds @YedidaZalik @yaelberger-commits @smcmurtry

[YedidaZalik]

On Jan 11, all devs were doing a bug bash so could not attend story refinement. In case it's needed for the coming sprint, we decided to proceed with the mapping exercise, just Adrianne, Sharly and myself. By the end of the hour, we'd got part-way through Step 5 and the board was messy. We need Yael for Step 6 to make decisions about where to slice off work. I cleaned up the board for Yael's review. https://miro.com/app/board/uXjVO6TPyIs=/

[yaelberger-commits]

Meeting again today to continue story mapping with devs and decide on releases

[yaelberger-commits]

Yedida and Adrianne meeting on this today, may wait on SMS limits v2 insights before continuing

[andrewleith]

• On hold for the time being;
• research insights from SMS v2 will be added in