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
"For the iBio people, knowledge is relational, not objectified, emerging from relationships like songs."
Victor UdoewaBeyond Methods and Diversity: The Roots of Inclusion
March 26, 2024
"Prototyping isn’t a second-class citizen, it should be a first-class citizen."
Bill ScottLean Engineering: Engineering for Learning and Experimentation in the Enterprise
May 14, 2015
"Sometimes accommodating 20% of users with special needs improves the experience for the entire 100%."
Lija HoganContexts of Use: A Framework for Connection
December 9, 2021
"All documents—PDFs, audio, video, Figma, Mural—live in a central repository searchable by project context."
Aurobinda Pradhan Shashank DeshpandeIntroduction to Collaborative DesignOps using Cubyts
September 9, 2022
"Our mission is to support the methods and processes devoted to producing high quality design."
Jilanna WilsonDistributed DesignOps Management
February 26, 2019
"Models are stateless; they have no memory and forget everything after each response."
Peter Van DijckBuilding impactful AI products for design and product leaders, Part 3: Understand AI architectures: RAG, Agents, Oh My!
July 30, 2025
"We need to think of ourselves as strategic leaders who know customer needs better than anyone in the organization."
Nicole Aleong Michaela Mora Prayag Narula Brianna SylverWhat UX research can learn from other research practices [Advancing Research Community Workshop Series]
September 14, 2023
"AI doesn't make bad ideas more dangerous. It makes unfinished ideas more convincing."
Beth ChappellLeading through ambiguity: Supporting a design team relearning their craft
June 9, 2026
"At last year’s conference, we were still scrambling to figure out where AI might be useful in our work."
Llewyn PaineDay 1 Using AI in UX with Impact
June 10, 2025
