Lyft's Product Language
Lyft's Product Language (LPL) is a multi-platform Design System with 98% product adoption within Lyft's consumer and internal applications. Led by the Design Systems team, the LPL team is a remote and virtual team of up to 11 members, supporting hundreds of developers and designers.
LPL's quality standard is exceptionally high, with WAG 2.0 accessibility compliance, exposing hundreds of components for each platform (iOS, Android, and Web), and mostly bug-free.
I worked part-time with the LPL team for one year and a half, investing around 20-40% of my time. During that time, I did the following:
- Influence the team roadmap and focus by grooming the backlog, surveying users, proposing, and getting buy-in on critical projects like a demos improvement, dropdown rework, and an impact and adoption dashboard.
- Increase developer productivity for the team and contributors by adopting quality code standards (testing, type safety, documentation) and updating tooling (test coverage tracking, code and commit linting, commit hooks, dependencies).
- Onboard contributors, giving technical support.
- Own and ship new components.
One of the outcomes I am most proud of was shipping a complex and accessibility-compliant Date Picker component suite (calendar, date picker, and date range picker). This component increased the efficiency and product consistency of 29 teams and was used 81 times, creating substantial time savings for the Frontend team at Lyft.
I also helped meet industry standards of WCAG 2.0 and elevated the a11y best practices for all frontend engineering and 98 web products by leading a rework initiative of 10 components with our a11y consultant. The team raised the Design System's perceived value from 79% to 84% of "strongly agree" during my time.