As a client creating a new service, I need to understand what the preview is telling me so that I can use the preview as intended.
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 lacked some context and participants misunderstood what it was trying to tell them.
WHAT are we building?
An iteration of the service identity preview
VALUE created by our solution
We're not relying on the service identity preview to do all the work to explain what a 'service' is. But, our clients do not misunderstand what the preview is explaining to them.
When a new client who hasn't attended a demo is creating a new service, they can doublecheck their understanding of a service and the required fields in the 'service creation' flow using the preview without misunderstanding.
[ ] 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)
Description
As a client creating a new service, I need to understand what the preview is telling me so that I can use the preview as intended.
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 lacked some context and participants misunderstood what it was trying to tell them.
WHAT are we building? An iteration of the service identity preview
VALUE created by our solution We're not relying on the service identity preview to do all the work to explain what a 'service' is. But, our clients do not misunderstand what the preview is explaining to them.
Documentation and Artifacts
Brainstorming Miro Research presentation for more details
Acceptance Criteria
When a new client who hasn't attended a demo is creating a new service, they can doublecheck their understanding of a service and the required fields in the 'service creation' flow using the preview without misunderstanding.
[ ] 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
QA Steps