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
"There wasn't much attention paid to onboarding team members—not the clients or users, but the actual team."
Tanya SnookDesigning the team experience: Building culture through onboarding
November 4, 2021
"Feature roadmaps are bad because over time coherent actions become noise."
Adam ThomasSurvival Metrics – Making Change in a Fast, Data-Informed, and Politically Safe Way
December 6, 2022
"Our work doesn’t always correspond to its actual use once it goes out into the world."
Cassini Nazir Meah LinThe Dangers of Empathy: Toward More Responsible Design Research
March 27, 2023
"WCAG does not apply to native mobile apps, which is how slow progress can be on this topic."
Megan Clegg Michael Haggerty-Villa Alexis MorinSpace for Everyone: Reframing Accessibility Through a Wider Lens
June 10, 2021
"Government cannot be the only solution—we needed community groups, nonprofits, and for-profits all involved."
Kyria Stephens Marlon KernerPower to Heal: Civic Design in the Aftermath of Tragedy
November 17, 2022
"AI-generated imagery feels too shiny and perfect — unlike the human-made objects that carry flaws and presence of the maker."
Uday Gajendar Adam RichardsonFrom AI to Zeitgeist: Theory as the design antidote to AI hype
March 27, 2025
"That unit there is kind of like a sprint."
Jim KalbachJazz Improvisation as a Model for Team Collaboration
June 4, 2019
"For the first time, I was able to advocate for funding directly for the research function at high executive levels."
Nalini KotamrajuResearch After UX
March 25, 2024
"We must be explicit about what we mean when we say collaboration or rigor to avoid vague expectations."
Julie Norvaisas Pert Eilers Mina JonssonBack to basics, or start from scratch?
March 12, 2025
