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
"We fundraised to cover Tatiana’s salary for three months so she could launch this project very quickly after the war started."
Xenia Adjoubei Sean BruceEmpowering Communities Through the Researcher in Residence Program
March 29, 2023
"Our framework is our playbook, our single source of truth for every launch."
Tamara KartoziiaThink global, adapt local: how service design accelerated B2B market entry by 6 months
November 20, 2025
"Ethical stress testing subjects AI to hypothetical morally challenging scenarios to ensure alignment with ethical norms."
Jay BustamanteNavigating the Ethical Frontier: DesignOps Strategies for Responsible AI Innovation
October 2, 2023
"How we orient ourselves to the future impacts how we experience the present."
Nicole AleongFuture Orientations to Everyday Life: Futures Anthropology as a Methodology
March 26, 2024
"Most heavy website performance issues come from videos, images, JavaScript, and fonts."
Nick LewisDesigning and building low-carbon websites independently
November 18, 2025
"Having the clients share their screen and having our actual team members watch these live sessions has become very compelling for the entire extended product, UX, and development teams."
Vicky Teinaki Michele Marut Tim ParmeeShort Take #3: UX/Product Lessons from Your Industry Peers
December 6, 2022
"The ultimate goal in conflict is to engage with the tension while reducing the friction between humans."
Laura WeissTurn Down the Heat: 3 Ways to Handle Conflict in the Moment
November 20, 2024
"This is pure context information, not requirements yet, but it’s structured and detailed for design."
Joerg Beringer Thomas GeisScaling User Research with AI: Continuous Discovery of User Needs in Minutes
June 10, 2025
"Be present, put devices down, turn off Slack notifications, and really engage."
Shelby SwitzerMaking Space for Community Knowledge-sharing in a Distributed World
December 10, 2021
