The document describes the journey of a large fintech company to develop an internal design system over several years. It started with an initial HTML/CSS system in 2015-2017 that was difficult to use and maintain. In 2019, they began a new effort with guiding principles like treating the design system like a product and building community. This led to improvements in adoption, onboarding and future-proofing. While challenges remain, moving toward a design system platform could help scale and support tools, engagement and reuse of components across products. The process requires ongoing work and faces many challenges.
4. 4
4
@amir_ansari @webdirections
The design system team
19 product designers, researchers and UX writers
1.5 UI designers
~ 600 product engineers
2 Sponsors (Me and CTO)
1 Product Manager
1 Engineering team lead
5 FE engineers
0.5 UI designer
Rest of the business
As of April 2023…
13. 13
13
@amir_ansari @webdirections
As the team, looked back,
they felt there had to be a
better way!!!
So we decided to start
again, from the bottom up
(pun intended!)
21. 21
21
@amir_ansari @webdirections
Guiding principles
● Treat it like a product
● Build community, break down silos
● Ease onboarding and adoption
● Future proof
Strategic priority
Consistent use of Iress Design
System (IDS) allows us to deliver
high quality experience at scale.
23. 23
23
@amir_ansari @webdirections
● More assets to maintain
● Team capacity
● Gap between design and dev
● Competing with product roadmaps
● Web components
● ROI
Unresolved challenges!!!
27. 27
27
@amir_ansari @webdirections
Product
● Ownership
● Governance
● Dedicated team
Scale
● Support tools
● Engage and collaborate
● Skin in the game
Community
● Right tech choices
● Ways of working
● Building blocks
Key takeaways