SmartClass

Case study · Robotel · 2025 – present

Rebuilding SmartClass around how teachers actually work

SmartClass is a platform where language teachers build activities, assign them, and grade speaking, listening, reading and writing. I led UX research and UI design for its rebuild from the ground up.

Role
UX Researcher & UI Designer
Team
PM, senior developer, teacher testers
Timeline
Jan 2025 – present
Platforms
Web · desktop, tablet, mobile

The problem

A decade-old platform where activities were hard to create, assigning was hidden, and deleting a class could wipe a teacher's work.

What I did

Research with teachers, a new information architecture, 19 activity templates, a design system, and repeated usability testing.

The result

Teachers build once, assign anywhere, and see who needs help, finishing core tasks without a trainer.

Every product screen on this page is a working recreation. Click, filter and try them. Skim mode: key screens and outcomes only

01 · Before

Ten years of features, no clear path through them

SmartClass ran on legacy code that one developer could maintain. Districts' security tools had started blocking it, and teachers kept saying: it looks outdated, and it's hard to get from A to B.

An earlier redesign attempt by another team stalled. In January 2025 the project restarted with me: rebuild the core so customers can move to a new web platform, then add the features teachers were asking for.

Why it matters

Teachers spend a significant share of their time on administrative tasks instead of teaching. OECD TALIS, 2019

What teachers need

Tools that let them focus on teaching rather than administration. Darling-Hammond et al., 2020

Scroll to see all four screens
Old start modal asking where to begin
Every session began with "Where would you like to begin?"
Old Create Activity window
Six types, nine templates, no explanation.
Old Organize and Assign screen
Two panels, two toolbars, one hidden action.
Old grade report
A grade report capped at 29 activities.
Real screens from the old platform. Click to enlarge.

02 · Research

Understanding teachers before touching a screen

I combined what the company already knew with new research, so every decision could point back to something a teacher did or said.

Discover

Interviews & contextual inquiry

Watched teachers prepare, assign and grade, in person and over Zoom.

Discover

Support tickets & analytics

Ranked recurring complaints and found where teachers stopped mid-task.

Discover

Heuristic evaluation

Scored the old product on efficiency, visibility and learnability.

Discover

Competitor analysis

A feature matrix across 12 platforms, from Canvas to Sanako and Quizlet.

Discover

Hands-on authoring

Built sample courses in Rise, Storyline, H5P, Canvas, Moodle, Blackboard.

Synthesize

Affinity, empathy & journey maps

Themes in FigJam, then a teacher's week from plan to report.

What each role needed

I interviewed teachers, students and an administrator. Teachers were the key group and became partners in the redesign.

T

Teachers

  • Group students; placement tests; progress tracking
  • Assign to a class, a group or one student
  • Gamification: leaderboards, challenges, class games
  • A chat or inbox to reach students
S

Students

  • Motivated by game-like, interactive practice
  • Simpler navigation
  • Works well on a phone
A

Administrator

  • Course management across many teachers
  • Security that districts accept
  • Scalability and licences

What competitors taught us

Three of the twelve platforms, summarised. Tap a card for its weak spots.

The pattern. Gamification, personalisation and accessibility set the best tools apart. LMSs like Moodle and Canvas win on flexibility but lose on simplicity, while Sanako and Klett show the value of teacher-first tools. SmartClass aimed for simple workflows, strong accessibility and engaging practice.

Affinity board

What teachers told us, grouped by theme

An affinity board groups comments into themes so patterns become visible. Filter by theme to see what teachers said about each part of their week.

Who we designed for

The interview themes were mapped onto three personas from the Robotel persona set, so every decision could be tied to a real person. Chelsea uses SmartClass every day. Ana and Nelson decide whether a school adopts it.

A fourth persona, a reseller partner, shaped licensing and onboarding rather than screens. Students were covered by interviews instead of a persona.

Teacher journey · tap a stage

A journey map follows Chelsea through a normal teaching week. Taller bars mean more effort and frustration; red marks the worst moments, which became the deep dives.

03 · Problems

Five problems kept coming back

The first one reshaped the navigation, the next three became the deep dives, and the last shaped the design system.

Hidden navigation

Every area sat behind one dropdown and a start modal. In the audit walkthrough, the tester didn't realise other sections existed.

AuditOld screens

Tangled data model

Activities and students belonged to a class. Same-name classes mirrored each other, and deleting the last class deleted the whole library.

DiscoverySurveyTraining

Confusing activity creation

It started with uploading a file. Teachers couldn't tell what a template offered, picked one blindly, then faced one long form.

SurveyAuditTraining

No at-a-glance status

Nothing showed who had submitted or what still needed grading without opening every activity.

