Panel Discussion: Integrating DesignOps
Summary
In this panel-style discussion, Dan, Jackie, and Ornima share their experiences and insights on growing design and UX teams and embedding design practices in large organizations. Dan highlights the challenges of delivering UX in federal agencies, noting the need for patience and anecdotal evidence of success rather than ideal solutions. He stresses the importance of flexibility when selling design processes, advocating for listening carefully to stakeholders and adapting instead of rigidly pushing pre-conceived solutions. Jackie discusses scaling design ops teams from 1 to 9 and planning to grow further, explaining how their organizational model addresses friction and broadening responsibilities beyond visual design toward experience design. Jackie also shares how a new VP of design (Gene Lee) championed the inclusion of design ops in broader business strategy, enabling a smooth business case. Ornima recounts the challenge of scaling Shopify’s UX research team from a small group to over 50, emphasizing the importance of cross-disciplinary collaboration and demonstrating impact on product outcomes over time. Both Jackie and Ornima underscore the necessity of educating other teams unfamiliar with design’s role and building trust through well-prepared documentation and consistent collaboration. The speakers repeatedly stress patience, collective consciousness, embracing conflict and friction as natural steps toward progress, and recognizing organizational maturity to time initiatives properly.
Key Insights
-
•
Great UX delivery in government and complex organizations is often imperfect and requires patience and anecdotal wins rather than perfect solutions.
-
•
Selling design processes requires flexibility and listening; imposing rigid solutions often fails.
-
•
Scaling design ops teams hinges on recognizing patterns of friction and expanding responsively rather than scaling for its own sake.
-
•
Experience design is a broader scope than UI or visual, requiring more hands and diverse partnerships including agencies.
-
•
A supportive leadership figure like Gene Lee can significantly accelerate design ops adoption through integrating it into business plans.
-
•
Cross-functional collaboration, such as pairing UX researchers with support, data science, and marketing, helps embed design thinking across organizations.
-
•
Building trust with other teams unfamiliar with design requires clear communication, well-designed documentation, and delivering value over time.
-
•
Patience and acceptance of organizational maturity cycles are essential; not every good idea can or should be implemented immediately.
-
•
Conflict and friction within teams or organizations are necessary flashpoints that enable growth and collective understanding.
-
•
Design ops and UX functions evolve with organization size, requiring new strategies and team structuring to maintain velocity and impact.
Notable Quotes
"Listen hard, change fast."
"I would in no way describe what we did as great UX, but constantly beating them over the head with UX solutions, they can’t unsee it."
"If you hear what I’m saying and you’re uncomfortable, and I say I’ll do it your way, now you’re connected and you’ll back me until you can’t anymore."
"We love small teams because we move fast and break things and figure things out on the fly."
"Scaling is not for the sake of scaling, but scaling over time."
"They had no idea who we were or what value we provided, so first was hello, we exist."
"We’re humans having human experiences and remembering that is key."
"Collective consciousness cannot be asked to happen overnight; it’s a game of patience."
"Sometimes you have all the best ideas, but it’s not the right time, and that’s OK."
"Part of our job is just to have an opinion right now, not necessarily to solve everything immediately."
Or choose a question:
More Videos
"Colonial ways of being, knowing, and valuing will never produce emancipatory methodologies."
Victor UdoewaBeyond Methods and Diversity: The Roots of Inclusion
March 26, 2024
"The Library of Congress web presence was a findability nightmare, like the Winchester Mystery House."
Peter MorvilleThe Architecture of Understanding
May 13, 2015
"Ask yourself, who is not included in this future? Be self-reflexive to reduce bias."
Sam LadnerHow Research Can Drive Strategic Foresight
March 9, 2022
"The feedback culture in our company means there’s transparent discussion if conclusions aren’t clear or agreed upon."
Michelle Bejian Lotia Anne-Marie MorellRolling Out a Repository: How Zapier Centralizes Insights from Across their Organization
March 28, 2023
"One researcher per team for at least three days a week was considered an outrageous luxury at GDS in 2013."
Leisa ReicheltOpening Keynote: Operating in Context
November 7, 2018
"Evan actually spent less than 15 minutes on the essay, and instead of working on homework, he was writing a letter to his significant other back home in Detroit."
Sarah GallimoreInspire Progress with Artifacts from the Future
November 18, 2022
"The output is not a requirements statement but a description of what is happening in the context."
Joerg Beringer Thomas GeisScaling User Research with AI: Continuous Discovery of User Needs in Minutes
September 10, 2025
"Relying on process is not a proxy for quality, and divorcing process from content is a fatal enterprise mistake."
Peter MerholzCustomer-Centered Design Organizations
June 8, 2017
"Closing the loop by understanding when and why recommendations don’t get adopted is probably the most easily actionable piece of advice I can give."
Dalia El-ShimySo You've Got a Seat at the Table. Now What?
March 31, 2020
