A design system for the renewal of the student information system at Charles University
How do we give a legacy student information system, used across all faculties, a responsive, mobile-first interface, and a design system that holds up beyond a visual refresh?
I was head of design systems on a small team, working with a contracted supplier who helped with the UI design. I coordinated the design system work, built most of the Figma library and the Notion documentation, and checked that what we designed matched what was built in code.
The project started as a responsive, mobile-first interface for everyday student tasks: study plans, results and personal data. It soon became clear that a visual refresh alone would not fix the legacy system, and the scope grew into a renewal.
There was no design system to start from. I set up the Figma library with its variables and components, and documented each component in Notion, including its status in Figma and in development, so the team, the supplier and the developers worked from the same source.
Part of the job was reviewing implemented components against the Figma library and the docs, and feeding the differences back to the team.
Client: Charles University (Univerzita Karlova)
Location: Prague
Project length: February 2024 – June 2025