Resilient Enterprise Design
Summary
Key Insights
-
•
Enterprise design must account for complex organizational contexts, not just individual user happiness.
-
•
Resilience in design means creating systems that flex and adapt under stress rather than breaking.
-
•
Customization is essential in enterprise software for companies to express their brand, culture, and workflows.
-
•
Loss of design control due to device variety and user customization requires influence over user behavior rather than strict enforcement.
-
•
Design principles are crucial to reduce indecision and provide a clear framework for decision-making in complex projects.
-
•
Prioritizing clarity over consistency can lead to better user experience outcomes.
-
•
Successful platforms often start by solving specific, concrete problems before generalizing widely.
-
•
Design systems function as living products that maintain consistency, flexibility, and scale across an ecosystem, including users.
-
•
Making it significantly easier to do the right thing drives adoption and behavior change in design.
-
•
Modeling real-world scenarios and anticipating customization scenarios helps create resilient, flexible enterprise applications.
Notable Quotes
"In the enterprise, it’s really about make me effective taking into account non-user personas as well as the individual."
"My boss might be looking over my shoulder and see nothing but red and think I’m not doing my job."
"Designing for the real world means dealing with practical constraints and making refinements in the face of compromise."
"We’re really passionate about our craft but we’re not in control — that’s a shared hallucination we must give up."
"If you design for everyone, no one is satisfied — start with specific solutions then generalize."
"The highest paid person’s opinion, or HIPPO, often makes decisions in the absence of principles and insights."
"Make it difficult to create ugly presentations — make it ten times easier to do the right thing."
"What happens when a user customizes the UI? Does the experience break? This is the question to ask."
"A style guide is an artifact, but a design system is a living, funded product with a roadmap serving an ecosystem."
"Resilient design needs to bend without breaking — to survive stresses while still delivering value."
Or choose a question:
More Videos
"History doesn’t repeat, but it sure does rhyme."
Patrick Neeman Jeffrey ZeldmanAgent Standards Best Viewed in Every Assistant
September 4, 2026
"The word 'requires' implies that whiteness is the default unless otherwise specified."
Alba VillamilStereotyped by Design: Pitfalls in Cross-Cultural User Research
March 30, 2020
"We have over a thousand participants from 61 countries, but remember this is only a sliver of the broader service design community."
Marc FonteijnFirst Insights from the 2025 Service Design Salary(+) Report
December 4, 2024
"We made it a priority from day one to support data exports so customers can leave without wasting weeks migrating data."
Sofia QuinteroThe Product Philosophy Behind EnjoyHQ
March 10, 2021
"Junior people are often afraid to ask questions because they don't want to look dumb."
Louis RosenfeldGenAI for UXers: A Rosenbot Demo and Discussion
June 11, 2025
"I save the proposed tags to a CSV file so I can preview and edit them before applying the changes."
Jorge Arango[Demo] How to re-categorize content at scale using LLMs
June 5, 2024
"If you have questions for the speakers, put them in Slack under the associated thread."
Bria Alexander Louis RosenfeldOpening Remarks Day 2
March 26, 2024
"Being able to see faces and first names of people we're learning from makes those users tangible to the team."
Catherine DubutBridging Physical and Digital Spaces: Approaches to Retail Service Design
March 18, 2021
"Nordstrom decided that innovation needed to be a corporate value, not a lab value."
Jeff GothelfInnovation Studios: the Engines of Enterprise Experimentation
May 14, 2015