Designing a Role-Based Learning Platform for Students and Admin Teams

What this platform needed to solve

MPJA Learning was designed as an integrated online learning platform that supports flexible access, structured courses, progress tracking, certification, and monitoring. The real design challenge was not only building a learning interface for students, but also designing a system architecture that could support three different user roles: General Admin, Admin GM, and Student. The project required balancing usability, scalability, and operational clarity in one ecosystem.

What I was responsible for

I worked on structuring the experience of a multi-role learning platform, focusing on how different users would access the system, what information each role needed, and how the product could remain intuitive while supporting more complex administrative workflows.

The challenge was bigger than building a student dashboard

Many learning platforms are designed primarily around the student-facing experience, while admin workflows remain fragmented or unclear. In this case, the system needed to support not only course access and progress visibility for students, but also stronger management controls behind the scenes. Without a centralized and role-aware structure, managing courses, users, certifications, and monitoring would become harder to scale over time.

The system had to work for very different users

This project had to solve two very different usability needs. Students needed a simple and approachable learning experience, while admin users needed more power, visibility, and operational control. The platform also had to maintain a clear access hierarchy so responsibilities between General Admin, Admin GM, and Student stayed distinct without making the system feel disconnected.

We designed the platform around role clarity

I approached this project as a system design challenge rather than just a dashboard design exercise. The priority was to define who needed access to what, what actions belonged to each role, and how the platform could stay coherent across all three user types.

• For students, the focus was simplicity clear course access, progress visibility, and a structured learning journey.

• For admin roles, the focus shifted toward control: managing users, monitoring learning progress, and supporting platform operations without unnecessary friction.

This role-based approach helped the product stay scalable while keeping the user experience aligned with each role’s responsibilities.

The decisions that shaped the system

A critical decision was to make the platform role-based from the start instead of designing one generic dashboard and adapting it later. That created clearer boundaries between responsibility, visibility, and workflow.

Another was to treat monitoring as a core product layer, not an extra feature. Since both students and administrators needed visibility into progress, tracking became part of the main system value.

I also framed the system as one ecosystem with differentiated access, rather than three separate products. That keeps the experience operationally consistent while allowing each role to stay focused on its own tasks.

What the final product made possible

The result is a learning management system designed around role clarity, centralized management, and a more scalable structure for digital education. It supports student usability while giving admin users better operational control, which makes the product stronger both as a learning experience and as an internal management system.

What I would strengthen next

To strengthen this case study even further, I would add deeper role mapping, example workflows for each user type, and specific before-versus-after admin efficiencies to show how the system improves day-to-day operations.