Publish iterated Analytics KPI dashboarding & analytics triaging documentation

[joanneesteban]

Product Outline

Link

High Level User Story/ies

As a VFS team member, I need to Understand and access past high level information on my product so that I can Report on previous success/failure with the product.

As a Platform Analytics team member, I need to know how to help VFS teams understand and access high level product information.

Hypothesis or Bet

If we update, iterate, & migrate high level analytics documentation to the Platform Website, then VFS teams can find, access, and understand high level data (user interactions, satisfaction, etc.) using Domo & the Platform Website to report previous success & failure on the product.

OKR

OBJECTIVE 1: Info for all common VFS needs are findable in Platform Website KR: 50% of VFS's analytics questions on Slack & Github are redirected to the Platform Website. KR: Decrease Platform Analytics time spent on support questions by 50%. KR: Increase engagement with Analytics documentation.

Definition of done

What must be true in order for you to consider this epic complete?

• [ ] Update, QA, and migrate general analytics operational documentation in Confluence
• [ ] Update, QA, and migrate general analytics VFS-facing documentation to the Platform Website

Take into consideration Accessibility/QA needs as well as Product, Technical, and Design requirements.

[johnny-jesensky-adhoc]

All issues closed as completed - closing this Epic.