EdTech · B2B SaaS

An employee learning management platform for companies

Clariq gives the admin or manager who runs company learning one place to create, assign and track employee training across teams — instead of scattering it across tools.

Role

UX/UI Designer
Solo, end-to-end

Timeline

~4 months
Jun – Sep 2026

Type

Concept · B2B SaaS
EdTech

Tools

Clariq dashboard on a laptop

Who it's for

Companies that want to pull scattered learning into one place, see who's actually learning, and understand where skills are missing.

What I did

The full cycle, solo — research, MVP, flows, IA, hi-fi wireframes, usability testing with 5 users, and the final UI and design system.

01

What “Clariq” is

A platform that brings onboarding, courses and mandatory training into one place, tracks who completed what, and shows where skills are missing across the company.

Admin / manager

Runs company learning — creates courses, assigns them, tracks progress and skill gaps.

Team lead

Sees their own team's progress and where it's falling behind.

Employee

Completes onboarding and whatever's assigned to them.

02

The problem, and the answer

Problem

Chaotic management — onboarding, materials and courses are scattered across different systems (Docs, Notion, video).

Problem

No transparency or control — the company can't see who finishes, who's behind, which teams score lowest, or which topics cause trouble.

Problem

No view of skills — no sense of which skills are missing, who's ready for promotion, or which courses bring the most value, so learning is generic and resources are wasted.

Solution

One place with a fast course builder — all learning assembled and run from a single platform.

Solution

A progress dashboard — completion, laggards and weak spots across every team at a glance.

Solution

Skill Gap Analytics — missing skills, promotion readiness, and who needs which course next.

03

Competitor analysis

I ran the project on the Double Diamond and started with research: I pulled apart how competitors handle the three things a manager does most — creating a course, assigning it, and reading reports — swept a wider set of LMS products on Mobbin, and sense-checked against user reviews on Reddit and G2.

What I foundReviews are mixed, so I treated this as a sense-check, not proof:

TalentLMS

  • Dated UI, less intuitive navigation.
  • Course creation feels click-heavy.
  • A dual interface that confuses people.

Recurring complaints — G2 · Capterra

Docebo

  • Steep learning curve.
  • Complex, clunky admin back end.
  • Hard to get around advanced config & permissions.

Recurring complaints — G2

So I kept nothing visual from them. I borrowed clean composition patterns from Podia (course builder, confirm dialogs, Public/Hidden) — but not its color or gradients.

What users said — G2

TalentLMS pros and cons on G2

TalentLMS — pros & cons on G2.

Docebo pros and cons on G2

Docebo — pros & cons on G2.

Flows & patterns I mapped

Competitor flow board — TalentLMS and Docebo mapped by task

TalentLMS vs Docebo — flows mapped by task.

Patterns pulled from other products on Mobbin

Patterns from other products (Mobbin).

04

MVP scope

From the research I defined a feature matrix and the MVP modules.

  • Dashboard
  • Courses
  • Create course
  • Assign
  • Users / Teams
  • Onboarding
  • Learning Paths
  • Reports
  • Settings / Billing
Feature matrix — module coverage across TalentLMS, LearnUpon and Docebo

Fig 2. Feature matrix — module coverage across leading LMS platforms.

05

Course creation flow in motion

Before the process, here's the product working — a full run through the course creation flow, from the course list to a published, ready-to-assign course.

Creating a course, end to end — course list, details, content builder and completion settings.

06

User flows

The main flows, end to end — admin side and employee side.

Clariq user flows — create and publish course, assign course, track progress, learner completes course

Fig 3. Key user flows — HR and learner journeys.

07

Information architecture & navigation

I mapped the product's sections and navigation to decide what to build and lay out the paths — so the wireframes had a clear structure to follow.

Clariq information architecture — full sitemap starting from the Dashboard

Fig 4. Full sitemap — everything starts from the Dashboard.

08

High-fidelity wireframes

From there I moved to high-fidelity wireframes — laying out every path, the full functionality and placement in detail.

