Log in or create a free Rosenverse account to watch this video.
Log in Create free account100s of community videos are available to free members. Conference talks are generally available to Gold members.
Summary
Each year brings new advancements, challenges, and opportunities to the DesignOps community, but this time seems much different—for DesignOps people and the design profession in general. It may be high time to reexamine and re-map DesignOps’ context, framing, and direction. We’re convening some of the leading DesignOps minds to reflect on the current state of our practice and its context and value in digital product and service organizations—and we want you to be a part of it. Watch the recording of this interactive moderated session with David Malouf, Patrizia Bertini, Peter Boersma, Theresa Slate, Z Zheng, Jon Fukuda, and Bria Alexander. Together we set the roadmap and framed our goals—both for the next DesignOps Summit and, more importantly, for the future of the DesignOps craft. We spent time together mapping out new scenarios for DesignOps in Figjam, and we opened up the DesignOps Summit’s Call for Participation during the session.
Key Insights
-
•
Design ops functions best when positioned as a strategic partner throughout the organization, not just executing tactical tasks.
-
•
A significant portion of design ops practitioners work as teams of one, highlighting challenges in growth and role clarity.
-
•
There is confusion and overlap in titles such as design ops, design program management, and product operations, complicating role definition.
-
•
Underfunding and undervaluation remain major challenges for design ops, often viewed as optional rather than essential.
-
•
Design ops should serve multiple stakeholders including designers, design leadership, product teams, and executives for broader impact.
-
•
Applying design thinking beyond the design team to the entire R&D organization and product processes amplifies impact and integration.
-
•
Measuring design ops success requires context-specific, directional metrics that evolve, focusing on designer happiness, onboarding time, and efficiency.
-
•
Decentralized and flat organizational structures make centralized design ops roles harder to justify, but guild or chapter models provide a solution.
-
•
Collaboration and alignment with design managers is essential to avoid perceived role conflicts and maximize value.
-
•
Design ops needs to better tell its story using business language and case studies to gain trust with designers and executive stakeholders.
Notable Quotes
"When design ops is elevated to a leadership role, it can bring tangible and quantifiable value to the whole product organization - Patrizia."
"Design ops is still an emerging field; a lot of unknowns, and we’re still defining the industry - Zi."
"When everything's working well, nobody notices design ops, but the moment things break down, everybody's missing design ops - Theresa."
"There really aren’t many job postings titled 'design operations'; often, roles are labeled as product operations or design program management - Dave Malu."
"We need role definitions to move beyond the ninja phase of UX practitioners - Peter Bosma."
"If we keep framing ourselves as servant leaders for design teams only, we will be shooting ourselves in the foot - Patrizia."
"To amplify the value of design means serving both those who use our designs and those who make money from them - Dave Malu."
"Metrics evolve by understanding inefficiencies and pains unique to each team; there’s no one-size-fits-all - Patrizia."
"Creating unofficial centralization through guild or chapter models is effective when formal central roles are absent - Theresa."
"Design ops must speak the language of business to narrate its value and build trust within the organization - Dave Malu."
Dig deeper—ask the Rosenbot:
More Videos
"The fastest way to gain influence is to get somebody else promoted."
Monty HammontreeThe Future of UX Research (Videoconference)
December 3, 2020
"You have to engage every layer of the system—from local communities to NGOs and government power structures—to create change."
Liz EbengoThe Burden on Children: The Cost of Insufficient Post-Conflict Services and Pathways Forward
December 4, 2024
"Content first design should happen after sketching but pretty early to help shape the wireframes and concepts."
Billy CarlsonTips to Utilize Wireframes to Tell an Effective Product Story
June 6, 2023
"Inclusive design happens on a spectrum from accidental to intentional."
Saara Kamppari-MillerInclusive Design is DesignOps
September 29, 2021
"Innovation is about being fearless. There’s a rule or a process, but that doesn’t mean it’s right—keep pushing and breaking things."
Ian SwinsonDesigning and Driving UX Careers
June 8, 2016
"Working across multiple teams all the time is normal for content designers, but that doesn’t mean it’s the best or the only way."
Jonathon ColmanHow to Maximize the Impact of Content Design
January 8, 2024
"What users say they want and what they really need can be very different; you need to be careful about how you interpret feedback."
Maria SkaadenContinuous Design: One eye on the horizon and the other on the next wave
November 8, 2018
"I learned from Molly that the lunatic asylum is now called the Austin State Hospital, and I've encoded that in a Python script."
Bryce Benton[Demo] AI-powered UX enhancement: Aligning GitHub documentation with USWDS at Austin Public Library
June 4, 2024
"Having service design in your job title is not necessarily an advantage, at least not globally."
Marc FonteijnFirst Insights from the 2025 Service Design Salary(+) Report
December 4, 2024
