Summary
Designers rarely work alone these days, and so the teams where we get our work done have an outsized impact on everything from how we feel day-to-day, to our ability to deliver our work, to our career trajectory. Rather than impose an operating model on my design team at [company], I borrowed heavily from the design process we use every day to co-create it in a way that solved real problems we were experiencing. Attendees will walk away with an understanding of how to lead teams that largely self govern, and the benefits of this model for team members, leaders, and the companies that employ them.
Key Insights
-
•
Design teams without embedded design ops support can still embed operational excellence by making every designer responsible for operations.
-
•
JP Morgan Chase’s small business credit card onboarding took over a year and 10 teams to deliver just four screens, illustrating scale challenges.
-
•
John Gall’s principle that complex systems evolve from simpler systems applies to building team operating models incrementally.
-
•
Three core principles for team operating models are simplicity, autonomy, and transparency.
-
•
Regular one-on-ones focused on development and driven by the direct reports’ agendas foster autonomy and trust.
-
•
Pulse surveys done monthly help baseline team alignment and surface deviations signaling areas for improvement.
-
•
Retrospectives are crucial cultural rituals where teams commit to direct yet kind conversations to surface friction for growth.
-
•
The team improved delivery from 50% of planned work in early sprints to over 90%, nearly doubling capacity without headcount growth.
-
•
Emergent cultural practices, like playing Wordle in standups, can shorten meetings and build unique team culture.
-
•
Operational models must be resilient to real-life disruptions like PTO and new team members to maintain sustainable momentum.
Notable Quotes
"Designers have a stake in design ops too—what would the world look like if that was the day-to-day for a team?"
"It took over a year and 10 teams just to ship four screens—scale is both a tremendous opportunity and a weakness."
"We have to go slow to go fast—highlight problems first, then iteratively evolve the process to solve them."
"Simplicity comes first—complex systems that work evolved from simpler systems that work, according to John Gall’s law."
"Autonomy means the team needs real control over how they work; enabling that unlocks buy-in and co-creation."
"Pulse surveys aren’t about making everything dark green, but about establishing baselines to spot meaningful changes."
"Retrospectives require a commitment to direct, kind conversations that come from a place of caring."
"We started with twice-weekly 15-minute standups and evolved everything together based on feedback."
"Context switching across eight initiatives made my brain explode; prioritization was a huge problem to solve."
"Process is scaffolding for culture—setting simple processes can reset culture and allow positive norms to grow."
Or choose a question:
More Videos
"It is part of your role to say no, enforce guardrails, and stop people pleasing when democratizing research."
Jemma Ahmed Steve Carrod Chris Geison Dr. Shadi Janansefat Christopher NashDemocratization: Working with it, not against it [Advancing Research Community Workshop Series]
July 24, 2024
"Customers rarely ask us to fix inconsistencies directly; we must watch activation rates and confusion instead."
Nina JurcicThe Design System Rollercoaster: From Enabler and Bottleneck to Catalyst for Change
October 3, 2023
"Sometimes clarity trumps consistency depending on the context or specific use case in the system."
Nathan Curtis Nalini P. Kotamraju Jack Moffett Dawn ResselDiscussion
June 9, 2016
"If we are working on something that does not ladder up to our KSPs, then we should not be working on it."
Saara Kamppari-Miller Nicole Bergstrom Shashi JainKey Metrics: Comparing Three Letter Acronym Metrics That Include the Word “Key”
November 13, 2024
"Our mandate was to simplify the experience for end employees and managers, but we neglected our power users and that really hurt us."
Malini RaoLessons Learned from a 4-year Product Re-platforming Journey
June 9, 2021
"Over 4,000 users volunteered to look at the beta version, giving us excellent data at scale."
Mackenzie Cockram Sara Branco Cunha Ian FranklinIntegrating Qualitative and Quantitative Research from Discovery to Live
December 16, 2022
"If you signed up for a cohort, please make sure you’re in your private cohort channel to meet and discuss with your group."
Bria AlexanderOpening Remarks
June 9, 2021
"Many product teams have never come face to face with their revenue numbers before."
Jackie HoLead Effectively While Preserving Team Autonomy with Growth Boards
January 8, 2024
"The street used to be for public life; then cars took over and changed it profoundly."
Dan HillDesigning for the infrastructures of everyday life
June 4, 2024