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
"You can’t know a human honestly from the outside alone; you have to let their reality work on you."
Daniel GloydDesigning From the Inside Out: How Method Acting Can Inspire Design Research
February 12, 2026
"Butter is about consistently showing up and being present so people don’t forget you."
Deirdre Hirschtritt Cesar Paredes Marie PerrotResearch is Only as Good as the Relationships You Build
November 17, 2022
"We were lost in the forest and you come across this compass, maybe all time rusty, but still something a little bit useful."
Benjamin RealMaturity Models: A Core Tool for Creating a DesignOps Strategy
October 1, 2021
"If you think fossil fuel companies are going to help us solve this, then we probably have a very different idea of how this system works."
Max Gadney Andrea Petrucci Joshua Stehr Hannah WickesAssessing UX jobs for impact in climate
August 14, 2024
"Seb is career UXer fresh at Canadian railways with a steep learning curve."
Lada GorlenkoTheme 1: Intro
January 8, 2024
"The most expensive part of digital initiative is not delivery, it’s that messy middle—the space between insights and moving things forward."
Feyikemi AkinwolemiwaPlay to innovate: How curiosity and experimentation transform UX
March 11, 2026
"Lauren Cantor keeps all those links and other resources so we don’t have to be googling while listening."
Bria AlexanderOpening Remarks
March 29, 2023
"Wonder Studio automatically segments actors, maps their movements to a 3D model, and renders a synthetic avatar video."
Llewyn Paine[Demo] Deploying AI doppelgangers to de-identify user research recordings
June 5, 2024
"Accessibility is a great example where OKRs can unify multiple product and design teams to a non-negotiable standard."
Bria Alexander Benson Low Natalya Pemberton Stephanie GoldthorpeOKRs—Helpful or Harmful?
January 20, 2022
