Developing and Deploying Your Design Operations Strategy
Summary
In this talk, Cassandra will guide you through the process of defining and deploying an operational strategy. With this strategy, you will scale the impact of design operations without increasing the size of your program management team. She'll provide tips on how to get buy in from your key stakeholders to ensure their investment and guarantee their adoption of your strategy as their own. With this practical toolset, you can define your operational vision, empower yourself and your partners to deploy it, and finally get yourself the bandwidth you’ve needed to be more strategic.
Key Insights
-
•
Design operation strategy acts as both foundation and protective structure for teams to withstand organizational challenges.
-
•
Multiple design teams often work in silos with inconsistent planning, causing inefficiency and communication gaps.
-
•
Documenting existing processes and roles is more effective than creating new systems from scratch.
-
•
Sharing early and 'ugly' drafts encourages stakeholder feedback and faster alignment.
-
•
Starting with clear roles and responsibilities by analyzing recurring meetings can quickly build common understanding.
-
•
Collaborative problem framing helps focus strategic efforts on the most impactful issues.
-
•
A single source of truth roadmap can unify multiple teams and visualize dependencies to improve planning.
-
•
Introducing quarterly milestone planning bridges the gap between long-term roadmaps and sprint cycles.
-
•
Scaling design operations requires shifting from tactical execution to strategic facilitation across teams.
-
•
The process of continuous improvement in operations mirrors iterative product development cycles.
Notable Quotes
"It needs to be a strong structure, not necessarily super pretty, but the foundation your team sits upon and the roof above its head."
"When you set out to build your own design operation strategy, pieces of the puzzle already exist—you don’t have to reinvent the wheel."
"Share early, share ugly—that’s our mantra for this entire process."
"Everyone has thoughts on what their job is, so starting with roles and responsibilities gets quick buy-in."
"If your teams work in silos and have different roadmaps, maybe the solution is a single source of truth to see dependencies and priorities."
"Quarterly milestone planning can help take the big annual rocks and break them down into manageable chunks throughout the year."
"You want to get really deep in the weeds with one team first, then move into a facilitation role to scale across teams."
"Being tactical means updating Kanban tickets for one team; being strategic means updating annual Gantt charts across the portfolio."
"The most important step we often forget is moving on to the next problem."
"Operations have to be constantly improving, just like when we ship features."
Or choose a question:
More Videos
"If you want to make one slice bigger you have to make another slice smaller — executives hate the exclusive or concept."
Rich MironovHow Can Product Managers and UXers Help Each Other (and Why are Product Folks so Annoying Sometimes)?
December 6, 2022
"Every talk you hear today couldn’t get more personal to our community."
Bria AlexanderTheme Two Intro
October 3, 2023
"Surgeons say during difficult operations the whole team feels like a single organism moved by the same purpose."
Ruzanna RozmanGetting in Flow with Your Team
January 8, 2024
"You need to be laser-focused as ops people—we get asked to do too many things otherwise."
Briana Thomas Christina RodriguezWhen Design Ops Comes in H.O.T. : A Tale of a Transformed Design Org
September 30, 2021
"Veterans don’t use the internet was the common excuse we heard, but that was simply not true."
Marina MartinLives on the Line: The Stakes of UX at the Scale of Government
June 14, 2018
"Activating insights multiple times can be necessary before teams truly internalize and act on them."
Jake BurghardtStop wasting research: Create new value with insight summaries
July 9, 2025
"Creating shared coding schemes and having teams do first-pass coding helps maintain consistency in qualitative analysis."
Clemens Janssen Jane DavisEfficiently Scaling Research as a Team of One
March 28, 2023
"Organizational information models need to grow and be managed, not treated as static deliverables."
Bram WesselEnterprise Information Architecture
January 10, 2020
"Highly trained professionals still default to a presumed 'standard' under pressure, revealing how bias persists."
Kaitlin TaskerFast and Fearless Inclusive Research
March 27, 2023
