Ideate metrics to collect

[jaimiebutton]

Ahead of our systems going live, let's align on how we can collect metrics to continually measure how our systems are meeting user needs and supporting business system goals.

Acceptance Criteria:

• [ ] Review this Miro board of past ideas
• [ ] Brainstorm overall goals of our system that can be measured with metrics
• [ ] For each goal identified, brainstorm individual metrics that can be collected (record these in one colour of sticky note)
• [ ] Ask the program if they would like any metrics collected (record these in a different colour of sticky notes)
• [ ] Prioritize metric sticky notes on a matrix of impact & effort to implement
• [ ] Discuss governance strategy around metrics - who will collect, analyze, and oversee?

Goal of this ticket:

• Gain collective clarity on what metrics should be collecting to ensure we're getting ongoing feedback on our systems

[patriciarussellCAS]

@NicoleGovvy is this different than Ticket bcgov/cas-reporting#17 ? Would love to dig into this more to understand the difference :)

[NicoleGovvy]

@patriciarussellCAS they're essentially the same - I think I'd flagged bcgov/cas-reporting#17 as being able to be closed. KPIs can be bigger or different than metrics - but are usually measured by metrics.

[zoeyli-46]

For the 2nd AC "Brainstorm goals of system that can be measured" We could refer to the reporting user story map and the registration user workflows for steps in the user journey that we can brainstorm goals for.

For example, the step "enter emissions" we could come up with goals like "reduce user error when entering emissions"