Resilient Enterprise Design
Summary
What is resilient enterprise design, and how can you incorporate it into your own enterprise organization? Craig Villamor is the VP of Product Experience & Design at AppDynamics and he talks about applying context and practicality to enterprise UX design to build resiliency.
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
"You’re going to absolutely love using the Rosenbot, our chatbot, and hey, it’s free."
Louis RosenfeldHow to use the Rosenbot
March 16, 2026
"Sometimes accommodating 20% of users with special needs improves the experience for the entire 100%."
Lija HoganContexts of Use: A Framework for Connection
December 9, 2021
"Getting to know someone as a person first—the vibe check—is the first step to successful UX research collaboration."
Rachael Greene Alison DavisBuilding a Design Ops Practice that Really Works (Most of the Time)
October 2, 2025
"We’re not celebrating failure. Failure sucks. We’re celebrating the attempt and boldness."
Dan WardFailure Friday #1 with Dan Ward
February 7, 2025
"Teaching others through hands-on projects and training sessions creates long-term advocates and grows your design footprint."
Stephanie WadeBuilding and Sustaining Design in Government
December 8, 2021
"In 2019 and 2020, established design ops teams were incredibly rare; now they’re the number one response."
Bud CaddellTheme 2 Intro
September 30, 2021
"We had a great depth of customer understanding, but our view of partners was two-dimensional; we didn't know their needs or goals well."
Mac SmithMeasuring Up: Using Product Research for Organizational Impact
March 12, 2021
"We hired a digital recruiter not to become a designer, but to bridge gaps between design and recruiting."
Jose CoronadoFrom Zero to Hero
September 8, 2022
"Creating one adopted component can be harder than creating a hundred that never get used."
Nathan CurtisDesign Systems for Us: How Many One-Source(s)-of-Truth Are Enough?
January 17, 2019
