The Big Question about Resilience: A panel discussion
Bria Alexander
DesignOps Curator
Laura Gatewood
Lead Design Program Manager, Central DesignOps, Salesforce
Corey Long
Senior Manager, Design Operations, Adobe
Daniel Orbach
Executive Director of Design, Small Business Credit Card, JP Morgan Chase
Laine Prokay
Principal Design Program Manager, Salesforce
Deanna Smith
Design Program Manager, Adobe Design
Summary
What’s the most important question regarding today’s theme of resilience that we, as a community, need to address? We’ve asked you, you’ve spoken—and now we’ll tackle it with the aid of Bria and some of today’s speakers.
Key Insights
-
•
Resilience in design ops hinges on a flexible mindset and excellent communication within teams (Danielle).
-
•
Kindness and a focus on the experience of people keep teams adaptable and less 'dried out' in changing environments (Laura).
-
•
Influence, built through empathy and demonstrating benefits, is key to design ops success, especially in small teams (Corey).
-
•
Energy management is more critical than time management for sustaining wellness and productivity (Lane).
-
•
Viewing feedback as objective data rather than personal criticism aids resilience and continuous improvement (Deanna).
-
•
Explicit behavioral modeling and communication of norms support personal and professional resilience in teams (Charlotte and Daniel).
-
•
Balancing energizing tasks with tedious ones and knowing when to say no helps preserve wellbeing (Corey).
-
•
Neurodiversity and personality diversity within teams are essential to support different working styles and prevent burnout (Daniel).
-
•
Allowing asynchronous and varied engagement methods in workshops gathers richer input from different personality types (Lane).
-
•
AI is becoming a powerful tool for design ops work by aiding ideation, message drafting, data interpretation, and even team facilitation (panelists).
Notable Quotes
"When I think about resilience, I think about flexibility, like trees that bend in strong winds instead of breaking — that starts with mindset and communication."
"Always approach from a place of kindness and think about the experience you want people to have as the water that keeps trees bendable."
"A lot of design ops impact comes from influence, and influence comes from empathy and showing the benefit of what you are putting out."
"It’s energy management, not time management — listen to yourself rather than comparing your output to others."
"Feedback is data, not personal — once you view it that way, it feels less like criticism and more like improvement information."
"Our behavior is implicit messaging; we need both explicit and implicit signals to support resilience on teams."
"Managing to outcome, not output, lets people own their way of working and leverages their best strengths."
"Supporting different ways people prefer to engage—like asynchronous workshops or prep time—helps introverts and extroverts contribute equally."
"What if we had AI teammates who were on every call and could help moderate, recap, and track time? That future is likely."
"AI is a great tool for drafting and summarizing, but you have to keep your unique voice because that’s what differentiates you."
Or choose a question:
More Videos
"Start with the problem, not the solution when partnering with engineers."
Dawn ResselFull-Stack User Experiences: A Marriage of Design and Technology
June 9, 2016
"Trust is fragile with designers; without clear communication, metrics can feel like micromanagement - Dave Malu."
Bria Alexander Patrizia Bertini Peter Boersma Jon Fukuda Dave Malouf Theresa Slate Changying (Z) ZhengCharting the future of DesignOps: A community workshop
April 18, 2024
"We ran community gatherings with themes, presentations, and breaks, because people needed space to just chat and connect."
Kara KaneCommunities of Practice for Civic Design
April 7, 2022
"We found out there wasn’t just one best in class solution and needed a hybrid approach."
Anna AvrekhUser Research, Design, and Product - A Love Story
March 11, 2021
"Our skills matrix became the center of gravity for our practice—it started writing job descriptions and guiding recruitment."
Liam ThurstonWhy Your Design Team Is Quitting, And How To Fix It
June 10, 2022
"One workflow might touch five different product areas but from the customer's perspective, it’s just one product."
Sean Fitzell Sarah Han Kayla FarrellCraft of User Research: Building Out Jobs to be Done Maps
March 12, 2021
"Design system is a continuous process—product development, service to educate, and creating adoption conditions."
Nina JurcicThe Design System Rollercoaster: From Enabler and Bottleneck to Catalyst for Change
October 3, 2023
"When you get stuck, fall back to the loop: observe, reflect, and make. Get out and talk to users."
Mitchell BernsteinOrganizing Chaos: How IBM is Defining Design Systems with Sketch for an Ever-Changing AI Landscape
September 29, 2021
"It took a long time for teams to prepare their first growth board presentations because many weren’t used to roadmapping or metrics."
Jackie HoLead Effectively While Preserving Team Autonomy with Growth Boards
January 8, 2024