Two Sides of the DesignOps Coin: Teams Ops and Product Ops
Summary
What happens to your DesignOps team when your Design organization hits scale? Juggling the growth of your product, your people, and your processes is a demanding challenge, and strains the jack-of-all-trades skillset of even the most seasoned DesignOps practitioner. Our solution? Evolve DesignOps into two discrete tracks: Team Ops and Product Ops. We’ll look at how these tracks emerged, how they operate in practice, where they intersect (and where they differ), and the lessons learned from our “conscious uncoupling” of design team ops and product design ops responsibilities.
Key Insights
-
•
Splitting design ops into two tracks—team ops and product ops—allows balancing broad organizational support with deep product-focused delivery.
-
•
Team ops focuses on scaling culture, community, learning, and tools for the entire UX org, while product ops focuses on project delivery and team-specific needs.
-
•
Design ops teams often fail to scale in sync with their growing design organizations, creating an inflection point requiring new operating models.
-
•
Design ops practitioners swinging wildly between org-wide and product-level priorities causes partner frustration and operational inefficiency.
-
•
Assigning clear ownership, such as a dedicated onboarding owner, improves new hire experiences and reduces manager and employee stress.
-
•
Silos and lone-wolf syndrome among design ops can arise from ambiguous roles and uneven workload distribution.
-
•
Clear career ladders with specialization options help retain DPMs by providing growth paths beyond being generalist problem solvers.
-
•
Effective collaboration between team ops and product ops creates a feedback loop for continuous improvement and scaling of best practices.
-
•
An evolving design ops model demands patience and intentional change management, treating role transitions as carefully as new hires.
-
•
Cross-company benchmarking is limited, but Salesforce’s design ops coin model inspires others to consider multiple tracks beyond design and research ops.
Notable Quotes
"Imagine your current design ops team is like a coin and every time you flip it, it comes up heads, but coins have two sides."
"Team ops goes wide to support 300-plus UX designers globally; product ops goes deep supporting 40-plus product design teams."
"Our design ops team was a step behind the growth of our design team, solving the wrong problems at the wrong scale."
"Design ops is always swinging wildly between priorities, making partners wonder why invest if you’re always going this way or that."
"If nobody owns the onboarding experience, it likely won’t get done or get the energy it deserves."
"DPM loneliness and siloing happen because of wearing too many hats and inheriting mismatched responsibilities."
"A design ops career ladder can look like a step stool unless you create multiple tracks for growth and specialization."
"With our new operating model, partners are more confident funding UX ops because of increased clarity and focus."
"As your design practice matures, your design ops team will reach inflection points, and it’s okay to flip the coin and explore the other side."
"Be human first when creating new roles; treat them with the same care as hiring new team members."
Or choose a question:
More Videos
"Building strong relationships with marketing requires mutual respect and regularly following up on their insights."
Joanna Vodopivec Prabhas PokharelOne Research Team for All - Influence Without Authority
March 9, 2022
"You have to build relationships with legal and political leadership to figure out what you can actually change."
Louis Rosenfeld Lashanda Hodge Senongo Akpem Chris HodowanecBecoming a Civic Designer: Making the Move from Private to Public Sector
November 17, 2022
"If you want to invite a friend or colleague, the sponsor sessions are free and awesome to attend."
Bria AlexanderDay 3 Welcome
September 25, 2024
"Am I getting what I wanna get out of this conference? What’s not coming and what would I still like to learn?"
Uday Gajendar Louis RosenfeldDay 2 Welcome
June 5, 2024
"Timely interactions that log users out without saving progress cause abandonment, especially for people with disabilities."
Sam ProulxOnline Shopping: Designing an Accessible Experience
June 7, 2023
"Unpaid design exercises are unfair because they don’t take into account people's real-life constraints."
Russ UngerOnboarding: The Ecosystem, not the Afterthought
November 7, 2017
"Being able to see faces and first names of people we're learning from makes those users tangible to the team."
Catherine DubutBridging Physical and Digital Spaces: Approaches to Retail Service Design
March 18, 2021
"These intelligent interfaces are collaborative, proactive partners on the user’s journey."
Josh Clark Veronika KindredSentient Design: New Postures for AI-Mediated Experiences (2nd of 3 seminars)
January 29, 2025
"Ownership needs to be shared. The craft of making is similar to raising a child — it takes a village."
Dantley DavisLeadership & Diversity—A Fireside Chat with Dantley Davis
September 17, 2020
Latest Books All books
Dig deeper with the Rosenbot
When should you avoid using play-based activities in team alignment sessions?
Why is design education’s emphasis on critical making important, and how does it interrelate with critique and theory?
Where can UX researchers find reliable, up-to-date information and recommendations on research tool options?