DiscoveryTickets

Dated, inconsistent UI

Text under 16 px, buttons that didn't look like buttons, grey icons that read as disabled.

AuditSurvey

How might we…

help teachers choose the right template before they start building? Answered in deep dive 1
let teachers build once and reuse across classes, groups and students? Answered in deep dive 2
show teachers who needs attention without opening every activity? Answered in deep dive 3

First came the principles and the new structure. The deep dives then answer each question in turn.

04 · Direction

Three principles behind every decision

Before any screen, the PM and I agreed on three principles. Every design was checked against all three.

Efficiency

Fewer steps for weekly jobs: create, assign, grade.

Visibility

Status, next actions and navigation always on screen.

Learnability

A teacher new to tech finishes a task alone the first time.

05 · Design process

From a sitemap to high-fidelity screens

With the PM, I wrote a North Star hierarchy: a persistent sidebar instead of a hidden dropdown, and a workspace for each class. User flows, wireframes and prototypes followed.

Sitemap

A sitemap is the map of every page and how pages are grouped. It decides where things live before anyone designs how they look. Compare the old menu with the new structure, then tap a column to see why it is shaped that way.

Tap a section to see what lives there.

The teacher's weekly loop

A user flow shows the steps someone takes to finish a job, including the decisions along the way. This main flow ties the three deep dives together: build, assign, then follow up on what comes back.

SET UP · ONCECREATE · DEEP DIVE 1ASSIGN · DEEP DIVE 2FOLLOW UP · DEEP DIVE 3 Create a class Invite students Create an activity How? AI builder Template Draft + activities Assign Students complete Gradebook Missing → Remind To grade → Grade Low → Redo many at onceone, full control saved to My activities class, groupor one student
Main user flow, redrawn from the FigJam flows. Decisions are diamonds; the three highlighted steps are the deep dives.

Sketch, wireframe, high fidelity

Each new feature went through three passes, with a design critique with the PM and developer after each one. Quick sketches settled what goes on the screen. Low-fidelity wireframes in Figma, with real labels and placeholder content, became a clickable prototype for the first teacher sessions, so problems were cheap to find and fix. Only then did colour and the design system arrive.

In short: a sketch decides what is on the screen, a wireframe decides where it goes and how it works, and the hi-fi decides how it looks.

Same screen, three fidelities. Switch between them to see what each pass decided.

06 · Deep dives

Three jobs teachers do every week

Each follows the same path: problem, research, decisions, testing, outcome. And each one is live.

Teachers picked templates blind. Now they browse a gallery that explains each one, fill a short focused editor, or let AI draft the work.

The problem

  • "Create activity" meant "upload a media file", before the teacher had said what the activity was.
  • Templates were bare checkboxes. Nobody could tell what one offered or how two differed.
  • The editor read as one long form, and "Close Editing" actually meant save.
  • Teachers said again and again: we don't have time to build activities from scratch.
Before: old Create Activity window
BeforeAfter
Drag the handle. On the left, the old window: a list of template names with nothing to explain them. On the right, the new gallery, where every template says what it does and which skills it practises.

Follow a teacher creating an activity

Scroll. The screen follows the story.

Step 1

Choose how to create

Two clear routes. Smart Activity Builder uses AI to draft several activities from a few settings; Single Activity opens one template with full control.

Step 2

See what each template does

Every template is a card with a one-line description and the skills it practises, so teachers choose before they commit. This came straight from round 1 testing.

Step 3

Fill only what the template needs

One editor pattern for all 19 templates: name, metadata, instructions, files, then questions. Media is a field, not the starting point.

Step 4

Students see exactly that

What the teacher builds is what students get, on any device, with dropdowns, drag-and-drop, typing or speaking.

Step 5

Feedback right away

A colour-coded grade, written or audio feedback, and a Redo button. Teacher-graded work shows a clear "waiting" state.

Try the Template Gallery

Teachers told us they picked templates blindly, so every card now explains itself. Filter by skill, search, or star a favourite; favourites move to the front.

Live prototype

Anatomy of the editor

Tap the numbered dots to see why each part is there.

Smart Activity Builder

A three-step wizard: settings (language, level, topic) → activity types (tick several) → vocabulary (up to 20 words, typed, from an image, or suggested by AI). Each draft opens in the normal editor for review. The AI starts the work; the teacher stays the author.

Play the student side

What the teacher builds is exactly what students get. Try three of the new activity types the way a student would.

Student view
Flashcards were rebuilt after a teacher survey asked about images and audio. AI Conversation is new: teachers set the role, topic, opening line and questions.

Testing and iteration

