Thomson Reuters Saffron Design System
Scaling adoption with people, not just pixels
Role: Lead UX Designer, design system team
Duration: 2023 - ongoing
Focus: Adoption, community building, design ops
The challenge
As the design system began to mature, a small centralized team faced an impossible task: scaling support and adoption across dozens of product teams in a global enterprise. Product designers needed help implementing components, guidance on patterns, and a voice in roadmap decisions, but the design system team couldn't be everywhere at once.
How do you scale a 5-person design system UX team to support [50+ product teams] without sacrificing quality, responsiveness, or strategic influence?
Key pain points
For product designers: Isolated problem-solving meant teams reinvented solutions others had already built. No clear channel to influence the design system road map or share cross-product patterns.
For the design system team: Constantly firefighting the same questions across teams. Limited visibility into real-world implementation challenges until after products shipped.
For the organization: Inconsistent adoption created fragmented user experiences. Duplicated effort across teams solving identical problems in isolation.
Success metrics
Increase cross-product pattern sharing and collaboration
Reduce time-to-implementation for new components
Establish measurable engagement and participation quality
Create sustainable program structure that prevents burnout
The approach
The strategy began with industry research into how companies like Salesforce, IBM, Atlassian, and Etsy scaled their design systems. The pattern was clear: successful programs relied on embedded advocates, not just documentation.
Analysis revealed the core insight: design systems succeed through culture and community, not just components. Ambassador programs work best when they distribute knowledge, create feedback loops, and build relationships—turning a central team into a networked organization.
Strategy & vision
The program architecture balanced three competing needs:
Scalability: Ambassadors extend the design system team's reach by becoming liaisons embedded in product teams. They answered questions, gathered use cases, and shared patterns and experiences across products.
Sustainability: Rather than relying on voluntary participation alone, the program needed formalized structure: clear time commitments, manager buy-in, and rotation models to prevent participant burnout.
Strategic influence: Ambassadors couldn't just implement the system—they needed to shape it. The program needed to create space for systems thinking development, cross-product synthesis, and design system roadmap influence.
Key initiatives
Monthly Ambassador sessions
Structured meetings became the primary collaboration forum, covering component demonstrations, pattern sharing, strategic initiatives, and open problem-solving. Sessions evolved from presentation-heavy formats to collaborative workshops where Ambassadors brought real team challenges and learned the commonalities between their products, no matter their business unit.
Formalized charter and role definition
Worked with leadership to establish clear expectations: 3-5 hours set aside for Ambassador duties per sprint, explicit ties to performance reviews, and recognition frameworks. Secured manager buy-in by positioning the role as leadership development, since Ambassadors gain systems thinking skills applicable to career progression.
Community participation model
Separated strategic work from general education by launching dual-track structure:
Weekly open "Collaboration Sessions" for all designers (design systems education and updates, pattern sharing, and Q&A)
Monthly exclusive "Strategic Sessions" for Ambassadors (deep systems thinking, roadmap influence, cross-product synthesis)
This reduced Ambassador burden as sole information gatekeepers while democratizing access to design system support and holistic product use case sharing.
Rotation and alumni network
Introduced 3-6 month terms with staggered rotation, quarterly entry points, and a tag-in/tag-out system. This updated rotation model created pathways for all experience levels (junior through lead+) and an alumni network for returning members.
Streamlined information architecture
Consolidated documentation to around 2 clicks for any resource, implemented AI-powered meeting summaries distributed to the entire design community, and created templated communication formats for consistent updates.
The solution in action
`**Visual suggestion:** Diagram showing the network effect—central design system team connected to Ambassadors, who connect to their product teams, creating web of knowledge distribution rather than hub-and-spoke support model.`
The program transformed how product teams engaged with the design system. Instead of isolated support tickets and unanswered call-outs for use cases, collaboration happened through structured sessions where Ambassadors shared how they were building their products with the design system's components and patterns.
For example, when multiple teams independently struggled with mobile table patterns, Ambassadors from three different products brought the challenge to a session. The discussion surfaced that teams were choosing between horizontal scrolling (poor accessibility) and list views (limited data density). This cross-product synthesis led to documented best practices that saved months of duplicated discovery work.
`**Visual suggestion:** Before/after comparison showing fragmented individual team work vs. collaborative pattern synthesis through Ambassador program.`
Another instance: during the development of an AI prompt component, Ambassadors from teams building AI features participated across multiple sprints by providing use cases, testing prototypes in their products, and refining functionality. This co-creation model ensured the component solved real problems across products before the release. This ensured that product end-users had a consistent AI prompt experience, no matter the products they used.
`**Visual suggestion:** Timeline or journey map showing multi-sprint co-creation process for complex component.`
Results & impact
Design system evolution
Ambassador feedback directly influenced 15+ component updates in 2025 alone. Real-world use cases shaped functionality, accessibility requirements, and documentation while cross-product alignment on token changes, visual design direction, and accessibility standards prevented fragmentation. The Ambassador program helped facilitate accelerated adoption of design system updates through embedded advocates. By having one Ambassador from every main product team in the program, this helped prevent inconsistencies by involving product teams in roadmap decisions before components shipped.
Cross-product collaboration
Teams working on similar challenges found shared solutions. This included solutions for mobile table patterns across three products, AI prompt interfaces across four teams, status indicators and badges across multiple workflows. This pattern sharing helped reduce redundant discovery work.
Systems thinking development
The program became a professional development powerhouse. During their tenure, Ambassadors learned to understand the cascading effects of design decisions, balance product-specific needs with system-wide consistency, and navigate trade-offs between brand guidelines, business demands, and usability. Overall, the program has been helping UX and product designers of all levels build skills applicable to elevated design roles.
2025 by the numbers
61 topics discussed across 42 sessions
83% of Ambassadors attending 3+ meetings after a strategic pivot in Q3 to a smaller cohort
55% longer meetings and 54% higher individual time investment in Q4 vs. Q1, indicating deeper engagement
First instances of perfect attendance appeared in Q4, validating a focused mode
Balancing quality versus quantity
However, analysis revealed that attendance didn't equal engagement. Some Ambassadors with 100% attendance showed minimal participation, while others with 50% attendance delivered exceptional value by surfacing critical cross-team challenges. This insight has been driving 2026's evolution toward measuring participation quality and individual impact, not just presence.
`**Visual suggestion:** Data visualization showing the quality-quantity gap—attendance percentage vs. contribution value scatter plot.`
Learnings & evolution
What worked well
Small, committed cohorts over broad participation: The strategic pivot from 28 participants to 12-13 highly engaged Ambassadors improved meeting quality, individual contribution, and sustained engagement. Smaller groups enabled deeper collaboration, productive discussions, and stronger relationships.
Dual-role structure: Positioning Ambassadors as both implementers and strategic influencers created investment. They weren't just learning the system, but they were shaping it.
Cross-product synthesis: The most valuable moments came when Ambassadors brought similar challenges from different products, revealing patterns the design system team couldn't see from their position and due to the siloed nature of the product organization. The Ambassador program has become a key player in breaking down silos between business units and their products.
Challenges & how they were addressed
Burnout and unclear expectations: The early iteration of the program relied on goodwill without formal time allocation or role clarity. This led to inconsistent participation and frustration for all parties invovled in the program. This was addressed through a formalized charter tha required manager buy-in, clear 3-5 hour sprint commitments, and a rotation model.
Information overload: Ambassadors felt pressure as sole information gatekeepers for their teams. This was solved by separating general education and design system updates (open to all) from strategic work (exclusive to Ambassadors).
Passive participation: Some Ambassadors attended consistently but contributed minimally, suggesting psychological safety or expectation barriers. The 2026 program introduced 1:1 monthly check-ins for candid feedback and clearer participation guidelines to address this.
Fragmented documentation: Resources for Ambassadors were scattered across multiple platforms creating friction and confusion about what was the current source of truth. All Ambassador-related documentation was consolidated into one main resource that is constantly updated.
What could be done differently
Earlier formalization: Waiting until year three to formalize the charter, time expectations, and manager buy-in created unnecessary frustration. Establishing these foundations earlier would have prevented confusion and burnout.
Measuring quality from the start: Tracking attendance without measuring contribution quality missed critical engagement issues, but future iterations establish participation metrics beyond presence.
Pilot rotation sooner: The rotation model addresses burnout and increases diversity of perspectives existed in previous iterations of the program, but no one was aware of this option. Making the rotation model a feature of the program sooner could have sustained engagement longer.