Debunking the Myths of Cross-Disciplinary Collaboration
Summary
Trying to plan and collaborate across different teams whilst creating a cohesive culture can sometimes feel like a pipe dream. This is especially true as we start to work with more distributed teams and as we add more and more specialised functions to the mix, such as Design, Research, Content Strategy, Product Management, Engineering, Data Science…oh my! There are also a few common myths which are just not true in today’s modern team environment. Come along for a few laughs as we explore a few popular myths, debunk them and arm you with a few practical tips and ideas to help you build world-class products.
Key Insights
-
•
Standardizing roles in cross-disciplinary teams often creates unnecessary blame and ignores individual skills and project uniqueness.
-
•
Focusing on shared responsibilities tied to outcomes is more effective than rigid role definitions.
-
•
Co-creation and joint accountability across disciplines reduce friction and promote better team cohesion.
-
•
Bringing all disciplines into the design and research process early improves project outcomes and ownership.
-
•
Trust in distributed teams does not develop automatically; it requires deliberate relationship-building and communication.
-
•
Raising communication bandwidth by switching from asynchronous to synchronous formats can prevent frustration and trust erosion.
-
•
Ensuring all remote participants join calls individually helps level presence disparity and improves meeting effectiveness.
-
•
Early and continuous sharing of work rather than a final big reveal increases shared empathy and alignment.
-
•
Understanding the ‘how we got here’ context of a product is as important as aligning on where you’re going.
-
•
Process alone cannot guarantee great teamwork; investing in the human and messy aspects of collaboration is essential.
Notable Quotes
"Teams constantly bicker over turf blaming the various disciplines for their inability to meet deadlines."
"Research does this and design does that creates an us versus them strategy that leads to needless friction."
"Who is not in the room is just as important as who is."
"Exceptional teams are made up of individuals who reach out beyond the traditional boundaries of their own role."
"You have to know when to raise the bandwidth. If you see 10 plus people commenting in Slack, consider jumping on a video call."
"When trust is high, speed goes up and costs go down."
"People miss the water cooler moments in remote teams, so you have to create deliberate opportunities to connect."
"A shared understanding of how you got here creates a sense of purpose, not just urgency."
"The cargo cult story teaches us that form without understanding is not enough; blindly following process won’t deliver results."
"Process is neither necessary nor sufficient for great design."
Or choose a question:
More Videos
"Sometimes the solution perceives the problem in the eyes of users, especially in enterprise spaces."
Alexandra SchmidtEnterprise UX Playbook
December 1, 2022
"If you want to have tattoos, you can have tattoos and show them."
Jen Crim Jess Quittner Saritha Kattekola Alex Karr Gurbani PahwaCulture, DIBS & Recruiting
June 11, 2021
"If you’re a product manager, you don’t do very much design work anymore; you care about it but step away from the Figma."
Christian CrumlishAMA with Christian Crumlish, author of Product Management for UX People
March 24, 2022
"We have to slow down hiring to be more thoughtful and deliberate about who we bring on the team."
Libby MaurerTreating Diversity & Inclusion in Hiring as a Design Problem
December 5, 2019
"Sustainability is not just about the environment, it’s about community."
Ali Jeffery Sheri ChudowHow DesignOps Helped Enable Wall Street to Work Remotely
October 22, 2020
"Design research often acts like scientists with clipboards rather than humans in conversation."
Daniel GloydDesigning From the Inside Out: How Method Acting Can Inspire Design Research
February 12, 2026
"Learning should be an experience tailored around the learner, not the curriculum."
Kristin SkinnerFive Years of DesignOps
September 29, 2021
"Design strategy focuses on providing a framework for developing design solutions that support a given product strategy, whereas product strategy addresses the business model, the roadmap, and prioritizing requirements - Frank Guo."
Johanna KollmannInsights-Driven Product Strategy: Get your Research to Count
December 6, 2022
"Every piece of product can be described using components like intent, viscosity, and flow—making UX a physics problem."
David SternbergUncovering the hidden forces shaping user behavior
July 17, 2025
