Initial observation
The platform needed a more current experience and an integrated area for students.
Loading…
Case study · Sector: Training & Education
More students and new cohorts should mean growth. But when every new intake means redoing enrolments, content, confirmations, and admin tasks from scratch, growth also starts adding weight to the operation.
A recognisable way of reaching clarity
The learning experience and the day-to-day operation lived apart, forcing the team to manually connect courses, content, and processes.
What relationships kept the problem in place?
Content kept in separate places
Multiple points of management
Tasks tied to each cohort
Administrative repetition
Two disconnected journeys
The team connects everything by hand
The path from first impression to the real problem.
We didn't start by picking a solution. We started by testing whether the apparent problem was the right one.
Editorial reconstruction of the reasoning, based on the documented challenges, goals, and results. Not a literal transcript of the Discovery sessions.
Initial observation
The platform needed a more current experience and an integrated area for students.
First hypothesis
IncompleteA new interface and an online academy could solve most of the difficulty.
Why it looked right
The lack of an integrated area and a dated visual experience were the most immediately visible problems.
What changed our reading
Administrative processes kept consuming time.
Courses, content, and operations all depended on multiple points of management.
Simplifying only the student side risked shifting more work onto the team.
Why we changed direction
The student experience and the internal workload weren't two separate projects. They depended on the same information and had to be designed together.
New direction
The focus shifted from the interface to the information shared between learning and operations.
Deep-dive notes
What principle answered each pattern?
Principle 01
Principle 02
Principle 03
What changed in the way of working?
From
Every course added more work
To
Every course reuses a shared foundation
Multiple points of management
One shared flow
Tasks repeated per course
Recurrence built in
Growth adds work
Growth reuses the foundation
What was underneath the symptom?
Symptom
Too much admin work
Real problem
The same information circulates over and over
Principle
Centralise before you automate
“Centralising isn't about putting everything on the same screen. It's making sure the same information stops being created, carried, and confirmed over and over.”
Related idea
Why hiring more people doesn't fix processes that don't scaleWhen every new client, class or project brings the same admin work along with it, the usual answer is to hire. But hiring spreads the weight around — it doesn't reduce it.Explore the reasoningNext case study
Sector: E-commerce & RetailWhen the business wants to move and the platform makes it waitThe context changes. The method holds.