As a Designer
I want to understand the claims process for all claims types supported by CST
So that we can determine how to represent the different claims processes in the new accordion UI
Hypothesis or Bet
Ifwe make this changethenwe expect this to happen.
OKR
Which Objective / Key Result does this epic push forward?
Definition of done
What must be true in order for you to consider this epic complete?
Take into consideration Accessibility/QA needs as well as Product, Technical, and Design requirements.
How to configure this issue
[ ] Labeled with Team (product support, analytics-insights, operations, Console-Services, tools-fe,content-ia, service-design, vsa-*)
[ ] Labeled with Practice Area (backend, frontend, devops, design, research, product, ia, qa, analytics, contact center, research, accessibility, content)
Product Outline
Link
High Level User Story/ies
As a Designer I want to understand the claims process for all claims types supported by CST So that we can determine how to represent the different claims processes in the new accordion UI
Hypothesis or Bet
If we make this change then we expect this to happen.
OKR
Which Objective / Key Result does this epic push forward?
Definition of done
What must be true in order for you to consider this epic complete?
Take into consideration Accessibility/QA needs as well as Product, Technical, and Design requirements.
How to configure this issue
product support
,analytics-insights
,operations
,Console-Services
,tools-fe
,content-ia
,service-design
,vsa-*
)backend
,frontend
,devops
,design
,research
,product
,ia
,qa
,analytics
,contact center
,research
,accessibility
,content
)