The dashboard they'd
actually open.
An underused educator dashboard, rebuilt into a unified, workflow-driven tool — built around how teachers, admins and principals really work.
An educator dashboard people worked around — rebuilt into a tool they actually open.
- Staff handled attendance, progress and comms on paper, in spreadsheets, over texts.
- Rebuilt around real workflows — useful modules, fast daily tasks, connected flow.
- Now live in the field with educators, admins and principals.
It existed — but went unused
The dashboard existed — it just wasn't being used.
Educators, admins and principals were all expected to manage attendance, track progress and communicate through one centralized system. In reality those workflows were either avoided entirely or handled somewhere else — on paper, in spreadsheets, over personal texts. The product existed, but it never became part of anyone's daily work.
A tool, worked around
Educators weren't struggling to teach — they were struggling with a dashboard that didn't fit their work.
The pattern: the more friction a module added, the more it got skipped — until staff relied on the dashboard less over time, not more. (Illustrative of observed usage.)
Modules with no actionable value
Screens showed data but offered no next step, so adoption never took hold.
Attendance was cluttered & slow
The one task done every day was the most inefficient — so it moved back to paper.
Disconnected, with no flow
Nothing led to the next thing. Each task was an island, and the whole felt incoherent.
Too complex for leadership
A messy, heavy interface meant admins and principals simply avoided the system.
The more friction a module added, the more it got skipped — until people relied on it less, not more.The pattern behind the rebuild
Usability, not features
The problem wasn't a lack of features — it was a lack of usability and trust.
People ignored anything that didn't pay off immediately, repetitive tasks had to be fast and reliable, and a lack of structure made the whole system feel unpredictable and hard to learn.
Rebuilt around workflows
Stop redesigning screens in isolation — rebuild around real workflows.
Make features useful
Adoption follows value — every module had to earn its place.
Simplify the daily tasks
Attendance and other everyday jobs had to be fast and reliable.
Connect the modules
One coherent flow across tasks instead of disconnected islands.
Fix communication
Integrated chat plus AI support, built right into the work.
One connected workspace
A dashboard rebuilt around what staff do every day — every module connected, and finally worth opening.
What it moved
Useful, actionable modules gave staff a reason to open the product daily.
The cluttered daily task became a seamless, reliable one-glance flow.
Structured chat with AI support replaced scattered personal channels.
Useful, not just functional
Designing the dashboard meant breaking complex workflows down and rebuilding them into simple, usable systems.
From early explorations to refined interfaces, one test settled every decision: does this actually help someone get their work done? Functional was the floor — useful was the bar.
Have a product
to ship?
A redesign on the horizon, a 0→1 in your head, or just want to argue about button radii? My inbox is open.