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."
Or choose a question:
More Videos
"When teams lose a sense of agency, they act strange, cutting corners and racing to get something out the door."
Standardizing Product Merits for Leaders, Designers, and Everyone
June 15, 2018
"The Red Queen effect means if others adapt, you must adapt or lose."
Simon WardleyMaps and Topographical Intelligence (Videoconference)
January 31, 2019
"Bias is a tendency, feeling or opinion for or against something without reason or evidence."
Sandra CamachoCreating More Bias-Proof Designs
January 22, 2025
"Reviewing decision points creates a source of truth and makes it harder to forget or scrap earlier agreements."
Darian DavisLessons from a Toxic Work Relationship
January 8, 2024
"We mitigated data privacy risks by subscribing to the corporate plan for ChatGPT, which offers enhanced security."
Fisayo Osilaja[Demo] The AI edge: From researcher to strategist
June 4, 2024
"Temporary, quick, and sometimes rough artifacts have a lifespan just long enough for the conversation they enable."
Uday GajendarThe Wicked Craft of Enterprise UX
May 13, 2015
"We formed a small core task force empowered to make decisions to avoid delays from formal reviews."
Davis Neable Guy SegalHow to Drive a Design Project When you Don’t Have a Design Team
June 10, 2021
"Once cash prizes were gone, people stopped feeling ownership of the design system."
Eniola OluwoleLessons From the DesignOps Journey of the World's Largest Travel Site
October 24, 2019
"Design leaders want predictable roadmaps and healthy teams, measurable against timelines and goals."
Aurobinda Pradhan Shashank DeshpandeIntroduction to Collaborative DesignOps using Cubyts
September 9, 2022
