In the Design system team is aligning the look and feel across all business platforms.
/About the project
The Royal London Design System brings together a scattered design language, creating consistency without stifling creativity. It’s a work in progress—constantly evolving to meet the needs of different teams. By stepping away from a rigid front-end framework, the system becomes more adaptable. Of course, this means balancing flexibility with control—a challenge that requires ongoing tweaks and collaboration. It acts as a shared foundation for designers and developers, making prototyping easier and UI components more consistent. But adoption takes time, and ensuring it genuinely supports everyone’s workflow is an ongoing process. My work spans governance, component architecture, design tokens, and process optimisation—constantly refining the system to make it genuinely useful rather than just another set of rules.
/Challenge
Future-proof flexibility
We remove reliance on a single front-end framework, ensuring the system adapts to different tech stacks with ease. Of course, flexibility comes with its own set of challenges—balancing innovation with stability isn’t always straightforward. But by prioritising adaptability, we create a system that evolves rather than becomes obsolete.
One unified system
Creating a single source of truth helps eliminate inconsistencies and speed up design decisions—but it’s not a magic fix. Getting teams to trust and adopt the system takes ongoing education, feedback, and iteration. It’s a constant process of refining and proving its value.
/Intro points
Future-proof flexibility
We remove reliance on a single front-end framework, ensuring the system adapts to different tech stacks with ease. Of course, flexibility comes with its own set of challenges—balancing innovation with stability isn’t always straightforward. But by prioritising adaptability, we create a system that evolves rather than becomes obsolete.
One unified system
Creating a single source of truth helps eliminate inconsistencies and speed up design decisions—but it’s not a magic fix. Getting teams to trust and adopt the system takes ongoing education, feedback, and iteration. It’s a constant process of refining and proving its value.
Interactive
/Lessons learned
Design systems aren’t just about tidying up UI—they’re about making work smoother, removing roadblocks, and helping teams move faster without cutting corners. This project is a great reminder that collaboration, real-world testing, and a bit of data-driven decision-making make all the difference. More than anything, it shows how a well-maintained design system can be the backbone of digital products, keeping everything consistent without stifling creativity.
