Roadmap
Customer Facing

Mystery Customer Admin

#6
Q3

Mystery Customer Admin

Prototype, test, and refine an Admin Usage Dashboard that lets district/school admins independently see product value and justify renewals without DPM help.

Overall80%
JIRA 1
RC-1026Loading…
Timeline
Start Jul 15, 2026Internal Aug 5, 2026Release Aug 26, 2026

What

Build and iterate on a prototype of the district/school Admin Usage Dashboard for Mystery Science, moving from initial mocks (V1) through an expanded MVP that adds engaged-teacher data, endorsements, and lesson ratings. Includes building a password-protected prototype using real school data so teachers/admins can interact with it directly, then testing and refining it with DPMs (Victoria, Sage, Natalie) before further design refinement (Heather/Victoria) and another round of modification and testing.

Why

District admins currently need DPM help to understand product usage and justify renewals. This dashboard is meant to let admins quickly see the value of Mystery Science on their own — showing that teachers are implementing it, why implementation looks healthy (or not), and helping them interpret the data — without requiring DPM intervention.

Success Looks Like

  • Admins can independently understand usage data and confidently justify renewals

  • Prototype accurately reflects real "lesson taught" data (resolving the mini-lesson vs. full-lesson discrepancy currently seen on the live admin dashboard)

  • DPMs validate the prototype with real school data and teacher engagement in testing

  • Design is refined based on DPM/teacher feedback through iterative rounds

Who's It For

  • District/school admins (end users of the dashboard)

  • DPMs — Victoria, Sage, Natalie (testers)

  • Heather/Victoria (design and product refinement)

  • Hopwood (prototype FE build/modification)

  • Brittany (data source and services input and driection)