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
"Development requests were often pragmatic—shadowing, mentoring, and reviewing—not big training courses."
Shaping design, designers and teams
November 8, 2018
"Bringing design on an equal eye level with technology and business is the starting point."
Sabrina Mach Nina WainwrightHow to Design Your Design Operating Model
September 29, 2021
"Disability isn’t a problem with a person; it’s something that happens when we fail to enable them."
Samuel ProulxInvisible barriers: Why accessible service design can’t be an afterthought
December 3, 2024
"Meeting designers where they spend their time and integrating accessibility into their tools is the most effective way to drive adoption."
Saara Kamppari-MillerDesignOps for Inclusive Design and Accessibility (Videoconference)
May 26, 2022
"I simply asked the team about their strengths and needs instead of figuring it all out on my own."
Briana ThomasThe Quiet Force: Uncovering Hidden Leadership in High-Impact Design Teams
September 24, 2024
"Don't be cool, be good—work hard at managing your teams because they need you to nail it."
Adam Cutler Karen Pascoe Ian Swinson Susan WorthmanDiscussion
June 8, 2016
"I’m hoping that once we figure this out, I can kind of go back to my old goal and break those rules."
Operationalizing DesignOps
November 7, 2018
"I don’t even use the word UX or user experience with clients if I can help it. Jargon is a barrier."
Leah Buley Joe NatoliAsk Me Anything with Leah Buley and Joe Natoli, co-authors of The User Experience Team of One (2nd edition)
October 8, 2024
"Strategy should be continuous, circular, and evolve with every action the organization takes."
Nathan ShedroffDouble Your Mileage: Use Your Research Strategically
March 31, 2020