Summary
When introducing DesignOps as a new function to an organization, the first few months are critical as you set the stage for how the organization familiarizes itself with your new team. In this session, Brennan will cover how DesignOps can partner with other functions, how to pick the right programs to tackle first, and how to measure a new team’s success. He will showcase tools that are useful to help establish your team’s newly formed brand within your organization.
Key Insights
-
•
Designers spent only about 37% of their time actually designing before adding design ops support.
-
•
Adding one design program manager (DPM) to a team of 14 designers increased design time by 50%, equivalent to adding three to four designers.
-
•
Design ops roles should be tailored to solve specific problems rather than hiring a generic role upfront.
-
•
The three Ps framework—people, process, and priorities—helps clarify design ops responsibilities versus design managers and directors.
-
•
DPMs reporting into a separate design ops team rather than design managers creates a therapeutic, safe space for designers to speak up.
-
•
Global design collaboration needs guidelines on time zones, communication norms, and sharing best practices across offices.
-
•
Removing unnecessary tools boosts efficiency more than continually adding new ones.
-
•
Assigning a DPM to design teams that don't want one leads to confusion and inefficiency.
-
•
Standardizing tools across all design teams is less important than good communication and adaptability.
-
•
Onboarding, mentorship, and team culture programs are critical design ops functions often overlooked in large organizations.
Notable Quotes
"Three hours per day was the average time designers actually spent designing—37% of their work time."
"We are the air traffic control making sure all the planes land in the right place."
"Hiring a design ops person off the bat without understanding the problem is like hiring a unicorn without a purpose."
"Design ops reporting separately from design managers creates a safe space—sometimes our DPMs are the therapists of the team."
"London is the straight-A student of our global design teams, and we've learned a lot from them."
"Adding a design program manager increased ‘maker time’ or actual design work far more than adding more designers."
"Removing tools, not adding more, was key to solving tool chaos across teams."
"Allocating a DPM to a design team that doesn’t want one just created more confusion."
"Standardizing everything is an uphill battle; communication and context matter more."
"Surprisingly, onboarding for designers was basically ‘here’s your laptop, good luck.’ We needed to fix that."
Or choose a question:
More Videos
"A 101 conversation over coffee yields better insights than written reviews in 360 assessments."
Adam Cutler Karen Pascoe Ian Swinson Susan WorthmanDiscussion
June 8, 2016
"Knowing your subject matter as a UX leader is just as important as knowing your craft."
Peter MerholzThe Trials and Tribulations of Directors of UX (Videoconference)
July 13, 2023
"Governance isn’t about choking creativity, it’s about putting bounds and clarity that enable purposeful collaboration."
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
"It matters what you build, but it matters more if you learn."
Brenna FallonLearning Over Outcomes
October 24, 2019
"We are all experiencing a spatial collapse, a disruption of our mental models of how we navigate physical and virtual spaces."
Tricia WangSpatial Collapse: Designing for Emergent Culture
January 8, 2024
"Delivering research in small, lean increments allowed us to iterate fast and reduce bias."
Edgar Anzaldua MorenoUsing Research to Determine Unique Value Proposition
March 11, 2021
"Our brains are terrible at operating only on one type of information, whether object-oriented or context-oriented."
Designing Systems at Scale
November 7, 2018
"A lot of developers are way too confident they write perfect code; testing bug fixes often reveals hidden issues."
Erin WeigelGet Your Whole Team Testing to Design for Impact
July 24, 2024