Westminster City Coucil's design system
Learnings and challenges of building a design system for local government
When launching a new service, speed and consistency are crucial, but without the right tools, teams face inefficiencies and redundant work. I was tasked with creating a design system for Westminster City Council. Collaborating with the Research and Design team, I developed a tool that not only enhanced user experience through consistency and accessibility but also improved team collaboration and product scalability.
More than just boosting efficiency, it transformed how the team works, ensuring every new service delivers a cohesive, high-quality user experience.

Objectives and benefits
Implementing the design system reduced the design and build time of new features by 50%
This work had several objectives, focusing on team workflows and user experience:
- Standardising design elements and patterns to ensure a consistent user experience.
- Establish design and code quality standards.
- Promote accessibility and document best practices.
- Improve team communication.
- Maintain design system standards as it grows.
- Enhance design and development processes.
- Enable products to scale more easily.
Reconciliate to create
That work had never been done before, so the first challenge was reconciling multiple sources of truth and a complex tech stack with various limitations. We approached this by combining all libraries, analysing them, and creating design components that could be implemented across every tool.

Improve accessibility
Another aspect of the project was conducting an accessibility audit of the components to improve the product's overall accessibility. Visually, this involved fixing hover and focus states of focusable components, which failed colour contrast ratio tests.






Before and after
Here is an example of before and after the design system was implemented. These screenshots show the entry points for six different services. They were visually inconsistent, but more importantly, their user experience and behaviour patterns differed, creating friction for users and adding unnecessary effort for the product team.


Documenting the design system
Once the first iteration of the design system was created, the next challenge was making it accessible to the wider team and presenting it across the organisation for adoption at scale. After the design phase, I created comprehensive documentation on Confluence, detailing how to use the library and outlining accessibility and usability best practices for each component and pattern.
We also developed a digital guidelines document to share the design system with external stakeholders. Check out the document for a preview of these guidelines.
Related projects
Blockchain consultancy website
Website redesign to improve brand recognition, SEO scores and accessibility