OClass
Role
Lead Product Designer
Timeline
2025
2 months
OVERVIEW
Reduction in task completion time
Task completion rate in testing
PROBLEM
Despite OClass's goal of automating backend operations, term-based businesses hit real friction every time they set up a new term. Fragmented screens and manual steps turned a routine task into a slow, error-prone one.
Disjointed workflow
Reliance on external tools
Tedious invoice correction
QUOTES FROM USER INTERVIEWS
DISCOVERY & INSIGHTS
Listening past the noise
I ran user and stakeholder interviews to separate what people asked for from what they actually needed. Interviews were often full of resistance and conflicting requests, so staying anchored to the core task, setting up a term was what surfaced the genuine pain points.
A competitor teardown of Edulabs sharpened the direction. Its strength was guided, customisable workflows for high-frequency tasks: bulk actions, strong filtering, and flexible invoice editing. The takeaway for OClass was clear, adopt these patterns, then push them further for our own users.
This all had to work within real constraints: a universal approach across very different business types, without adding cognitive overload, scalable for future features, and feasible within OClass's existing UI and roadmap.
CHALLENGE
VISION & PRINCIPLES
Before designing any screens, I set the principles the solution had to meet, a way to keep decisions consistent across studios, centres, and gyms.

Edulabs Competitor Analysis
THE SOLUTION
1
One guided flow for class copy
Class copying is now a single process with fewer steps. Student enrolment and invoicing are folded into that same flow to cut effort and errors, while class-edit details are split into tabs so the main screen stays clear. A final review summary acts as a checkpoint — catch errors, confirm, and complete with confidence.
OCLASS COPY CLASS EDIT PAGE (OLD)
OCLASS COPY CLASS FLOW (NEW)
2
Flexible invoice editing
This ensures accurate billing aligned with student pricing plans and schedule. It helps accommodate diverse invoicing workflows across different businesses, reducing errors and saves time.
OCLASS INVOICES (OLD)
OCLASS STUDENT ENROLMENT & INVOICING (NEW)
3
Maintaining Data Integrity & Autosave
Auto-save function
Save to drafts
OCLASS AUTO-SAVE & SAVE TO DRAFT FUNCTION (NEW)
RETROSPECTIVE
No effort for users, a lot of it for us
Building a SaaS tool is a constant balance between what users ask for, what they actually need, and where the business is heading, usually with conflicting feedback in the mix. The hard part wasn't drawing screens; it was navigating ambiguity and tying every design decision back to a strategic outcome.
Working closely with admin users and the support team each week, we uncovered plenty of high-value improvements that could ship with low-to-medium effort. The lasting lesson: real impact comes from looking past individual features to the whole journe, and from communicating change well enough that users actually adopt it.
Looking ahead: the priorities are clear communication and education to drive adoption, and tracking engagement, feature uptake, and support volume to keep prioritising what creates real business value.







