Prescient Security needed a learning platform that could teach an individual learner, be run by instructors and admins, and be rolled out across a whole organization — without collapsing into three disconnected products. Axlume designed one system that gives each role a focused, purpose-built experience on a single, calm visual language.
Prescient Security builds security and compliance training. Their product had to work for three audiences at once — the learner taking a course, the admin building and grading it, and the organization enrolling a whole team — and each of those people wants to see almost nothing the others need.
Axlume owned the product design end to end: the information architecture, the role-based navigation, the full UI, and the design system that holds it together. The result is one platform that reads as three tailored apps — learner, instructor/admin and organization — sharing a single visual language, component library and data-visualisation style.
Most learning platforms solve this badly. Either they ship three disconnected tools that feel like different companies built them, or they cram every role into one interface where a learner wades through admin controls and an org manager hunts for the one number they came for.
And the surfaces are genuinely heavy: a quiz builder with multiple question types and grading, cohort analytics with pass-rates and attempt curves, organization management with verification and subscription states, per-seat billing. Designed carelessly, any one of those becomes a wall of controls.
The brief was to make all of it feel calm — to give each role a screen that looks like it was built only for them, while every screen still obviously belongs to the same product.
Progress, enrolled courses, quizzes and certificates in one calm view — the entire administrative half of the platform simply removed from sight. This is the experience an individual learner lives in.
Before any screen, we mapped who does what — and made role the organizing principle of the whole system, not a permission bolted on at the end.
We separated the jobs-to-be-done for three users — learner (find, take, pass, get certified), admin/instructor (author, grade, publish, read outcomes), organization (enroll teams, verify, manage seats). Each got its own navigation and its own home.
One content spine — courses → lectures → quizzes → certificates — surfaced differently to each role. The learner sees a course to finish; the admin sees the same course as something to build and measure.
A single token set — the indigo/violet palette, glass-surfaced cards, one type scale, one chart style — so a learner dashboard, an admin analytics view and an organization table all read as one product.
Every surface designed to production standard, including the hard ones — the multi-type quiz builder, the cohort analytics, the organization console — each reduced to the few things that role actually needs.
Flows connected end to end — sign in, enroll, learn, get assessed, get certified — and handed off as a build-ready system, not a folder of static screens.
Discover, enroll, watch and get certified. The learner’s world is deliberately narrow — a home that tracks progress, a clean course and player surface, quizzes, and certificates. Nothing administrative leaks in.
Course detail and the video player — curriculum, lectures, progress and an embedded player — designed so “continue learning” is always the obvious next action.
The admin’s quiz builder: multiple question types, correct-answer selection, reordering and live preview — the platform’s most complex authoring surface, designed to feel like filling in a form, not operating a machine.
Cohort stats, pass/fail rates, attempt curves, average and median scores, and earnings — the read-out layer that turns activity into a decision, for instructors and admins alike.
The operator console — organizations with verification and subscription states, user tables with activity and spend — dense data made scannable through one consistent table and status language.
Free and business tiers, per-seat pricing and trials — monetisation designed into the product, not tacked on, so upgrading is a short path from inside the app.
The path a learner actually walks — a branded front door with a single choice, a course built around progress, and a distraction-free player. The rest of the platform stays out of the way.
The admin’s quiz builder is the platform’s heaviest surface — multiple question types, correct-answer selection, drag-to-reorder and a live content outline. We designed it so authoring a graded assessment never feels like operating machinery.
The platform isn’t three products, and it isn’t one crowded app. It’s a single design system feeding three navigation shells — learner, admin and organization — that all draw from the same content spine and speak the same visual language.
What admins and organizations actually run the platform on — people, teams and outcomes. The same table, status and card language carries all three, so nothing here has to be relearned.
The platform ships as one product that behaves like three. A learner never sees an admin control; an admin never wades through learner chrome; an organization gets its own portal — and all three are instantly recognisable as the same system.
What the design delivered:
Adoption, activation and learning-outcome metrics are held under NDA — available on request, or we can prepare a client-approved figures brief before publishing.
The difficulty in a multi-role product isn’t any single screen — it’s consistency under pressure. The same table pattern has to hold for users, organizations and quiz reports; the same status language has to mean the same thing whether it’s a subscription, a course or a quiz attempt; the same card has to feel right holding a progress bar or an earnings chart.
So the work was systemic, not cosmetic. A tight token set — the indigo/violet palette, one radius language, one elevation model, glass-surfaced cards — and a component library disciplined enough that a new screen is assembled, not invented. That is what lets three very different experiences stay unmistakably one product.
The payoff is a platform that scales by role and by feature without fragmenting: add an organization view, a new analytics surface or another question type, and it drops into a system that already knows how to hold it.
You’ve seen our standard of engineering. Now, let’s build yours. From high-impact websites to complex enterprise applications, we specialize in transforming ambitious ideas into elite-grade digital reality. Whatever the platform, we bring the precision your vision demands.