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
"The System Usability Scale’s question about needing a technical person to use the system is confusing and inaccurate for screen reader users."
Sam ProulxSUS: A System Unusable for Twenty Percent of the Population
December 9, 2021
"There are lots of little mushroom patches of design sprouting up, but they're disconnected and not sharing."
Michael LandEstablishing Design Operations in Government
February 18, 2021
"Going from 100 to 200 people, suddenly product managers started hearing from a dozen people a week with conflicting requests."
Shipra KayanHow we Built a VoC (Voice of the Customer) Practice at Upwork from the Ground Up
September 30, 2021
"Careers as ladders are what HR wants, but careers aren’t linear; they should be a jungle gym."
Ian SwinsonDesigning and Driving UX Careers
June 8, 2016
"If you’re managing over 100 design practitioners, it makes sense to start looking at a chief of staff role."
Isaac HeyveldExpand DesignOps Leadership as a Chief of Staff
September 8, 2022
"Controls like insurance qualifiers and legal agreements were necessary guardrails for this new way of working."
Amy EvansHow to Create Change
September 25, 2024
"We are stronger when we work together towards a unified goal – that’s our super healing power."
Kate Koch Prateek KalliFlex Your Super Powers: When a Design Ops Team Scales to Power CX
September 30, 2021
"It’s impossible to be angry with a warm cup of tea in your hand."
Dave GrayLiminal Thinking: Sense-making for systems in large organizations
May 14, 2015
"Repository to me has a connotation of a place where stuff goes to sit and collect dust."
Matt DuignanAtomizing Research: Trend or Trap
March 30, 2020
Latest Books All books
Dig deeper with the Rosenbot
How can designers practically integrate systems thinking tools like stakeholder mapping in their daily work?
What does the convergence of design ops, product ops, and engineering ops look like in practice?
What rituals and practices help maintain team connection and belonging in large remote design teams?