Coordinated collaboration: a Service Design & DesignOps love story
Summary
On paper, UX reviews are a no-brainer. Teams want feedback. Leaders want quality. Experts are willing to help. So why wasn’t it working? What seemed like a simple ask—“let’s offer UX reviews to teams”—quickly exposed a mess of invisible complexity: unclear ownership, inconsistent experiences, too many ad hoc requests, and burned-out senior designers doing unrecognized labor. There was so much willingness to help and share knowledge, but not enough of a system or support to scale. So we decided to design it. This is the case study of how we created an internal UX Review service, not just a process. Co-led by service design and design ops, we mapped the end-to-end journey—from request intake to reviewer matching to documentation and follow-up. We built shared definitions of success. We tackled coordination debt. And we designed for the system, not just the moment so we considered who participates, who decides, who benefits, and who sustains it. The project became a love story between two disciplines (Service Design and DesignOps), between intention and implementation to navigate the ambiguous intersection of what the business needs, what designers say they want, and what actually helps everyone do better work. More than that, it challenged us to apply our design craft to ourselves. What does it mean to design services for designers? How do we balance flexibility and fairness in a knowledge org? And how do we turn a “nice to have” into a performance driver?
Key Insights
-
•
Intentional, structured collaboration outperforms random or ad hoc teamwork in globally distributed UX teams.
-
•
Creating shared language and purpose, such as through a naming workshop, builds strong alignment beyond task-level agreement.
-
•
Forming a dedicated collaboration squad with explicit agreements on logistics, tools, and interpersonal support strengthens team performance.
-
•
Coordinated collaboration includes recognizing distinct but complementary roles, enabling each partner to do their best work while supporting the other.
-
•
Small feedback loops and check-ins sustain momentum and build collaboration muscle memory over time.
-
•
Increasing coordination can triple project impact from 2-3 to 10-11 projects per quarter with less individual effort.
-
•
Service design and design ops partnership drives service innovation and operational sustainability together.
-
•
Collaboration rituals and structured sessions replace reliance on chance hallway conversations, fostering alignment.
-
•
Focusing on learning and adaptive capacity within teams enhances UX knowledge sharing and continuous improvement.
-
•
Looking beyond traditional roles, operational or program managers can fulfill some design ops coordination functions in organizations lacking dedicated roles.
Notable Quotes
"Each of us is a superhero managing our own work and advocating for design best practices in silos."
"Coordinated collaboration is about designing our efforts with purpose to sustain peak performance conditions."
"Naming was nothing about the name; it was about creating alignment and clarity of purpose."
"Once collaboration loops start compounding, they become muscle memory and the structure supports our work."
"You do not rise to the level of your goals, you fall to the level of your systems."
"Small feedback comments like, 'Hey, how’s that going?' keep the momentum alive in addition to structured meetings."
"Our partnership is like cat and dog—sharing a body but having distinct identities and personalities."
"Increasing coordinated collaboration increased our service capacity by 200%."
"We intentionally created space to talk about career goals, stress, and how to support each other as a team."
"Program managers are the unsung heroes who can back up design ops work in many organizations."
Or choose a question:
More Videos
"Our job is to make sure research conducted by non-researchers is objective, rigorous and unbiased."
Anna Poznyakov Richa PrajapatiGet The Most Out Of Stakeholder Collaboration—and Maximize Your Research Impact
March 12, 2021
"It’s impossible for any single researcher or manager to identify all cross-functional impact opportunities alone."
Fatimah RichmondThe Future of ReOps as a Strategic Function: A Roadmap for Getting There
March 25, 2024
"We didn’t have the maturity of the practice itself to specify the impacts of losing design ops until it happened."
Benjamin RealShowing the Value of DesignOps by Not Having a DesignOps Team
October 21, 2020
"When executives start questioning your research details, that’s a good sign they’re engaged and trusting the process."
Landon BarnesAre My Research Findings Actually Meaningful?
March 10, 2022
"Testing AI products requires longitudinal methods to see how relationships and experiences evolve."
Jonathan Fairman Kevin JohnsonIntegrating generative AI into enterprise products: A case study from dscout
June 5, 2024
"Trying to figure all this out in business settings is nearly impossible; we have to step away and foster ongoing conversations."
Uday Gajendar Adam RichardsonFrom AI to Zeitgeist: Theory as the design antidote to AI hype
March 27, 2025
"The assistant deputy minister described this to me as a design problem, even if his peers couldn’t articulate it that way."
Gordon Ross12 Months of COVID-19 Design and Digital Response with the British Columbia Government
December 8, 2021
"Even if the model is responsible for the behavior, there’s another piece of the puzzle: the context."
Paz PerezContext Architecture for AI systems
September 11, 2026
"Nobody actually cares that we’re better researchers. The question should be, what makes us different? What makes us distinctive?"
Peter LevinSolve a Problem Here, Transform a Strategy There: Research as an Occasion for Expanding Organizational Possibility
March 25, 2024
