As adoption of the Sequoia Design System increased, so did the complexity of maintaining it. Teams were contributing new components, requesting enhancements, and building reusable solutions, but the process for doing so varied from team to team. I worked across design and engineering to establish a scalable operating model that defined how work entered the system, how it was evaluated, and how updates were communicated back to the organization. The goal was to move beyond maintaining components and create a system that could support long-term growth.
Problem
- →Design system contributions were handled inconsistently across teams.
- →Documentation, ownership, and review expectations were not always clear.
- →Updates and new capabilities were difficult for consumers to discover.
- →Product teams often solved similar problems independently instead of building on shared solutions.
Goals
- →Create a repeatable contribution and governance process.
- →Improve alignment between design and engineering.
- →Increase visibility and adoption of design system resources.
- →Establish a foundation that could scale with future web and mobile products.
Process
Understanding How Teams Worked
I reviewed how new components, enhancements, documentation updates, and accessibility improvements moved through the organization. The goal was to understand where decisions were being made and where teams experienced friction.
Defining an Operating Model
Rather than creating additional process, I focused on establishing clear paths for intake, review, implementation, documentation, and release. The model needed to support designers, engineers, and product teams without becoming a bottleneck.
Improving Visibility
A recurring theme was that teams often weren't aware of new capabilities. I expanded documentation efforts and introduced recurring design system announcements and release communications to make updates easier to discover.
Solution
Governance & Contributions
Created a formal contribution model that defined how components, enhancements, bug fixes, and documentation updates entered the system and moved through review.
Documentation & Storybook
Expanded component guidance, implementation documentation, accessibility recommendations, and design system resources. Continued improving Storybook as a source of truth for implementation guidance and component behavior.
Adoption & Communication
Created recurring release announcements, changelog communications, presentations, and educational sessions that helped teams understand what was available and how to use it.
Cross-Functional Collaboration
Established a stronger partnership between design and engineering through shared reviews, contribution workflows, and design system planning discussions.
Impact
The Sequoia Design System evolved from a shared component library into a more mature product platform with clearer ownership, stronger documentation, repeatable contribution processes, and improved visibility across the organization. The work established a foundation that supports future initiatives, including the development of a dedicated mobile design system.