Summary
Dave, leading a 50-person UX team at GE Software, recounts the development of a design system aimed at solving the massive scale and decentralized nature of GE’s software efforts. Starting in 2011 with only a few UX designers amidst thousands of developers, Dave and his team collaborated with Frog Design to create a modular, Lego-like kit of UI components that prioritized ease of use over strict design rules. Inspired by design systems from NASA, Apple, and Braun, they built a visual language and reusable components to accelerate development and enable teams without extensive UX resources to produce usable, consistent interfaces. Despite some initial challenges like lack of clear usage guidelines, multiple competing UI patterns, and engineering complexities, the system gained wide adoption within GE, eventually spawning variants such as a communications and healthcare design system. The team also focused on prototyping tools, co-creation workshops, and integrating design deeply with product teams under emerging lean startup culture promoted by leaders like Beth Comstock. Dave highlights lessons learned including the importance of continuous evolution, community contribution, and balancing creative craft with organizational scale. The talk closes with reflections on craft as active collaboration and prototyping, rather than pixel perfection, centered on solving complex industrial data visualization and user needs.
Key Insights
-
•
GE’s software efforts in 2010 surprisingly ranked it as the 15th largest software company, yet UX design resources were extremely limited.
-
•
The initial UX team at GE was too small to directly influence all 40,000 developers, pushing the need for a scalable solution.
-
•
The design system concept was inspired by industrial design legacies like Braun, NASA, and Apple's human interface guidelines.
-
•
The team adopted a tools-not-rules mantra to create a modular 'Lego' kit of UI parts aimed at broad developer adoption.
-
•
Successful adoption was boosted by providing code-first deliverables, along with stencils for designers and PMs for fast prototyping.
-
•
Multiple UI patterns for the same controls caused confusion and difficulty in maintenance, motivating a system redesign.
-
•
The design system catalyzed a cultural shift at GE Software towards integrated, cross-functional teams with embedded UX.
-
•
Variants of the design system were created for different GE domains, such as healthcare and communications, preserving core modularity but catering to unique needs.
-
•
Challenges included balancing opinionated interaction patterns versus flexibility, and technical difficulties extending frameworks built on large CSS libraries like Bootstrap.
-
•
Craft evolved from pixel-level perfection to co-creation workshops, storyboarding with simple tools, and rapid prototyping to align complex industrial IoT users and stakeholders.
Notable Quotes
"GE was something like the world’s 15th biggest software company, which was a huge surprise to everyone."
"We landed on this mantra of tools, not rules."
"If we made something that was really easy for developers to use, we would drive adoption."
"We didn’t know enough to have a strong opinion about what was good design and what wasn’t good design for these particular users."
"We found that multiple kinds of tabs confused users and complicated maintenance; at most, we need one kind of tab."
"We built a modular, adaptable space solely for co-creation and bringing in customers and stakeholders."
"Part of craft now is how we conduct co-creation workshops to form shared understanding and vision."
"Some of the best investments were making stencils for designers and product managers to quickly mock up ideas."
"People went from whiteboard to high fidelity prototype very quickly, which was both cool and a bit scary."
"We’re learning how to pay our designerly affection to the design system so we can prototype new ideas and have great conversations."
Or choose a question:
More Videos
"We want teams to have autonomy and power to make pivot, shelve, and proceed decisions, not leadership dictating."
Standardizing Product Merits for Leaders, Designers, and Everyone
June 15, 2018
"I realized I was just making it up despite the company’s growth."
Simon WardleyMaps and Topographical Intelligence (Videoconference)
January 31, 2019
"Bias is a tendency, feeling or opinion for or against something without reason or evidence."
Sandra CamachoCreating More Bias-Proof Designs
January 22, 2025
"By observing, appealing to interests, and promoting accountability, we can build empathy and respect to combat toxicity."
Darian DavisLessons from a Toxic Work Relationship
January 8, 2024
"ChatGPT didn’t have the full context of what was most important to stakeholders, so I had to edit its output before sharing."
Fisayo Osilaja[Demo] The AI edge: From researcher to strategist
June 4, 2024
"Empowering maker culture invites everyone to be part of a collective endeavor far beyond any individual."
Uday GajendarThe Wicked Craft of Enterprise UX
May 13, 2015
"Trust is often underestimated but is critical when designers face public critique and feedback."
Davis Neable Guy SegalHow to Drive a Design Project When you Don’t Have a Design Team
June 10, 2021
"You won’t know what success looks like until you put something out there and see how it works in practice."
Eniola OluwoleLessons From the DesignOps Journey of the World's Largest Travel Site
October 24, 2019
"Design leaders want predictable roadmaps and healthy teams, measurable against timelines and goals."
Aurobinda Pradhan Shashank DeshpandeIntroduction to Collaborative DesignOps using Cubyts
September 9, 2022
