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 'team ops' and 'product ops' allows focused support at different organizational scales—team ops manages culture and growth, product ops supports delivery and product teams.
-
•
Recognizing an inflection point where design ops growth lags behind the design organization is critical to avoid solving outdated problems.
-
•
The pendulum problem occurs when design ops swings priorities wildly between organizational-wide events and product team needs, leading to neglected areas.
-
•
Assigning ownership for large organizational programs like onboarding ensures consistent quality and reduces stress for DPMs juggling multiple priorities.
-
•
Siloed DPMs ('lone wolves') arise when responsibilities are too broad or mismatched, harming team morale and efficiency.
-
•
Creating distinct career ladders aligned with the two design ops tracks encourages specialization, growth, and retention.
-
•
A horizontal team ops function enables scaling of best practices, playbooks, and cultural connection across a large global UX organization.
-
•
Product ops acts as an 'air traffic controller' for UX project delivery—synchronizing releases, managing workflows, and facilitating workshops.
-
•
Continuous learning, community building, and tooling are foundational pillars of the team ops track.
-
•
Design ops operating models must evolve iteratively, informed by organizational maturity and feedback, with care for human impact.
Notable Quotes
"Imagine your current design ops team is like a coin and every time you flip it, it comes up heads, but it has more than one side worth exploring."
"Team ops goes wide to optimize for the entire UX organization, while product ops goes deep to optimize delivery for individual product teams."
"The pendulum problem is when priorities swing wildly between org-wide events like Dreamforce and product release support, causing some needs to be neglected."
"If nobody owns onboarding, it likely won’t get done or won’t get the energy it deserves."
"DPM loneliness or feeling like an army of one happens when people wear too many hats and become siloed, harming alignment and effectiveness."
"Our career ladder used to look like a step stool—just high enough to see what's interesting but no next step to grow."
"With our new model, partners are more confident funding UX ops because there is clear focus and coverage across priorities."
"Take your time. The road to a new design ops model is long and definitely not a straight path."
"As your design practice matures, your design ops team will reach an inflection point—flip your design ops coin and see what’s on the other side."
"Being critical of your operating model and exploring all ways it can look will push you past that inflection point onto your path forward."
Or choose a question:
More Videos
"You need strong regional players with negotiation skills to navigate the split loyalties in global teams."
Adam Cutler Karen Pascoe Ian Swinson Susan WorthmanDiscussion
June 8, 2016
"Sometimes the director is the most senior design person in the org and ends up playing the executive role without the title or support."
Peter MerholzThe Trials and Tribulations of Directors of UX (Videoconference)
July 13, 2023
"Digital is a system, not a project. It’s there all the time and you have to keep iterating on it."
Lisa WelchmanCleaning Up Our Mess: Digital Governance for Designers
June 14, 2018
"The solutions are out there; we just need the will to implement them."
Vincent BrathwaiteOpener: Past, Present, and Future—Closing the Racial Divide in Design Teams
October 22, 2020
"Psychological safety was far and away the key ingredient for teams being effective."
Brenna FallonLearning Over Outcomes
October 24, 2019
"Linear perspective created this myth that we can see reality from a single perspective, which is the source of all misunderstanding."
Tricia WangSpatial Collapse: Designing for Emergent Culture
January 8, 2024
"Research should be done the same way products are built, with stakeholders as your users."
Edgar Anzaldua MorenoUsing Research to Determine Unique Value Proposition
March 11, 2021
"Successful operations must have a well-laid-out and transparent process and documentation, but that process must become invisible in its application."
Designing Systems at Scale
November 7, 2018
"Design is the rendering of intent — bringing ideas into a form people can interact with to solve problems, as Jared Spool said."
Erin WeigelGet Your Whole Team Testing to Design for Impact
July 24, 2024
