Summary
An essential part of creating a Design System is to make distribution and content flow sustainable. When the task is bringing the joy and community of gaming to everyone on the planet, the challenge gets massive! How can DesignOps and Automation become a facilitator for this challenge? Join Senior Software Engineer & Designer Luca Rager from Xbox as he takes us through their innovative take on design systems. Luca will illustrate how Sketch’s flexibility and modern DesignOps automation has allowed Xbox to package, theme and easily distribute component libraries. Furthermore, how their system bridges the gap between the Xbox Design System team and the wider product teams at Xbox.
Key Insights
-
•
Xbox Design System supports four themes including high contrast to ensure broad accessibility.
-
•
The component library needed to work across multiple platforms: TV, desktop, and mobile.
-
•
Theme customization is achieved by swapping foundational Sketch libraries rather than relying on overrides.
-
•
Every component and foundation (theme file) exists as its own Sketch file to support clarity and easy iteration.
-
•
Clyde, an internal automated tool, packages components into Sketch libraries and generates design tokens for engineers.
-
•
The design system team focused on creating easy-to-adopt kits for product designers to reduce complexity and improve uptake.
-
•
Multidisciplinary team members, including designers with engineering skills, help bridge gaps between disciplines.
-
•
Accessibility experts are embedded in the design process, enriching documentation and audits within the system.
-
•
Governance balances flexibility for product teams to propose and customize components with ensuring consistency from the core team.
-
•
Integration with Microsoft tools like Azure and Teams allows realtime notifications and seamless collaboration around design system updates.
Notable Quotes
"Gaming is for everyone anywhere, and Xbox has evolved way beyond the box under your TV."
"Our mission required us to build something fast, flexible, and scalable across many different product needs."
"A button is just a rectangle with some text, but our magic is in how we theme and customize it using foundations."
"Instead of overrides, we swap out entire theme files to customize components for different product teams."
"We realized the real problem was a people problem, not just tooling complexity."
"Sketch’s open file format allowed us to build custom tooling that shapes the design data to our needs."
"Clyde runs every time there’s a change, generating libraries and tokens to keep everyone up to date."
"Engineers love having individual components in files because it makes implementation much easier."
"Design system adoption exploded when we focused on the needs of everyone who builds, extends, or uses it."
"Accessibility and research are part of our org, not just consultants, which makes a huge difference in quality."
Dig deeper—ask the Rosenbot:
More Videos
"Our dedicated scribe Shivangi is making sure all the notes are captured so you don't have to worry about it."
Bria AlexanderOpening Remarks
November 17, 2022
"We have weekly meetings with implementation teams to design APIs, discuss progress, and address issues to ensure alignment."
PJ Buddhari Nate BaldwinMeet Spectrum, Adobe’s Design System
June 9, 2021
"Priorities aren’t priorities until they’ve been prioritized with attributes and values; otherwise they’re just items."
John Cutler Harry MaxPrioritization for designers and product managers (1st of 3 seminars)
June 13, 2024
"We created a change log to document roadmap and user story map updates due to evolving requirements and regulations."
Laureen Kattan Julie KimCentering Patients and Clinicians in a Complex Government Ecosystem
November 29, 2023
"If you don’t get good guidance and feedback from your enterprise partner, you’re not going to do the best work possible."
Melinda BelcherBridging the Gap: Making the Most of the Differences Between Agency and Enterprise
January 8, 2024
"When you’re passionate about a topic, you hear the song loudly in your head; the listener just hears clapping."
Janaki KumarInnovate with Purpose
June 14, 2018
"For me, ideally one design ops manager per 14 designers is the ratio that works best."
Benjamin RealShowing the Value of DesignOps by Not Having a DesignOps Team
October 21, 2020
"Polaris was not just a database but a system involving humans and a strong curatorial role."
Michele MarutResearch Repositories Reconsidered
February 14, 2019
"There are values that have really stood out to us together: evolving, relational, decolonized, life centered, healing, equitable."
Sarah BrooksTheme 3 Intro
December 10, 2021
