A learning system for a large holding’s support department
- Timeline
- MVP — 2 months
- rollout — under a year
Task: bring three disconnected systems into one platform for learning and testing.
- Legacy LMScourses, kept in service
- Legacy Wikitraining articles
- Users
- Onboarding and user managementa profile is created, a manager assigns work
- Testing modulematerial → test → mark, and no way to fake it
- Reporting and analyticsevery finished activity lands here0%20%40%60%80%100%
How it works
Onboarding, and the employee filling in their own details
A manager assigns tests and training from the same profile, and every result later attaches to it.
The employee sits tests, reads the knowledge base and takes LMS courses
One chain, whichever system the material lives in: material → test → mark.
Results go onto the bus and gather in the operations centre
The two legacy systems stayed where they were and kept working — they report onto the bus instead of being rewritten.
Progress by person, team, subject and period
Reporting is not a layer on top of the platform, it is part of it: flexible exports and report setup come with the data, not after it.
Results
- 1500
- employees moved onto it
- up to 100%
- faster onboarding
- 2
- months to MVP
Honest testing
Cheating is no longer possible, and the quality of completion rose several times over
Legacy stayed in service
Cheaper to build and lower operational risk than migrating and retraining everybody
Stack
PHP · Symfony · MariaDB · Elasticsearch · Vue.js · Docker · Kubernetes