Caseflow metrics instrumentation #11994
Labels
Eng: Data
Mark when data has been backfilled, or the issue has any data integrity concerns
Epic
Priority: Low
Reported issue, not a blocker. "Last in" priority for new work.
Team: Delta 🔺
Type: Metrics or Reporting
Ticket to capture allda Caseflow metrics. We have a lot of disparate tools for metrics, too, which we may want to consolidate.
Subsequent sections of this ticket will capture metrics & where they should go (if we know at this time)
Goals
My overall goal for metrics instrumentation
Goals for this ticket:
Data sources
There are 2 relevant data stores:
Depending on the metric we’re trying to report, either one could be used.
Tools
Caseflow team owns:
VA teams own:
NOTE all the VA tools currently rely on a Redshift db that effectively mirrors the Caseflow and VACOLS dbs.
Metrics
Groups of metrics included below:
Required OIT metrics
These are metrics required to report to OIT and OMB. They are a subset of all the metrics that we as a Caseflow team would like to capture. But because they're reported externally, they have to be priority.
Key OIT stakeholder contacts for these: Geoffrey Stienblock, Susan Kagan
Business metrics (appeals/decision review process metrics)
These are the hardest, given the appeals process. We'd like to influence the length of time it takes for an appeal to move through the system. Since it takes years, and there are a number of other variables (union quotas, multiple appeals systems, multiple dockets), it's difficult to see the impact of specific features tied back to those long term business outcomes. Doesn't mean we shouldn't try!
I think all these, below, should live in BVA's instance of Tableau.
Things we don't capture yet:
Things we have captured or know we need to capture
Product & performance metrics
Adoption & usage
User breakdown
Usability
Performance
Data dog dashboard - Service level indicators
Team process metrics
Old Caseflow Stats doc where we hacked together incident response metrics, CI metrics, and data integrity metrics.
Open questions
The text was updated successfully, but these errors were encountered: