Summary
In an ideal world, Design Operations is one part of a larger team working toward a common goal. However, working with other program management teams - Product Operations, Technical Program Management and Content or Marketing Operations – can be a challenge due to overlap and other common pitfalls. Alnie will discuss these challenges, and present strategies to better define expertise and charter for each program management team, resulting in more effective collaboration.
Key Insights
-
•
Design operations functions are often new and misunderstood, requiring clear communication of their mission and scope.
-
•
Creating a team or individual charter helps define and communicate design ops roles internally and with peers.
-
•
Managing ambiguity is a core skill for design ops, particularly in early, exploratory phases of product development.
-
•
Using tangible tools like prototypes can reduce meetings and align multiple stakeholders effectively.
-
•
Building a program management community of practice facilitates relationship-building and clarifies overlapping responsibilities.
-
•
Design ops should act as strategic operational leaders, bridging silos and connecting people, processes, and tools.
-
•
Successful collaboration is marked by understood expectations, clear swim lanes, healthy team cadence, and minimal friction.
-
•
Regular feedback loops, even informal ones, help surface operational gaps and mature partnerships.
-
•
Balancing where design ops sits organizationally—within design or cross-functional program management—affects proximity to teams and collaboration.
-
•
Engaging HR business partners is critical to resolving leveling and role recognition challenges within operations teams.
Notable Quotes
"Our job is really a lot of managing ambiguity and chaos; it's just par for course."
"A prototype is worth a thousand meetings to create alignment and reduce churn."
"Design ops are strategic operational leaders, not just connectors."
"Build relationships beyond design, including product partners, legal, communications—relationship is the currency of our craft."
"Expect confusion about design ops roles especially if the function is new; be ready to explain it often."
"Say yes or no to projects based on company priorities, user experience impact, and your ability to make a difference."
"Once people see design ops in action, they understand its value and start asking for investment."
"It's okay to evolve your charter; it should be a living document that reflects organizational maturity."
"Not everyone needs to be in every meeting; define clear touch points and handoffs to reduce friction."
"Community of practice meetings grow stronger when ownership is shared and rotating."
Or choose a question:
More Videos
"I have to triangulate socially because Yorkshire folks are quite reserved; they won't openly admit issues."
Adam Cutler Karen Pascoe Ian Swinson Susan WorthmanDiscussion
June 8, 2016
"If you’re doing a lot of work that’s not in your job description, you might actually be doing leadership."
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 time for action is now, and it must be collaborative."
Vincent BrathwaiteOpener: Past, Present, and Future—Closing the Racial Divide in Design Teams
October 22, 2020
"If you forget the individual, you cut out psychological safety, and that’s the foundation of strong teams."
Brenna FallonLearning Over Outcomes
October 24, 2019
"Thick data is the opposite of big data; it’s stories, qualitative, and crucial during moments of rapid change."
Tricia WangSpatial Collapse: Designing for Emergent Culture
January 8, 2024
"Clusters describing demographics and behaviors alone were not enough; we needed emotional personas to find value propositions."
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
"If my experiment made front-page news tomorrow, what would the headline be? Would my mother be proud?"
Erin WeigelGet Your Whole Team Testing to Design for Impact
July 24, 2024