Mathletics - District Reporting Dashboard

Designing Data-Driven Decision Tools for US School Districts

Role: Lead UX/UI Designer

Team: CPO, Product lead, PM, BA, Engineers, Junior designer, Sales and Customer success.

Tools & Methodology: Figma, Miro, Maze — Design Thinking (Double Diamond), Research, Stakeholder Interviews, Data Synthesis and Visualization and User Testing.

Impact & Outcome: The Mathletics District Reporting Dashboard empowers district leaders to justify investment and secure funding by providing clear ROI and meeting reporting requirements. It drives strategic, data-informed decisions to improve student outcomes and boosts Mathletics adoption through transparent usage insights, ultimately strengthening partnerships with schools.

Here’s the interactive Prototype >

🧩 Brief

Mathletics is a globally used mathematics program serving over 3 million students. In the US and Canadian markets, public and charter schools operate within geographically structured districts, which are responsible for reporting performance to state and federal authorities. These reports guide funding allocations, especially toward at-risk or underperforming students.

District leaders need robust reporting tools to:

Track school and grade-level usage
Measure student proficiency by state standards
Identify underperforming student groups
Justify investments in learning technologies

Currently, we lack district reporting capabilities. To successfully enter the US and Canada markets, we need to build a brand-new district reporting system that meets their needs. Without this feature, districts often turn to competitors—even if they consider our products superior.

“When I’m overseeing my district’s math performance, I want a real-time dashboard to monitor student usage and outcomes by school and grade, so I can confidently make decisions, report to the state, and justify investment in digital tools.”

District Leader

— Discover & Define

Design Synthesis

From the initial brief, stakeholder interviews, competitive analysis, we identified key insights:

Provide a real-time, client-facing dashboard. 
Offer usage and performance insights across district → school → grade → class. 
Display outcomes by state standards.
Highlight student proficiency bands.
Enable filtering, drill-down, and exporting for all reports. 
Track teacher activity, student engagement, and learning outcomes(Progress).
Show trend data over time for progress and funding justification.

Key Insights

"We need district-wide views with drill-down into schools and grades."

"Without state-standard breakdowns, it’s hard to use this for reporting."

"Exporting data is a must—especially by specific metrics like time online, skill mastery, and grade-level performance."

_

— Develope & Test

Here’s the interactive prototype >

Design Strategy

We structured the dashboard into modular, outcome-focused views, allowing users to start broad and drill deep:

Dashboard

Usage across all schools (average score, questions answered and progress).
Student performance bands (above, at, below 50%)
Grade-level comparison and trends Quick weekly insights for engagement tracking.

Activation

Real-time tracking of school/teacher/student adoption. Impact: Flagged low-usage schools (e.g., Castro Valley Unified: 12/164 teachers activated)

Usage

Giving an overview at the top and by breaking down usage by school, leaders can identify which schools are leading in engagement and which are lagging.

Skills Practiced

Connecting practice patterns to student outcomes for targeted interventions. Answers the district leader's critical question:
"Where are students struggling, and which schools need instructional support?"

Standard Based Assessement

Linking granular skill mastery(Standards) to state compliance and funding decisions.

Core Purpose: Answers the district leader's ultimate question:
"Can we prove our students meet state standards for funding and accreditation?"

The initial phase using these mockups aims to validate our core assumptions by engaging key District leaders. Their feedback will be crucial in iteratively evolving the design to align precisely with their requirements and strategic business goals.

Phase 1:
Validating assumptions with District Leaders leveraging high-fidelity prototypes to test critical risk hypotheses before development.

We are in the process of getting feedback as this engagement will enable us to refine and evolve the design based on their critical requirements and overarching business goals.

Stay tuned!