'Service' is *your* identity

[adriannelee]

Description

As a new Sender, I need to be able to input the right information when I create a service so that I have the right expectation with the rest of the site and I don't have to correct information later on.

WHY are we building?

• In usability testing, even with reading the welcome screen, people don't understand that 'creating a service' is about them creating their identity.

WHAT are we building?

• Onboarding screens?
• Curating the information more for someone who is new to GC Notify

VALUE created by our solution

• Better UX, especially for people who use assistive technology
• Easier to design the rest of the experience when the basic concepts are well understood

Documentation and Artifacts

Opportunity canvas & User story map

Acceptance Criteria

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

• [ ] Design increases likelihood that new clients understand that a 'service' is their identity

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

• A11y

• Bilingualism

• Privacy considerations

• Security controls in place

• Measuring success and metrics

Related Research Airtable records

From Fable 2023 testing Hard to understand that 'Service' is your identity Unsure about creating a service. Site feels like something they have to learn in order to orient themselves Previous Participants didn't understand why they needed to name the service in both languages and what a 'service' was.

QA Steps

• [ ] Tested in a realistic production scenario

[yaelberger-commits]

Hey team! Please add your planning poker estimate with Zenhub @adriannelee @amazingphilippe @YedidaZalik

[amazingphilippe]

I just wanted to clarify my story point estimation. Here are some questions I'd like to answer. There may be more... I will add more...

• Every service is different, users have different words to explain what they want to do
• Not all users have the same technical capabilities
• How exactly do we explain how Notify works? How do people think Notify works before they start using it?
• When should we / are we displaying onboarding?
• Could we make it easy to return to onboarding?
• Could we make onboarding a self paced process?

[adriannelee]

Working on opportunity canvas and user story map here https://miro.com/app/board/uXjVO6TPyIs=/?share_link_id=514016562144

[yaelberger-commits]

To do this sprint: 1) Define terms for ourselves 2) Ideation workshop as a team Decide on next steps