One LMS. Four completely different jobs to be done.
Designing a role-based learning platform for 50,000+ students - where the hardest problem wasn't adding features, it was giving a student, a teacher, a coordinator, and an admin four different reasons to trust the same system.
Most LMS platforms fail quietly. Nobody complains - they just route around it.
Teachers keep a personal spreadsheet because the gradebook is three clicks too deep. Students miss deadlines because "due" and "graded" sit in the same flat list with no visual difference between them. Admins build their own reports because the platform's reports answer questions nobody asked. EduPath started from the premise that this institution didn't need another LMS with more features - it needed one that understood a "dashboard" means something completely different depending on who's looking at it.
- Navigation overwhelm One nested menu tries to serve course browsing, grading, and admin at once - regardless of who's logged in.
- Unclear prioritization Due, overdue, and graded items look the same. Users have to read every row to find what's urgent.
- Fragmented teacher workflow Content, grading, attendance, and messaging exist as disconnected modules, not a coherent daily flow.
- Admin complexity Governance tasks use the same density as student screens, despite needing a different control surface entirely.
- Role confusion The platform never structurally acknowledges that "what should I see" depends entirely on who's asking.
Interviews ran across all four roles - looking for where daily use actually breaks, not first impressions.
The goal wasn't to validate a visual direction. It was to find out what each role checks first when they log in, where they've quietly built workarounds outside the platform, and how differently "urgent" is defined depending on whose desk you're sitting at.
Each role gets its own navigation - scoped to their actual job, not a filtered version of everyone's.
Rather than one navigation tree gated by permissions, the platform gives each role a structurally distinct set. The only thing held constant is the underlying logic: every dashboard, regardless of role, leads with "what needs attention today" before anything else.
The mark needed to read as structured software, not K-12 edtech.
EduPath already names its own metaphor - a structured route through learning. No caps, no apples, no open books - those read as consumer edtech, not software serious enough to run 50,000 students' academic operations. The mark went through four rounds before landing on a direction that earned its place next to the product itself.
Three directions were explored early: path-text integration (routing arrows through the letterforms), a book/path monogram combining "E" and "P," and typographic stacking with "Path" sitting beneath "Edu." The stacked direction won - it read cleanest at small sizes and didn't force the path metaphor so literally that it would look dated in two years. From there, the typographic stack went through a serif pass, a too-light sans-serif pass ("ModuPath" - kerning issues, lost the brand name's clarity), before settling into the selected stack and moving onto the precision grid.
Construction reference for the wordmark - proportions, clear space, and minimum sizing, kept consistent with the product's own restraint: no flourish, no unnecessary ornamentation.
The prototype below demonstrates the role-based model described above.
Switch roles using the pill control near the top of the frame - the dashboard content fully reconfigures while the underlying chrome and component language stay structurally consistent. This is the thesis statement made interactive.
This prototype demonstrates the core navigation and dashboard model across all three built roles (Student, Teacher, Admin). Try switching roles to see the attention-first pattern reconfigure itself per user. Some deeper screens are scoped for the next design phase - what's shown here is the structural backbone, not full feature coverage.
Calm, structured, and readable across long sessions - never decorative for its own sake.
Every component - status badge, progress bar, attention card, data table - is designed once and reused across all four roles with different data. The semantic color palette is the hardest-working part of the system: it's the visual mechanism that makes overdue work look different from completed work, identically, whether you're a student or an admin.
Each screen below demonstrates a different piece of the system holding up under real pressure.
Rather than a full inventory, these four were chosen because each one proves something specific the research surfaced - not just coverage for its own sake.
Naming what's unresolved is more credible than implying full coverage.
EduPath is a real, in-progress product - so this isn't framed as "shipped and measured." The role-based navigation model is designed to reduce the navigation overwhelm from Insight 1. The attention-first pattern is intended to reduce missed deadlines and delayed grading. The grading queue is designed to shorten the gap between submission and review. None of that is a claimed outcome yet - it's the design intent the research points toward.
- Coordinator IA is the least resolved piece The altitude problem is clearly identified - the navigation and screens for it aren't fully designed yet.
- Mobile continuity layer is conceptual, not screened The principle (reminders, lightweight access) is set; execution is still ahead.
- Cross-role overlap isn't fully solved A coordinator who also teaches doesn't fit cleanly into the current role-switcher model yet.