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
"That friends is service experience in the 21st century."
Ron BronsonDesign, Consequences & Everyday Life
November 18, 2022
"Rosenverse Gold now includes a streamable library of Rosenfeld books, which we think is pretty cool."
Louis RosenfeldYou’ve got Gold! A Rosenverse demo with Lou Rosenfeld
June 9, 2026
"Our role shifted toward building communities that tackle common challenges and build a robust ecosystem."
Laura Smith Tom GaylerEmbedding Service Design and Agile Practice within UK Planning Teams to Create Services that Last
December 3, 2024
"I am sick and tired of other people telling us what our role is without having done the work."
Jemma AhmedTheme 2 Intro
March 26, 2024
"Roadmap amnesia is real — every new thing wipes out weeks of priorities from stakeholders’ minds."
Rich MironovHow Can Product Managers and UXers Help Each Other (and Why are Product Folks so Annoying Sometimes)?
December 6, 2022
"There are many ways to compensate people, but it is not your choice—it is theirs."
Victor UdoewaRadical Participatory Research: Decolonizing Participatory Processes
March 9, 2022
"We have to slow down hiring to be more thoughtful and deliberate about who we bring on the team."
Libby MaurerTreating Diversity & Inclusion in Hiring as a Design Problem
December 5, 2019
"Sometimes the solution is obvious and doesn’t need a lot of user research time."
Aditi Ruiz Christian Crumlish Farid SabitovA PM State of Mind: Empathy Mapping Your Product Manager, Pt. 1
December 6, 2022
"It’s more dangerous to do nothing than to do something that’s not super perfect to start."
Bob Baxley Sara Asche Anderson Sharon Bautista Frank Duran Jamie Kaspszak Abbey Smalley Sylas SouzaTheme 4: Discussion
January 8, 2024
Latest Books All books
Dig deeper with the Rosenbot
What tools enable local, privacy-focused integration of smart home energy data without relying on cloud services?
What role do psychological safety and coalition-building play in surfacing invisible workplace issues?
How does framing AI as a chapter in automation history change our perspective on it?