In moderated round 1 (in person and on Zoom), teachers could build an activity once inside the right template, but choosing it was slow. Several opened the wrong one first. One said: "I don't know what Segmented Recording is until I'm already inside it."

A Maze preference test compared a plain list of names with cards showing icon, description and skills. Teachers preferred cards because they could tell templates apart at a glance.

In round 2 I measured task success, time on task and errors for "create a Fill in the Blank activity". Most finished alone and found the right template on the first try.

Outcome. Activity creation went from a file-first flow that needed a trainer to a self-explanatory gallery and one consistent editor, with AI for teachers short on time.

07 · Design system & accessibility

A system small enough for a team of two

One designer and one developer shipped 19 templates and 14 product areas. The system extends the SmartClass brand in Noto Sans and adapts Shadcn and Google Material patterns.

A design system is the shared kit every screen is built from: colours, type, spacing and ready-made components. Pick a tab to explore it. Each one says what the part is for, and everything is live.

Foundations
Components

The decision that changed everything

Early dashboards bordered every card. Once the Activity Builder was added, screens felt busy, so borders gave way to spacing and soft shadows. Toggle to see the difference.

Responsive by design

Every teacher screen was designed for three sizes. Switch devices, and pick a colour or pattern for the class card.

Accessibility, checked not assumed

SmartClass is used by teachers and students with different abilities, devices and first languages. The target was WCAG 2.1 Level AA, the standard most school districts ask for. These are the criteria that shaped the design most. Pick one to see what it means and how the design meets it.

How I checked

WAVEaxe DevToolsStark in FigmaWebAIM Contrast CheckerVoiceOverKeyboard only
1.4.3

Contrast

Text must stand out from its background, with a contrast ratio of at least 4.5:1.

In SmartClass: Body text, muted text and every tag colour were checked in Stark. See the live table below.

Found in testing: the yellow status text was darkened to pass on its light background.

Contrast of the SmartClass palette

Calculated live on this page with the WCAG formula. 4.5:1 is the minimum for normal text.

Known issue. White text on the bright blue Create button and the green Assign button does not reach 4.5:1. Both colours come from the brand guide. The fix, either darker shades (blue-700 and green-700 pass) or navy text, is planned for round 3.

08 · Testing

Tested with teachers at every stage

Each round used real tasks. I tracked task success, time on task and errors, and logged findings in Notion and Google Sheets.

Round 1 · moderated

Find the breaks

6–7 teachers set up from scratch. Adding students and assigning failed for many.

Between rounds · Maze

Compare options

Preference and first-click tests on gallery layouts and the draft card.

Round 2 · moderated

Check the fixes

Most finished all four tasks alone; groups and multi-course dates stayed hard.

Round 3 · planned

Learnability

Tooltips and intro videos, plus alpha and beta feedback from real classes.

How core tasks moved

TaskRound 1Round 2
Create a courseDone aloneDone alone
Add studentsMost needed helpMost done alone
Create an assignment, add activitiesMost needed helpMost done alone
Create an activity from a templateSlow, wrong turnsRight template first try

09 · Across the product

More of what I designed

Beyond the deep dives, the rebuild covered every place a teacher, student or admin touches. These work too.

Add users

Four ways to invite, each with a list of active invites. Built after round 1 showed teachers struggling to add students.

Login

Google sign-in, or username, email, or a class code for quick student access.

Notifications

Grouped, filterable, each with a direct action. Click one to mark it read.

Resources

Teacher and student materials by language and CEFR level.

Also designed: Students and roster with groups, Activity Exchange (five iterations; sharing is opt-in per activity and controlled by admins), Profile and notification settings, Licenses for admins, and a teacher dashboard concept for the next phase.

10 · Outcome & reflection

What changed, and what I learned

  • The core journey (create a class, add students, create, assign, grade) rebuilt on a new web platform with mobile support.
  • A content model that keeps a teacher's work instead of deleting it with a class.
  • A design system that let one designer and one developer ship 19 templates consistently.
  • Between rounds 1 and 2, core tasks went from needing help for most teachers to being done alone by most.

Next: round 3 testing with tooltips and intro videos, the teacher dashboard, and AI Conversation in more languages.

What I learned

Fix the structure before the screens

The biggest problem wasn't visual. Content lived inside classes, so deleting a class deleted a teacher's work. Moving content into a personal library solved what no redesign of the screens could.

Design for the least confident user

Clear labels, helpful empty states and one editor for every activity type helped more than polish. When the least confident teacher could finish a task alone, everyone could.

AI should start the work, not finish it

Teachers trusted AI drafts because the drafts opened in the editor they already knew, where they could check and change everything before students saw it.

Learning science shapes product decisions

My background in educational psychology led to skill tags on activities, translated instructions and clearer feedback for students.