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
"People on the project were reporting back to management in their silo, not talking to one another."
Carl TurnerYou Can Do This: Understand and Solve Organizational Problems to Jumpstart a Dead Project
March 28, 2023
"Performance management is really about the employee experience; avoid surprises by coaching continuously on both what and how folks are doing."
Karen PascoeDeveloping Experience Teams and Talent in the Enterprise
June 8, 2016
"We share the inconvenience of meeting times across time zones, alternating so no one team always bears it."
Jilanna WilsonDistributed Design Operations Management
October 23, 2019
"Throwing a potluck sounds easy until you realize you don’t have a group that magically reads each other’s minds, resulting in a random table of snack foods."
Shawna Hein Kevin HoffmanCreate a Cohesive Civic Design Practice Across Agency, Vendors, and Contracts
November 17, 2022
"You need to find your own mattress—a grounding purpose or phrase—that you can rely on when progress feels hopeless."
Barb SpantonDoing Work That Matters: A Look Beyond The Idealistic Notion of 'Doing Meaningful Work'
June 10, 2022
"Dana is a reliable, solutions-oriented designer who prefers honest feedback but needs clear expectations."
Briana ThomasThe Quiet Force: Uncovering Hidden Leadership in High-Impact Design Teams
September 24, 2024
"Creating and holding space is like putting bumpers up in bowling so people know they won’t fail if they engage."
Gina MendoliaTherapists, Coaches, and Grandmas: Techniques for Service Design in Complex Systems
December 3, 2024
"Being fluent in multiple data languages and understanding behavioral and attitudinal data will be essential."
Lija Hogan Milan Mijatovic Sam Proulx Louis RosenfeldThree Years Out: Perspectives on the Near-Term Future of User Research
March 15, 2024
"Our design ops team was a step behind the growth of our design team, solving the wrong problems at the wrong scale."
John Calhoun Rachel PosmanTwo Sides of the DesignOps Coin: Teams Ops and Product Ops
January 8, 2024
Latest Books All books
Dig deeper with the Rosenbot
Why are some organizations moving away from third-party customer data platforms (CDPs)?
What strategies help UX teams translate usability findings into stakeholder-relevant outcomes like cost savings or risk reduction?
What is the evolving role of researchers of one in organizations practicing democratized research?