Design system

Problem
I worked for 18 months as part of the UX team on a large government project, developing new tools and systems for a well-known organisation. Our task was to modernise complicated and outdated online interfaces and applications. Due to NDA restrictions, specific details and visuals can’t be shared.

Challenge
The project involved creating a new design system. This was a first the for the organisation. The system we developed would be used by the wider company on future software projects. We adopted the principles of atomic design. Creating atoms, molecules and organisms to produce templates and pages. The agile work method of working in sprints was used to design, test and build. Collaborating closely with two UX strategists I was responsible for building out the design system while also supporting with developing user flows, wireframes, user testing and producing hi-fidelity designs

Solution
Our design system was built using Material Design 3. The lack of ready components proved a problem later in the project. It is primarly designed for mobile apps not large IT systems. We also had to bridge our development with Material angular as at the time MD3 wasn’t ready/fully released for developers.

Results
This was my first time working on a large-scale design system build. It was both challenging and a steep learning curve. It greatly expanded my knowledge of Material Design 3 and Figma. The project progresses with the launch in 2025.

ClientCGIYear2024ProjectUI & UX design