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
"Tech workers in the UK are five times more depressed than the UK average, with stress killing creativity."
Dr. Karl JeffriesThe Science of Creativity for DesignOps
January 8, 2024
"There’s been a huge convergence because everybody’s got a mobile device now and expects a certain kind of experience."
Amy MarquezINVEST: Discussion
June 15, 2018
"Enterprise UX is still nascent—businesses worldwide are just beginning to figure out where UX fits."
Steve Portigal Chris Chapo Kelly Goto Christian RohrerDiscussion
May 13, 2015
"It took a lot of relationship building and conversations to break down the perception that designers' time was owned by particular teams."
Alicia MootyDesign Staffing Models
September 30, 2021
"UX should be a critical dependency, not an afterthought or checkbox on the to-do list."
Ana Maria Montero Barrantes Aditi Dhar Michelle Kaplan Nate Osborne Matt LaurenceThe Authentic UX Talent Show
January 8, 2024
"Operations tends to be something companies only think about when they are scaling rapidly, but investing early is essential."
Lada Gorlenko Sharbani Dhar Sébastien Malo Rob Mitzel Ivana Ng Michal Anne RogondinoTheme 1: Discussion
January 8, 2024
"Data entry is the enemy; automation is the key to making research repositories successful."
Sofia QuinteroThe Product Philosophy Behind EnjoyHQ
March 10, 2021
"If you think innovation can happen without buy-in from the CEO, I would love to see that; I have not seen it work."
Laura KleinUnique challenges of innovation in enterprises
April 23, 2020
"Data analysts and user researchers rarely work together effectively, which is one of the biggest missed opportunities."
Andrew MichaelBuilding a Product Insights Team
March 10, 2022
