DesignOps without Boundaries: Building More with What You Have
Summary
What happens when your design tools can’t keep up? We’ll share how we’ve helped teams scale complex design systems—without buying new tools—by building custom solutions that integrate directly into existing workflows. Learn how a flexible, API-driven approach can streamline operations, adapt to unique challenges, and scale with your needs. Leave with practical strategies for overcoming tool limitations and driving continuous improvement in your DesignOps practice.
Key Insights
-
•
Large B2B enterprise products with dozens of sub-products require robust, scalable design ops practices to maintain consistency.
-
•
Legacy design systems from acquisitions often create messy, bloated Figma files and inconsistent component usage.
-
•
Figma's native variable mode limit of 40 is inadequate for complex needs like multiple devices, themes, and generational differences, requiring innovative workarounds.
-
•
A three-layer variable structure—foundation, themes, and product design system files—enables scalable management of colors, typography, and other primitives.
-
•
Clear documentation and a unified workspace with well-managed access reduce onboarding time and design inefficiencies.
-
•
Neuron’s custom 'variable sync' tool uses Figma’s REST API to push and pull variable data, syncing design tokens directly with Storybook and front-end JSON repositories.
-
•
Batch editing and moving variables without breaking dependencies is critical for efficient rebranding and theme management.
-
•
Managing design systems as federated yet centralized processes with controlled points of change improves coordination between design and engineering leads.
-
•
AI-driven generation of production-ready React components from Figma files, shown in a follow-up session, indicates a maturing bridge between design and code.
-
•
Internal R&D time, as emphasized by Alex Kirche, is essential to develop sustainable design ops processes that work across multiple teams and projects.
Notable Quotes
"It’s often large B2B enterprise products that really warrant the most from some robust design ops practices."
"Even the most mature organizations tend to be on the nascent end of design ops maturity, and that leads to duplicated work and inconsistent user experiences."
"They really needed to take a serious look at their 500 plus variables and get better about their collections."
"Figma natively only allows 40 variable modes, but our client required around 90 different modes to handle age groups and device types."
"The variable sync tool we built is not a commercial product; it’s a utilitarian sync layer to overcome Figma’s limitations and connect design to engineering."
"Changes made in this sync tool migrate to Figma and vice versa, enabling a federated push-pull system managed by design and engineering leads."
"Batch edits allow updating multiple variables at once and moving them between design systems without losing their connection to the foundation file."
"Having a single workspace for the branded house makes it easier for designers not to dip and dive between spaces, reducing complexity."
"Alex has been instrumental in setting the internal standards, and many team members have adopted his approach for consistency."
"Using AI tools like Cursor to create React components from a well-documented Figma file helps close the gap between design and code."
Or choose a question:
More Videos
"We had 24 different consent scenarios but wanted to avoid a 15-page form that scares participants."
Theresa MarwahHow Atlassian is Operationalizing Respect in Research
February 27, 2020
"Most categories are fuzzy; there’s no clear boundary between what’s in or out."
Peter MorvilleThe Architecture of Understanding
May 13, 2015
"If you wait for permission, you will probably never be granted it. Just start doing what you know to be the right thing."
Lori Muszynski Peter MerholzKeeping Design Weird
October 2, 2023
"Listen hard, change fast."
Jacqui Frey Dan WillisPanel Discussion: Integrating DesignOps
November 7, 2018
"Scaling change starts at the margins and ripples from the periphery into the center of a system."
Hana NagelTurning Research Ripples into Waves
November 8, 2018
"We’re entering an information era because information itself is infrastructure and has actual monetary value."
Bram WesselEnterprise Information Architecture
January 10, 2020
"Onboarding is critical; the first five minutes an engineer spends working with a system defines their experience."
Nathan CurtisDesign Systems for Us: How Many One-Source(s)-of-Truth Are Enough?
January 17, 2019
"There’s a new tech stack for software creation, all about cloud services and subscription-based business models."
Greg PetroffSoftware as Material—A Redux
June 6, 2023
"Order today is change, and the uncertainty that it brings rules us day and night."
Jon FukudaTheme One Intro
October 2, 2023
