When the Classroom Became the Complexity : Nebula Leap Technology needed one LMS that worked for four completely different people — Admins managing the entire ecosystem, Institutions overseeing cohorts, Teachers running assessments, and Students just trying to learn. Each role carried different mental models, different permissions, and a completely different definition of what simple even meant. As the sole designer, the risk wasn't building too little — it was building something that tried to serve everyone and ended up truly serving no one. Before touching a single screen, I mapped the full permission hierarchy across all four roles, defining who sees what, who controls what, and where the boundaries between roles had to hold firm. That structural work — unglamorous and invisible to the end user — was the decision that kept the entire ecosystem from fragmenting under its own weight.
One Language. Four Readers : The breakthrough came when I stopped thinking about four separate experiences and asked one question — what does every user, regardless of role, actually need at any given moment? The answer was always the same: know where I stand, know what to do next. That became the north star behind every decision. I validated the student journey first — the most emotionally loaded and most public-facing surface of the product — and used a phased approval process with the client to catch structural problems early before they spread into the teacher and admin layers. The process moved deliberately from research and IA through personas, wireframes, repeated UX testing, and final UI, before culminating in a scalable design system that made consistency across three platforms not just possible but reliable.
Solo Designer. Full Ecosystem. No Safety Net.
The hardest challenge on this project wasn't the complexity of the design — it was the weight of the scope. Integrating live classes, exam management, OTP login, online payments, live chat, and a full gamification layer — quizzes, leaderboards, and progress tracking — across four user roles and three platforms, alone, meant one inconsistent decision could quietly break patterns established weeks earlier. The gamification system required the most iteration of anything in the product. Leaderboards carry real risk — they can demoralize the students who need the most encouragement. I designed them to surface personal progress first and peer ranking second, so every student competes with their past self before competing with anyone else. The design system was the structural answer to all of it — a contract ensuring every component meant the same thing wherever it appeared.
The Thinking Is Already Proven
The final product delivered a mobile-first LMS where Admins gained operational clarity, Institutions got visibility, Teachers got speed, and Students got an experience that felt built specifically for them. OTP authentication built trust at first contact. Gamification improved engagement and retention. Simplified onboarding lowered the barrier for new institutions joining the platform. And a unified design system made every future development cycle faster and more consistent. The platform is yet to be deployed — but the most important lesson from this project has already landed. The best multi-role products never show their complexity. They carry it silently, invisibly, so the person on the other side never has to think about it at all
