Debunking the Myths of Cross-Disciplinary Collaboration
Summary
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
"Change is fundamentally about people—our approach lives out agile principles in service design to create a team that can build."
Laura Smith Tom GaylerEmbedding Service Design and Agile Practice within UK Planning Teams to Create Services that Last
December 3, 2024
"The LLM gave many different answers for the same passage, each time reporting it was one hundred percent confident."
Trisha Causley[Demo] Complexity in disguise: Crafting experiences for generative AI features
June 5, 2024
"Stakeholder communication is crucial because without it, we risk activity without impact."
Fisayo Osilaja[Demo] The AI edge: From researcher to strategist
June 4, 2024
"Frameworks are a team sport; each player brings unique strengths that help create innovative solutions."
Ruzanna RozmanGetting in Flow with Your Team
January 8, 2024
"The biggest challenge with LLMs was keeping them on task instead of writing their own Reddit posts."
Karen McGrane Jeff EatonAI for Information Architects: Are the robots coming for our jobs?
November 21, 2024
"This method has a degree of reactivity; paying attention to something may alter or change behavior."
Amelia ColeData-Prompted Interviews
December 17, 2021
"Over the long term, democratization programs can even out workloads and reduce pressure on research teams."
Trisha TerharEmpathizing with the Empowered: Non-Researcher Responses to Democratization
March 10, 2022
"Service design performs the belief, finance performs the control."
Jen van der MeerService design performs value
November 19, 2025
"I’m adopting a mindset of vulnerability and openness to failure because the worst outcome won’t shut the servers down or fire people."
Steve Baty Richard Dalton Maria Giudice Harry MaxDiscussion
June 9, 2016
