Summary
Dave, head of a 50-person UX team at GE software, recounts how they tackled massive design challenges in a huge, decentralized company by developing a modular design system. Starting in 2011 under the leadership of Greg Petrov, their team was small but ambitious, aiming to bring consistent user experiences to thousands of software developers scattered throughout GE’s vast industrial ecosystem. Inspired by traditional industrial design and presentations like Mike Lemmon’s on interaction design languages, they shifted from rigid style guides to flexible, Lego-like toolkits for design and development. Collaborating with Frog Design experts such as Robert Fabricant and Ed Hicks, Dave’s team built a broadly adopted system focused on accelerating development, enabling better prototyping, and supporting consistency without stifling creativity. They discovered that their early system needed better governance, clearer usage guidelines, and easier extensibility, especially as teams demanded variations for marketing and healthcare applications. Today, GE’s UX organization in San Ramon has scaled to 60 designers integrated into cross-functional teams, evolving their design system with richer user insights and technology improvements. Central to their craft is co-creation, rapid prototyping, and maintaining shared understanding with stakeholders, all while continuing to refine the system to support complex industrial data visualization and brand coherence.
Key Insights
-
•
GE’s design challenges stem from being a decentralized matrix with 40,000 developers but fewer than 20 UX designers initially.
-
•
The team shifted from style guides to a Lego-like design system emphasizing tools, not rules, to drive adoption among developers.
-
•
Partnership with Frog Design brought valuable expertise in creating scalable, modular design systems for GE.
-
•
The design system accelerated software development by answering recurring UI questions and providing pre-built components.
-
•
The team saw early success with nearly 20,000 downloads inside GE for the design system, signaling wide adoption.
-
•
Despite adoption, the team acknowledged weaknesses like multiple confusing tab patterns and difficulty extending the system.
-
•
Healthcare and marketing teams created variations for empathy and communication needs, showing design system adaptability.
-
•
Sketches by Hey Studio became effective co-creation tools for storytelling and aligning stakeholders around user needs.
-
•
Moving from an isolated UX studio to embedded, cross-functional teams increased design’s influence across product delivery.
-
•
The evolving craft of UX at GE emphasizes rapid prototyping, co-creation, and shared understanding over just polished visuals.
Notable Quotes
"We landed on the mantra of tools, not rules to drive adoption with developers."
"If we could make something really easy for developers, we would drive adoption and continually improve user experiences."
"We didn’t have enough knowledge initially to have a strong opinion about what was good design for these users."
"A lot of people were just going and downloading the tear sheet, which is to be expected."
"We found that different failure modes of equipment have different spatial signatures on spider web charts."
"The most important thing about the design system is that it’s already coded — designers and devs just use it."
"It’s very tempting to bypass the sketching step and jump straight to high-fidelity prototypes — proceed with caution."
"We resisted the temptation to squash diversity of usage because we thought we’d learn from it."
"Prototyping and co-creation workshops have been a huge accelerant to the design process."
"Our craft today is about forming shared understanding and building prototypes, not just delivering polished visuals."
Dig deeper—ask the Rosenbot:
More Videos
"Carol was really grateful for our conversation."
Randolph Duke IIWar Stories LIVE! Randy Duke II
March 30, 2020
"You do not have to go publicly thank the employer who just laid you off. They’ll be fine without it."
Corey Nelson Amy SanteeLayoffs
November 15, 2022
"Driver modeling tells you which research initiatives matter most based on their impact on key outcome metrics."
Landon BarnesAre My Research Findings Actually Meaningful?
March 10, 2022
"Most of my career has been in health, and it’s really important that we don’t just get people to do something once, but sustain a new behavior."
Amy BucherHarnessing behavioral science to uncover deeper truths
March 12, 2025
"With QFI, we go upstream: simulate, model, predict user behavior before shipping, not just react after."
David SternbergUncovering the hidden forces shaping user behavior
July 17, 2025
"More frequent change isn't always better; good communication and team pulse are key."
Deanna SmithLeading Change with Confidence: Strategies for Optimizing Your Process
September 23, 2024
"When the powerless get to speak freely, those in power hear what they desperately need to."
Jennifer StricklandAdopting a "Design By" Method
December 9, 2021
"We created separate tracks so people can self-organize, leverage the right skills, and grow their careers in focused ways."
Rachel Posman John CalhounA Closer Look at Team Ops and Product Ops (Two Sides of the DesignOps Coin)
November 19, 2020
"Provoking and reframing perspective helps teams get unstuck by thinking in new and surprising ways."
Gina MendoliaTherapists, Coaches, and Grandmas: Techniques for Service Design in Complex Systems
December 3, 2024
Latest Books All books
Dig deeper with the Rosenbot
What is an effective structure for organizing design variables in large multi-product ecosystems?
What does an effective omni operations model look like balancing standardized processes with domain flexibility?
What are the benefits of using component libraries in tools like Figma to maintain people maps?