The more we know about how our users are using the Editorial Workflow & Assignments features, the better equipped we are to improve the feature set.
User Story or Problem Statement
As a designer/researcher, I need to have access to consistent set of data collected over the long-term about how users are using editorial features within the CMS application.
Affected users and stakeholders
The CMS team that designs, engineers and supports editorial workflow features
Hypothesis
By collecting usage data, we will be able to:
understand user behavior patterns when using the application
understand how effectively EWA feature set supports content ops objectives
make educated decisions for feature enhancement
Assumptions
We have access to data collection via Google Analytics / Google Tag Manager
We may utilize other SaaS or custom developed software for data collection if we identify metrics that GA/GTM can not capture
Background
The more we know about how our users are using the Editorial Workflow & Assignments features, the better equipped we are to improve the feature set.
User Story or Problem Statement
As a designer/researcher, I need to have access to consistent set of data collected over the long-term about how users are using editorial features within the CMS application.
Affected users and stakeholders
Hypothesis
By collecting usage data, we will be able to:
Assumptions