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 learning framework does not prescribe but supports reflection in action and demonstration or action."
Yoel SumitroActions and Reflections: Bridging the Skills Gap among Researchers
March 9, 2022
"If you want an accessible app on iOS and Android, using the standard native APIs and controls will get you there."
Sam ProulxMobile Accessibility and You
June 9, 2022
"VPs want to know what you really think. They want to see your insights distilled into a clear position of what needs to be done next."
Dalia El-ShimySo You've Got a Seat at the Table. Now What?
March 31, 2020
"The big question to ask in collaboration is: what is the main question you’re trying to answer and why does it matter?"
Jemma Ahmed Subhasree Chatterjee Robert Fabricant Alexandra Jayeun Lee Ben RobinsCollaboration: learning from other fields beyond our own [Advancing Research Community Workshop Series]
August 7, 2024
"Do I find a way to make this conversation more about the software as scheduled or do I show Laura how to react to the unplanned?"
Randolph Duke IIWar Stories LIVE! Randy Duke II
March 30, 2020
"Doing these conversations regularly, not just in crisis, makes a big difference."
Laura WeissThere is No Playbook: Leader as Coach During Challenging Times
April 26, 2024
"Statistical significance tells you if a change is likely not random, but it does not tell you if the change matters to your business."
Landon BarnesAre My Research Findings Actually Meaningful?
March 10, 2022
"The best large language model is right under your nose: the human brain with 300,000 years of ancestral development."
Dr. Jamika D. Burge Nick Fine Alexandra Jayeun Lee Greg Nudelman Bo WangHow UX researchers can partner with (and not be replaced by) AI [Advancing Research Community Workshop Series]
August 31, 2023
"Amy Tibido used to call what I was doing dusting the content — tidying the words on the surface without solving the underlying problem."
Jonathon ColmanHow to Maximize the Impact of Content Design
January 8, 2024
