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
"They walked. The locals were most likely right."
Brendan JarvisFraming Tomorrow by Questioning Today
June 8, 2022
"Routine shapes how we collaborate—different teams have their own habits and we need to learn to dance together differently."
Séamus ByrneAligning Teams with Choreography
January 8, 2024
"I am one of the lucky ones. I have not lost my job this year and I get to work on inclusion and accessibility every day."
Saara Kamppari-MillerTheme Three Intro
October 4, 2023
"Keeping something cloud-based accessible is the most complicated because of hundreds of releases per day in continuous integration."
Sheri Byrne-HaberAccessibility at Scale
June 9, 2021
"If our body doesn’t feel safe, or we can’t share emotions, we won’t be able to think or do work effectively."
Alla WeinbergHow to Build and Scale Team Safety
January 8, 2024
"We need to end the reign of features and complexity—too much time making stuff, not enough using it."
Chris Geison Cristen Torrey Eric MahlstedtWhat is Research Strategy?: A Panel of Research Leaders Discuss this Emergent Question
March 4, 2021
"Our responsibility is to help make digital channels work really well and in a humane, appropriate way."
Leah BuleyClosing Plenary: The Crisis of Digital
March 31, 2020
"Flexible Lego block operations let you build the shape you need when and how long you need it."
Kate Towsey Jake BurghardtResearchOps AMA with Kate Towsey & Jake Burghardt
October 16, 2025
"You want to ask an LLM to evaluate the fuzzy stuff because there’s no black and white output."
Peter Van DijckHands-on AI #2: Understanding evals: LLM as a Judge
October 15, 2025
