While sharing visuals of the Providence Design System and its paired documentation site is against Fidelity's content sharing policy, I can speak to some of the responsibilities as a lead designer on the Providence team.
Some of those responsibilities include:
- Audit new product work in flight
- Propose and scope new components and features
- Work with engineers to define component API
- Write, review, and publishing technical documentation
- Work with accessibility and write guidelines
- Refine processes of our Agile centralized team
- Community support
- Facilitate working groups with the community
- Steward community contributions
- Build and maintain a complex Figma library
- Design visual language and produce guidelines
- Collaborate with corporate marketing to create illustration guidelines

The system also saw data-backed success in driving speed to market increases, reusable component availability, and visual style cohesion across a multi-business unit enterprise.
Some of those successes include:
- Cost avoidance in excess of $5.3m in 2020
- Increased testing and support to meet Fidelity's Accessibility Requirements without the need for consuming-team-level adjustments
- An overall 5.92 (out of 7) overall satisfaction on the initial release of the firm's first cross-business-unit unified system
- An increasing month-over-month install rate of 10k+
- An adoption rate increase from 200 (based on 2018 data of PVD2's single-business-unit scope of service) to 1400+ (based on 2020 data of cross-business-unit scope of service)
System Evangelism
Mark Steinruck and I co-presented during a Figma "In the File" session on governing design systems. See the recording below.

You may also like

Back to Top