Azvasa LMS — architecting concept-based learning across three roles

Azvasa is a concept-based Learning Management System built for private-sector schools. Instead of testing students on recall, it organises every subject into its underlying concepts and asks concept-oriented questions designed to build real understanding — mapped to each school's curriculum, grade by grade.

The platform serves three roles — students working through curriculum and concept quizzes, teachers managing classes and tracking performance, and admins overseeing the school — and ships as both a downloadable mobile app and a full desktop web application.

On Azvasa, I worked as the product designer — and that meant owning the full arc, not just screens: product design, application architecture, and testing, end to end. That included architecting how a curriculum actually gets represented in software — every grade, every subject, every concept, and how a student's progress through them gets measured, marked and reported.

The problem statement was direct: provide concept-based learning that helps a student understand a particular lesson and the roots behind it — not just get the surface-level answer right. Private schools had curriculum content and question banks, but no structured way to teach or test the underlying concept a lesson was actually built on.

Standard multiple-choice testing rewarded memorisation over understanding, gave students no visible sense of progress, and gave teachers no early signal of who was falling behind on a specific concept — only a subject.

Before any wireframe, structured research ran across all three roles — 15 students across different grade levels, 10 teachers across subjects, and school admin stakeholders — to understand how each group experiences learning, assessment and school management.

Azvasa's core challenge wasn't visual design — it was defining what a "concept" is inside a curriculum, and whether a good way to teach and test it already existed anywhere in the market. Herbert Simon's seven-stage design process fit that problem directly: it starts by defining the thing you're designing before you touch a solution, and only converges on components once you know they're both meaningful and available.

I defined the application architecture end to end — broken into three flow architectures that had to work together: a student functional flow architecture covering how a student moves through grade, subject and concept; a concepts architecture defining how each concept tree is structured and surfaced; and an admin & teacher review flow architecture covering how content gets approved, released and reported on.

Once the web application's concept trees, examinations and mark sheets were architected, the same structure had to work as a downloadable mobile app — the format most students and teachers actually reach for first.

Testing focused on whether the happy path actually completed end to end for each role — that a student could finish a quiz without hitting a dead end, that a teacher could release a chapter without missing a step. Concept testing validated whether a question genuinely tested understanding of its concept, feasibility testing checked whether each concept and flow was realistic to build and maintain, and A/B testing compared competing presentations of the same concept to see which one students actually learned from.

Azvasa was my first full LMS build, and the hardest part was never the screens — it was defining what a "concept" is precisely enough that a marking system, a concept tree, and a quiz type could all agree on it. Herbert Simon's seven stages gave that definition work a process, instead of leaving it as a vague first meeting.

Rebuilding the same architecture for mobile after the web version already existed was the best forcing function on the project — every screen had to justify its place on a smaller canvas, which made the whole system more disciplined, not just the phone version of it.

The biggest lesson: motivation design isn't cosmetic. Streaks, scores and animations are the mechanism by which a student decides whether to come back tomorrow — getting that right mattered as much as any concept tree.