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
"We are like three legs of a chair: product, engineer, and UX all contribute to stability."
Product and Design at Bloomberg: A 15-year Evolution
December 6, 2022
"There is no one size fits all solution for screen readers."
Sam ProulxUnderstanding Screen Readers on Mobile: How And Why to Learn from Native Users
March 27, 2023
"We treat foundational and tactical research differently, using more flexible structures where rigid reports don’t fit."
Matt DuignanHITS, Microsoft's internal human insight system: From research library to living body of knowledge
July 16, 2019
"We found a three percent decrease in time to market using our design system, which translates into measurable business savings."
Gonzalo GoyanesDesign ROI: Cover a Little, Get a Lot
September 8, 2022
"There are competing variants in UX adoption like competing virus strains that can slow down change."
Scott PlewesWhy Isn't Your UX Approach Going Viral?: A Mathematical Model
March 28, 2023
"Selection bias, overgeneralization, data variability, and time constraints are common challenges to synthesis."
Katie HansenFinding the unknown in the known: Harnessing meta-analysis and literature review
March 12, 2025
"People crave real connection, but not forced fun or extra Zooms—so we embed play into existing meetings."
Shipra Kayan Tess DixonHow Tess Dixon Facilitates Team Engagement and Collaboration at Condé Nast Using Miro
October 1, 2021
"We created a change log to document roadmap and user story map updates due to evolving requirements and regulations."
Laureen Kattan Julie KimCentering Patients and Clinicians in a Complex Government Ecosystem
November 29, 2023
"How am I supposed to do that? is a good question to reflect impracticality without defensive triggers."
Joshua GravesWe Need To Talk: Managing Ludicrous Requests at Work (Part 3 of 3)
May 12, 2025
