Design System Library


Prudential Global Theme and Design System Website were a great success and I took advantage of this momentum to propose building a dedicated team and treat Design System as a product.



  • Ensure the best user experience by providing quality built and accessible components
  • Increase the speed of delivery
  • Foster a culture of collaboration
  • Build a global component library
  • Framework Agnostic
  • WCAG 2.0 AA compliant
  • Starter Project
  • Easy enough use by an intern

My Role

  • Built and led a team of designers and developers
  • Project Owner
  • Scrum Master
  • UI Design
  • Art Direction
  • Development
  • Evangelism


  • No global component libraries
  • Lack of collaboration
  • No quality standards or code documentation
  • No front-end architecture
  • Adoption

User Interface Audit

We began by conducting an audit of existing components and patterns finding any redundant combinations and merge duplicates.

Developer Experience (DX)

In order for the library to succeed we ensured developers had a great experience. To accomplish this, we determined what made a successful library by conducting several developer interviews and competitive analysis.

Attributes of a great library are detailed documentation, concise release notes, changelogs, consistency, ease of use and open source frame of mind.

Design System Website properties switcher allows the developer to toggle wanted configuration of a component and copy snippet.


Using Codepen integrated with our theme and SASS variables we conducted smoke tests for modularity, accessibility, and responsiveness.

Test compilation video
Link timeline cards test.
Authenticated cards test.
Range Slider testing multiple themes.
Global Footer test.

Time to Build

We focused on build quality, not quantity, we took time to thoroughly test and document. Often functional accessibility was the most complicated and time-consuming process, sometimes going way past sprint deadlines.

We created a monorepo which included a sandbox and component library.

Continuous Integration and Continuous Delivery

The team Automation Engineer implemented full integration into the CI/CD pipeline. Some highlights were:

Docker-based container first development.
Full integration with CI/CD pipeline.
80% Code coverage.
Supplemental auto generated documentation via Compodoc.

Promote Collaboration and Contributions

One of the most prominent team goals I set was to change existing siloed culture by introducing a collaborative workflow, promoting the benefits of a global library, conducting workshops, and general pair programming.

Adoption and Evangelism

Evangelized a collaborative workflow.
Conducted workshops in New Jersey, California, and Ireland.
Fostered culture of collaboration by conducting regular workshops and facilitated bi-weekly public forums.


  • Built & published 40+ components
  • Decreased development time up to 45%
  • Decreased onboarding time at least by 50%
  • Enhanced documentation
  • Fully 100% Accessible WCAG 2.0 AA compliant
When running the Design System Library project a Developer Sandbox website is generated to preview components as they get built.