Understand what a 'service' is faster

[adriannelee]

Description

As a client, I need to be able to understand that a 'service' is external-facing faster so that I can complete the 'create a service' flow with more ease.

WHY are we building? We prototyped a solution in Jan 2024 where an interactive preview helped to explain what a service was. But, the preview was not helpful enough, especially for the participants who hadn't attended a demo.

WHAT are we building? A new iteration of the 'create a service' flow

VALUE created by our solution Smoother onboarding UX and better recipient UX.

Documentation and Artifacts

Brainstorming Miro Research presentation for more details

Acceptance Criteria

A new client who hasn't attended a demo can create a service with ease and minimal questions.

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

• A11y

• Bilingualism

• Privacy considerations

• Security controls in place

• Measuring success and metrics

Related Research Airtable records

• Explanation for what a service is comes too early. Some participants read the intro screen but they still struggled with the input fields related to ‘service’ on the preview screen. When we brought them back to this screen after going through the whole prototype, they re-read “sender identity” and found this language helpful.
• The fields on the service creation screen need more clarity because the preview didn’t help them when they first landed on the preview screen (it only changes when you input something in the fields).
• “Service name” needs to fit clients’ internal processes more. We defined a service to do 2 things: the sender identity and a shared space for a team. But the second definition didn’t feel accurate to clients who had attended the demo and miscommunicated what Notify’s purpose was for clients who didn’t attend the demo.

QA Steps

• [ ] Tested in a realistic production scenario