Operations analytics

What to monitor in your first 30 days

The first 30 days should answer one question: are learners moving from enrollment to mastery without friction?

Begin with three operational signals: time to first activity, week-one completion, and unresolved support requests.

  • Early activation. Track how fast new learners complete their first meaningful activity.
  • Friction detection. Monitor retries, hint usage, and stalled attempts by module.
  • Support throughput. Measure open tickets and response windows to protect learner momentum.

If those baselines are stable, expand monitoring into quality metrics such as retry patterns and hint dependency.

Build one dashboard your whole team can use

Teachers, coordinators, and support leads need the same weekly view so intervention decisions happen quickly and with shared context.

"Weekly operational reviews gave us early warnings before learner drop-off became a systemic issue."

Judith Rogers
Judith Rogers - Learning Director

Keep your review meeting short and action-oriented: one owner, one hypothesis, one follow-up metric per issue.

Operations team reviewing weekly learning metrics
Shared metrics create faster and more consistent interventions.

Turn metrics into weekly decisions

Define thresholds for alerting, then document response playbooks so teams know exactly what to do when a metric degrades.

By day 30, you should know which cohorts need coaching support and which content paths are ready to scale.