Clariq high-fidelity wireframe — Courses list with filters
Clariq high-fidelity wireframe
Clariq high-fidelity wireframe
Clariq high-fidelity wireframe
Clariq high-fidelity wireframe — Courses with date filter
Clariq high-fidelity wireframe
Clariq high-fidelity wireframe
Clariq high-fidelity wireframe
Clariq high-fidelity wireframe
Clariq high-fidelity wireframe
Clariq high-fidelity wireframe
Clariq high-fidelity wireframe

Fig 5. High-fidelity wireframes — every core screen and state, laid out end to end.

09

Usability testing — and what I changed

MethodI built a clickable prototype and ran the tasks with 5 relevant users (U1–U5) over Zoom in September 2026: create a course, set deadlines and reminders, assign it to a team, check progress. I clustered everything into an affinity map in FigJam.

A usability-testing session over Zoom, with the task scenario shown alongside the call

Fig 6. Running the tasks with users over Zoom — the task scenario alongside the call.

Affinity map of the testing findings, clustered on a FigJam board

Fig 7. Findings clustered in FigJam.

10

Key decisions from usability testing

Each one is a change I made after testing — the problem, the fix, and before / after.

What changed · 01

The dashboard's "Needing Attention" table

FindingThe table (then "Team needing attention") showed team, number of employees, average progress, overdue and status — which didn't tell the manager what was actually wrong, or who specifically needed help.

ChangeRenamed to "Needing Attention" — it's not only teams, a single person can need it too. Reworked the columns to Team / Employee · Course · Progress · Due date · Status, with a Remind quick action. Now it points to the exact course and person, and you can act in one click.

BeforeDashboard — the old Team needing attention table
AfterDashboard — the reworked Needing Attention table with a Remind action

What changed · 02

Visible actions in the course builder

FindingThe Content Builder step had just a + icon; in testing, people didn't realize that "Add lesson" and "Add quiz" lived inside it.

ChangePulled those actions out and placed them directly in the module, highlighted, so adding a lesson or a quiz reads as the main action. No more guessing.

BeforeCreate course — Content Builder with only a plus icon to add content
AfterCreate course — Content Builder with visible Add lesson and Add quiz actions

What changed · 03

"Build your lesson" instead of a fixed template

Finding"Add lesson" opened a rigid template with video, file and text fields already added — whether you needed them or not.

ChangeNow it's a "Build your lesson" block builder — add only the blocks you want (just a video, just text, and so on). A plain builder means the person sees only what to focus on, which cut the cognitive load.

BeforeAdd lesson — a fixed template with video, file and text fields already added
AfterBuild your lesson — an empty block builder where you add only the blocks you want

What changed · 04

A user profile that answers questions

FindingThe profile showed numbers without a clear "so what" or a way to act on them.

ChangeAdded a quick Assign button next to each course in Skill Gaps (close a gap on the spot), and a "Promotion Readiness" label so the platform signals whether someone's ready for a promotion. The profile now answers questions instead of showing random numbers.

BeforeUser profile — Skill Gaps showing numbers with no way to act on them
AfterUser profile — Skill Gaps with per-skill Assign buttons and a Promotion readiness label
11

Final UI

I wanted to move away from the dated LMS look and make Clariq modern, minimal and intuitive. People using it work with a lot of data, so I kept the colors calm and unobtrusive — easy on the eyes and easy to read across long sessions.

Fig 8. A sweep across the final interface.

12

Design system

I set up a full design system to keep the UI consistent — color and spacing tokens, typography, and a library of 21 component sets from atoms to organisms: buttons, fields, the People table, metric cards, sidebar and dialogs. I built it out with the help of AI (Claude).

Clariq design system — foundations: colour scales, typography and semantic tokens Clariq design tokens built as variables in Figma

Fig 9. Foundations and design tokens — documented and built as Figma variables.

13

Assign flow in motion

One of the ways to assign a course to a user — right after you create it, or later by opening the course settings. Choose people or teams, set the schedule, review, and send.

Assigning a course — select workers, set the schedule, review, done.

14

Screen gallery

The breadth of the UI across the main sections.

15

Summary

The redesign answers the three management problems: it centralizes learning in one place, makes progress transparent and controllable across teams, and turns skills into something you can see — gaps, promotion readiness and where to develop people next.

It's a concept product, so the design is validated against usability findings, not business metrics.