Panel Discussion: Communicating the Value of DesignOps
Summary
In the discussion, Brennan from Target explains his design ops team’s composition, emphasizing the current presence of himself in a chief-of-staff-like role and design program managers handling high-level initiatives like onboarding and product releases. He elaborates on the emerging role of producers focused on pixel-perfect design execution and operational efficiency. Chris and Mark contrast this with smaller teams lacking producers but employing roles like scrum designers and design architects. Brennan shares his experience implementing the maker schedule in a bureaucratic environment, emphasizing the necessity of executive buy-in from VPs and COOs to mandate protected design time. Ashley Jaron raises the question of fostering and measuring a user-first mindset, with panelists highlighting the complexity, often relying on countless small initiatives rather than clear metrics. Stories like having leadership admins answer customer calls reveal impactful cultural change methods. Chris discusses their success creating a quality scorecard based on heuristics, built iteratively over nine agile sprints to translate soft design concepts into data-driven metrics, though Mark notes some organizations like CERN may resist such approaches due to their scientific culture. Brennan clarifies that most surveyed designers are not production-focused but engage in defining product features, user advocacy, and balancing design with product roles. The panel reflects on storytelling strategies to communicate design ops value, such as linking design issues to business outcomes (e.g., referral revenue) during company-wide meetings. They differentiate design ops from general operations, stressing the need for empathy and understanding of design work akin to how TPMs understand engineering. Regarding the future of design, the panel views AI and tooling as augmenting rather than replacing designers, embracing an experimental mindset with new tools. Finally, Chris defines design strategy as a team-driven broader role that goes beyond ops to include corporate planning and strategic design sprints at multiple organizational layers. Overall, the talk surfaces nuanced challenges and successes in building and promoting design ops in diverse organizational contexts.
Key Insights
-
•
Brennan’s design ops team currently has a chief-of-staff role and design program managers, with plans to incorporate producers managing day-to-day design production.
-
•
Producers likely manage detailed task execution in tools like JIRA, while program managers oversee higher-level, long-term initiatives.
-
•
Implementing the maker schedule requires executive support, especially in bureaucratic organizations, as grassroots efforts alone are insufficient.
-
•
Measuring a user-first mindset is a complex 'wicked problem' with no single metric; success comes from numerous small cultural shifts.
-
•
Engaging leadership directly with customer experiences, such as having admins take support calls, can powerfully shift organizational empathy for users.
-
•
Chris’s quality scorecard was developed iteratively over nine sprints, translating qualitative design heuristics into a quantifiable metric used by PMs.
-
•
Certain scientific or research-driven cultures may resist adopting design measurement tools due to skepticism about methodology and relevance.
-
•
Most designers studied spend limited time on production design; their core work involves product definition, user advocacy, and early-stage research.
-
•
Design ops storytelling succeeds by aligning design impact with key business metrics like referral revenue and attrition in company-wide forums.
-
•
Design ops requires domain understanding akin to technical program managers, blending operational skills with deep empathy for design work.
Notable Quotes
"I feel like I play more of a chief of staff type role than just head of design operations."
"A producer is probably in JIRA day-to-day, running tasks, creating tickets and epics, while a program manager tracks board-level timelines."
"We had to push up the ladder to VP and COO level to get the maker schedule endorsed and mandated."
"Every one of us is probably the lubricant in a system—you only notice us when things go bad."
"We took all the leadership admins to a call center for a week to make them feel what customers go through."
"We made up the quality scorecard, translating fuzzier heuristics into a hard number for our data-driven company."
"Science cultures like CERN have a huge headwind against adopting design measurement tools because of skepticism."
"Designers often have to step up and play the product manager role to define features and evangelize for users."
"We built a linear aggression model showing direct correlation between design problems and business metrics like referral revenue."
"A design program manager needs to understand at least what interaction, visual, and motion design mean—much like TPMs know engineering."
Or choose a question:
More Videos
"The estuary is highly resilient but also very sensitive to industrial waste—creative collaboration areas in organizations are similar."
John CutlerOxbows, Rivers, and Estuaries: How to navigate the currents of change (without burning out)
December 3, 2024
"Taking responsibility for our behaviors starts with an apology and continues with regular feedback and action."
Darian DavisLessons from a Toxic Work Relationship
January 8, 2024
"Our communications is all over the map — email, Slack, Hangouts, face-to-face, GitHub — it surfaced some gaps we didn’t fully appreciate before."
Dave GrayGroup Activity: Making Sense of DesignOps
November 7, 2017
"If you are a glue person expecting to be indispensable, you are more dispensable than you think. But if you’re a catalyst moving information and translating to action, that’s more valuable now."
John CutlerThe Alignment Trap
November 29, 2023
"When was the last time that you felt stuck? The one where you feel a sense of being stuck trying to understand something."
Abby CovertStuck? Diagrams Help
October 27, 2022
"Side-pav proposals answer what’s going on, why it matters now, what you propose, what action to take, and what benefit comes from it."
Mark InterranteCollaboration Flows in Product Development
June 9, 2017
"The future will be struggle; we need to face that forward, not deny it."
Devon PowersImagining Better Futures
March 9, 2022
"The best teams I know are a quarter ahead of the product roadmap, seeking out impactful strategic research projects themselves."
Prayag NarulaHow to Empower Your Designers to Do Good Research – And Why You Want To
June 10, 2022
"Cloud code wasn’t programmed to do this; it’s a very lightweight system where the model does most of the work."
Peter Van DijckHands on AI #3: Claude Code for UX people
October 22, 2025
