Skip to content

Update tier review process SOP to align with journey needs and quarterly reporting #927

Description

@o-ram

Brainstorm and scope out how the quarterly tier review process should change

  • Align with the new reporting structure, so that the review helps feed reports
  • Factors in needed quarterly updates to the customer journey, where AMs are updating where their agencies are along their journeys and why

Process notes:
Moving forward we want to:

  • Do quarterly reviews that cover both tiers and journey placement
  • Look at all agencies in these reviews
  • For ones that are not "priority", can be a more cursory pass. For ones that are priorities, call out what you are doing with them right now
  • Have a dashboard that we use to populate ONE spreadsheet for the quarterly review. Review takes place in spreadsheet and then any resulting updates are officially made in the CRM.
  • Rough process
  1. At end of quarter, dashboard(s) are exported into a spreadsheet
  2. Review is prepped in s/sheet for looking at tier, journey, and assignment of agencies
  3. Review takes place
  4. Updates made in CRM
  5. Close out

Previous helpful notes for background context:
I created columns for each quarter (we already had Q1 and where we want them to end up in Q4/end of 2025). I duplicated Q1 for Q2. We can filter out all non-priority agencies and update for the 66 if there are updates.
All of Olivia’s agencies are at stage 8 (Payments/Benefits) and 3 might go to 9 in 2025 (get GTFS-RT), so no updates there
Basically the same for Laney, so this mostly for Nina and Marie
For the 66 priority agencies, I would report quarterly/monthly on quarter/month-over-quarter/month progress along the journey (rolled into existing report, ideally)
As simple as “X agencies moved along their journey, and if they did not, Y & Z are the main blockers” and here’s a snapshot of what 2025 looks like
For the ones that aren’t a priority in 2025, I recommend we (Caitlin/Enza) do quarterly newsletters to them in the first month of each quarter (January, April, July, October) to market what is upcoming/available to them, send additional announcements following up if needed (new MSAs or products, etc.), and/or if they’re really needed and could respond for/to a Campaign - otherwise we don’t do proactive outreach, but of course always respond if they reach out to Cal-ITP

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

CS Transition PlanningRelated to CS Transition PlanningdocumentationImprovements or additions to documentation

Type

No type

Projects

Relationships

None yet

Development

No branches or pull requests

Issue actions