Discussion
Summary
In this session, Sam, Frederick, and Russ explore the complexities of enterprise design and product development. They stress beginning with personal hypotheses and proving them right or wrong, as Sam advocates starting with oneself. Society-wide culture change, rather than just design work, is central to successful enterprise transformation, noted especially by Sam and reinforced by others referencing the role of art, comedy, and social networks. Frederick highlights the challenge of delivering complex system improvements under tight time constraints, advising honesty and aligning project scope accordingly. The panel discusses the tension between radical and incremental innovation, with Sam emphasizing that most changes occur through networked connections rather than disruptive reinventions, though radical innovation requires culturally ready organizations, as noted with Honeywell's example. Russ explains how large audiences, like federal agencies, can adopt shared style guides while retaining customization for their unique needs. The importance of managing legacy systems alongside future-focused teams is highlighted, with the Atari example illustrating structural separation benefits. The panelists warn about technical and organizational debt as long-term obstacles. Sam underscores that culture trumps strategy and suggests embedding user experience improvements into an organization's social fabric, using regular communication channels to build momentum. Overall, the talk stresses that enterprise UX requires patience, cultural sensitivity, incremental progress, and a networked approach to change.
Key Insights
-
•
Start enterprise design projects with yourself to form testable hypotheses before engaging others.
-
•
Enterprise UX work is often more about culture change than just design or technology.
-
•
Transparency about time constraints and realistic scope is crucial when organizations demand rapid delivery.
-
•
Radical innovation in enterprise requires a culturally ready organization; otherwise, incremental improvements are more feasible.
-
•
Complex legacy systems require maintaining separate teams focused on current operations and future innovation to avoid stagnation.
-
•
Technical and organizational debt are major causes of prolonged pain during system migrations or upgrades.
-
•
Shared design standards can coexist with agency-level customization to balance familiarity and unique needs, as Russ explains with 18F.
-
•
Users can derive a sense of status or accomplishment from mastering complex legacy systems, making change socially challenging.
-
•
Embedding UX progress into an organization involves building strategic support and grassroots momentum through social networks and storytelling.
-
•
Measuring software like employee performance—reviewing and retiring underperforming systems—is essential to avoid wasted resources.
Notable Quotes
"Start with yourself. It’s a great place to get a hypothesis, and then prove yourself wrong or right."
"What we underestimate is that enterprise work is essentially culture change, not just design work."
"Do what you can, where you are, with what you have — that’s how you show you can deliver."
"Only work with companies willing to invest the time required; otherwise, deliver what you can and be honest about it."
"Radical innovation isn’t the main form of change; the main form is connections, like open APIs with massive downstream effects."
"If you create a separate team to work on the future, make sure they stay focused on the future, or you’ll never get out of the trap."
"The moment you spend more on maintaining legacy than creating the future, you’re probably doing the wrong thing."
"Users sometimes enjoy the complexity of old systems because mastery grants them elite social status internally."
"Culture trumps strategy. When culture derails your best plans, you need both strategic air cover and grassroots momentum."
"Building a distribution list of user-centered design success stories created a groundswell with 1,200 subscribers hungry for more."
Or choose a question:
More Videos
"The 'stay in your lane' mentality is a red flag signaling silos and turf protection instead of cross-functional collaboration."
Frances Yllana Kaaren Hanson Husani Oakley Dan OlsenDesignOps Exposed: What do our peers really think of us?
September 11, 2025
"Nudge to me now is much more about wiggle it and see what happens rather than expecting exact outcomes."
Jen BriselliLearning Is The Engine: Designing & Adapting in a World We Can’t Predict
April 16, 2025
"Safety is a state of our nervous system, when our autonomic nervous system is in a safe state, we feel connected."
Alla WeinbergDesign Teams Need Psychological Safety: Here’s How to Create It
September 9, 2022
"Communicate as much as possible and in different formats, because different formats resonate differently with people."
Michelle ChinThe DesignOps Starter Kit
September 29, 2021
"AI development is often uninformed and hurried, resulting in deployments that don’t operate well in the real world."
Joel BranchHumanizing AI: Filling the Gaps with Multi-faceted Research
March 11, 2021
"It is impossible for one research ops person to do all the things expected in job descriptions."
Kate TowseyAsk Me Anything (AMA) with Kate Towsey
April 2, 2025
"Our cities are at a tipping point, and we need actionable, sustainable solutions."
Alex Hurworth Bonnie John Fahd Arshad Antoine MarinDesigning a Contact Tracing App for Universal Access
October 23, 2020
"I am usually the only designer on the team, and it gets difficult to get the information needed for design decisions."
Ruzanna RozmanGetting in Flow with Your Team
January 8, 2024
"If we don’t get good experiences in the workplace, we’re going to beat the system and go get products that actually help us do our jobs."
Catherine CourageThe Enterprise UX Journey: Lessons From the Voyage & The Opportunity Ahead
May 13, 2015
